Selector probe: derive local_disagreement from interrogation coverage; keep rootless revisions pending

[AdaWorldAPI]

This PR has two commits on crates/cognitive-shader-driver/examples/recipe_selector_probe.rs, both following up #1362.

1. Rootless revisions stay pending (b448ffec)

Codex found this in its review of #1362, but #1362 merged before the fix was pushed. The old predicate fired only when the encounter brought a new independent root. A revision that changes the horizon without a new root, such as a contradiction that withdraws a claim (ContradictionPreserved), was therefore never applied.

new_encounter now holds while revising would still change any mask the revision writes: the projected claims, a root, an inherited root, or a contradiction not yet in the tension. On all 65 536 worlds of a 2-bit universe this equals whether revise actually changes those masks.

• New test a_rootless_contradiction_is_still_revised: the revision is applied once, then the cycle rests.
• an_echo_selects_nothing now uses a real Echo.

2. local_disagreement is derived (de69eefe)

local_disagreement is now unresolved_tension \ interrogated. interrogated is the coverage the MooreInterrogation recipe writes (by union), and nothing else writes it. Revision never clears tension; interrogation clears the fact and leaves the tension unchanged.

Measured:

• A new contradiction reopens the fact. From a settled state, the fusion world now runs [Revision, MooreInterrogation] and then rests.
• Only new tension does. A contradiction that is already covered does not reopen it; one on a new bit does.
• The rest depends on the write. If the interrogation's write is dropped, the cycle never rests, the same as dropping revision's write.
• Wired cycles are bounded and replay. Every wired cycle rests within 5 steps and replays to the same path and the same final world.

Finding: with both facts derived, a cycle is no longer one step per condition. Revision can reopen local disagreement, so V1 interrogates after revising, not only before.

Still stand-ins or open:

• observations_pending and frontier_bounded are still stand-ins.
• interrogated lives only in this probe. InterpretiveHorizon has no coverage field, so where coverage would live durably is undecided.
• The Moore recipe's actual fold (the Palette hop, D-GSO-5 R2) is not linked to claim bits. Only the coverage it leaves is wired.

Checks

17 tests in total; clippy and fmt are clean. All 15 disable runs fail as they should:

• Commit 1 (10): the derived fact forced to true; the supplied flag used instead of the derived fact; revision's result discarded; roots compared against projected claims; the drop flag ignored; each of the four mask clauses dropped; the old roots-only predicate restored.
• Commit 2 (5): raw tension read without the coverage; interrogation made a no-op; the supplied flag used instead of the derived one; interrogation clearing the tension; the drop flag ignored.

Board: the STATUS_BOARD.md D-GSO-6 row is updated. New entry .claude/board/entries/2026-10-06-selector-local-disagreement-wired.md, and the existing 2026-10-06-selector-revision-wired.md entry now covers the fix. The entries index is regenerated; SUPERSESSION-INDEX.md was regenerated and came out unchanged.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MHMvKHLhM6xwRswKY4s6vY

---

Generated by Claude Code

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: 9172a578-22cd-4002-a35f-3054416323b8

📥 Commits

Reviewing files that changed from the base of the PR and between 10a7aac and bca533a.

📒 Files selected for processing (5)

• .claude/board/STATUS_BOARD.md
• .claude/board/entries/2026-10-06-selector-local-disagreement-wired.md
• .claude/board/entries/2026-10-06-selector-revision-wired.md
• .claude/board/entries/README.md
• crates/cognitive-shader-driver/examples/recipe_selector_probe.rs

 ______________________________________________________________
< Ad Astra Per Codicem Fixis. To the stars through code fixes. >
 --------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 7a6a16b2-3242-4be7-bf02-feba130a8c6f)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T12:25:35.336851Z	f07e3b4	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.