fix(noema): ground formal verdicts in exact changed-line manifest

[seonghobae]

Incident

BandScope PR #1122 failed in Noema job 99792663163 with:

RuntimeError: Noema reviewed line 3 is not an exact changed-side line

Here, line 3 is the third reviewed_lines item. The strict validator correctly rejected a model-produced coordinate that was not present on the corresponding side of the unified diff.

Root cause

noema_review_gate.py already parsed the authoritative (path, line, side) set, but the model received only the raw diff and one schema example. The repair retry repeated a generic “use exact changed-side locations” instruction without exposing the permitted coordinates. A long-running retry could therefore make the same class of coordinate guess again.

Repair

• serialize every parsed changed-side coordinate into a compact deterministic JSON manifest, grouped by file and LEFT/RIGHT inclusive ranges;
• include the same manifest in the initial request and the one repair request;
• declare it the sole coordinate authority for reviewed_lines, adversarial probes, and findings;
• point the repair instruction at the manifest and include the exact validation error.

The deterministic post-response validator remains unchanged and fail-closed. This patch does not snap, coerce, filter, or silently discard invalid coordinates, and does not downgrade a formal verdict to obtain a green check.

TDD evidence

• RED: the BandScope-style invalid third reviewed-line item failed before implementation because the manifest interface did not exist;
• focused Noema suite: 116 passed;
• combined exact-tree repository verification: 2342 passed, 1 skipped, 21 subtests passed;
• scripts/ci: 11019 statements, 4440 branches, 0 missed, 0 partial, 100%;
• docstring, compile, and git diff --check gates passed.

Verification run: https://github.com/ContextualWisdomLab/.github/actions/runs/33514831758

Dependency and rollout

PR #1610 is a separate test-only repair for a protected-main Strix coverage regression discovered while running the full suite. It must land first so this PR's repository-wide coverage-evidence check reflects the Noema change rather than that pre-existing baseline gap.

After both PRs merge, rerun Noema against BandScope PR #1122 and require a fresh exact-head verdict before considering the production incident closed.

---

[coderabbitai]

Warning

Review limit reached

Next included review available in 2 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 0099569c-7b37-4f46-83c8-f64757879d61

📥 Commits

Reviewing files that changed from the base of the PR and between a86177e and 0343778.

📒 Files selected for processing (4)

• CHANGELOG.md
• docs/superpowers/plans/2026-09-01-noema-exact-changed-line-grounding.md
• scripts/ci/noema_review_gate.py
• tests/test_noema_review_gate.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Devin Review found 3 potential issues.

[seonghobae]

The exact-head-path-policy check failure on this PR's head is not from this PR's diff (which only touches noema_review_gate.py + tests). scripts/ci/test_strix_quick_gate.sh's bash suite asserts .github/workflows/strix.yml exports LLM_TIMEOUT=0, but the workflow currently hardcodes LLM_TIMEOUT=300 — confirmed this same assertion fails identically against origin/main directly, independent of this PR.

Opened #1658 with the one-line fix (300 → 0, matching the three sibling timeout env vars on the following lines, which are already 0). Once #1658 merges, this PR's exact-head-path-policy check will pass without needing a rebase (the check re-clones main fresh each run). Not merging it into this PR itself since it's unrelated to the noema line-manifest change.

Claude-Session: https://claude.ai/code/session_019YgmaEKnPhrsbSyQBierFH

---

Generated by Claude Code

[seonghobae]

Both dependencies this PR's exact-head-path-policy failure needed are now merged to main: #1610 (Strix compat-entrypoint coverage, merged 13:57) and #1658 (LLM_TIMEOUT=0, merged 00:57). Re-triggered the failed job (rerun_failed_jobs on run 33517130928) to get a fresh evaluation against current main.

Claude-Session: https://claude.ai/code/session_019YgmaEKnPhrsbSyQBierFH

---

Generated by Claude Code

[seonghobae]

Naruon consumer-path advancement from fresh live state: dependency #1610 is now merged, but this PR is still open with head 03437786ad57dad849a996c334911d294dc4bcee, while protected .github/main has advanced to 2792b964b321d096ed292979e175510cf94aa03c and the PR currently reports non-mergeable. Please reconstruct/restack this owner repair non-destructively on current protected main, preserving only the exact changed-line-manifest delta and regenerating all current-head evidence rather than transferring the earlier 33514831758 run.

Please also include the existing Naruon #1613 canary in post-merge acceptance: ContextualWisdomLab/naruon#1485@4e2cb3b39f89aff811d5113962861bd1963d2996 previously failed required Noema run 33444969216 / job 99781918923 with Noema reviewed line 1 is not an exact changed-side line after repository-native gates were green. After the repaired central path reaches protected main, Naruon will rerun that unchanged head. GREEN is a genuine exact-line formal verdict or an early typed review-unavailable/model-output-invalid result; nearest-line coercion, synthetic source findings, predecessor evidence, and leaf source churn remain prohibited.