fix(coverage): unblock org-wide OpenCode approval + docs(gaps) corrections

.gitignore

@@ -3,3 +3,4 @@ __pycache__/
 .coverage
 .pytest_cache/
 .codegraph/
+.claude/

CHANGELOG.md

@@ -5,6 +5,29 @@ this file. The format follows Keep a Changelog, and versioned releases follow
 Semantic Versioning where the repository publishes a release.
 
 ## [Unreleased]
+- Fix `scripts/ci/pingora_edge_policy.py`'s `_load_changed_files`: the
+  post-loop pagination-exhaustion `PolicyError` was unreachable dead code
+  (proven: 31 full 100-item pages always trip the in-loop `len(files) >
+  3_000` raise during page 31's own iteration before the loop can exhaust
+  its range), and it was silently failing this repo's org-wide
+  `coverage-evidence` gate (`fail_under=100`) for every PR reviewed through
+  the central OpenCode/Noema/Strix dispatcher, blocking opencode-agent from
+  ever posting an APPROVED verdict anywhere in the org. Marked
+  `# pragma: no cover` with justification, matching this repo's existing
+  convention. See the 2026-08-30 "OpenCode Agent 자체 문제" gap-baseline
+  entry for the full three-PR diagnosis this came out of. (Independently
+  found and fixed by the org owner in the same window, commit `34c88356`,
+  with a stronger regression test pinning the arithmetic invariant itself —
+  adopted the owner's version when reconciling the resulting merge conflict.)
+- Document a structural CodeRabbit gap in `docs/product-technical-gap-baseline.md`
+  (2026-08-30 entry): every ContextualWisdomLab repo is below CodeRabbit's
+  10-GitHub-star automatic-review threshold, so CodeRabbit never reviews a new
+  commit without an explicit `@coderabbitai review` trigger comment — this was
+  surfacing as a `naruon` PR-governance metadata-gate block that looked like a
+  blocking finding but was actually CodeRabbit's own "not reviewed yet" state.
+  No code change; a central auto-trigger workflow is a candidate follow-up,
+  deliberately deferred pending a review of its required-workflow-ruleset
+  blast radius.
 - Fix one more Devin Review finding on PR #1452, a genuine gap in the round-4
   malformed-gateway-reply fix (`scripts/ci/contextual_orchestrator_review_sidecar.sh`,
   `tests/test_contextual_orchestrator_review_runtime_preflight.py`):
@@ -302,6 +325,27 @@ Semantic Versioning where the repository publishes a release.
   `zero_data_retention` stays `False` as it already was; only the citation
   and note change. See the 2026-08-30 ZDR/NIM-routing gap-baseline entry for
   the full architecture review this citation was part of.
+- Correct `docs/product-technical-gap-baseline.md`'s "2026-08-30 post-#1486/#1438 wake" entry: Bytez
+  can never populate `orchestrator/free` regardless of its HTTP status (`_parse_bytez` never sets
+  `is_free`), and the `request_failed status=413` line is the sidecar's own unconditional self-test
+  rather than a live ZDR-prefetch fallback. The incident's actual terminating message
+  (`"review sidecar preflight failed"`, a live warm-up-probe rejection) is the same one the
+  `ORCHESTRATOR_CATALOG_FAMILY_CAP` fix above mitigates (hosted confirmation remains pending) — the
+  two corrections converge on the same real root cause rather than describing two different bugs.
+  Also adds a bounded, one-retry
+  resilience improvement to `contextual-orchestrator`'s provider *discovery* fetch (a different,
+  non-overlapping call site from the family-cap/preflight fix above) in
+  `ContextualWisdomLab/contextual-orchestrator#923`.
+- Refresh `docs/product-technical-gap-baseline.md`'s §5.1 next-increment list,
+  which had gone stale: #1297 was already merged, and #1345/#1326 were closed
+  unmerged, yet all three were still listed as pending candidates. Replaced
+  with the current state (#1347 still open/dirty; `ContextualWisdomLab/naruon#1486`
+  added as this pass's naruon increment) and recorded the naruon-side Noema
+  role clarification: naruon's `noema-general-agent` is a separate, correctly
+  BYO-LLM-scoped agent from this repo's central review-bot Noema — they
+  intentionally share only a name — and it now has a `check_calendar_conflict`
+  tool (PRD-02) that reuses naruon's existing deterministic conflict policy
+  instead of inventing a second one.
 - Bump the vendored `contextual-orchestrator` review-sidecar pin from
   `5f2753a` (the #1422 pin) to current `main` `30c6d716`, picking up
   `ContextualWisdomLab/contextual-orchestrator#919`: generalizes the