fix: preserve scope in consequential claims

[ruby-dlee]

Intent

Fix unchecked scope collapse in both directions: firstmate must not turn one route's failure into a platform-wide blocker or one leg's success into a claim that a composite mechanism works. Ship one unified consequential-claim carrier in operating fundamentals principle 7 that records exact scope and every leg, requires direct end-to-end evidence or an explicit unverified label for positives, requires authoritative reference plus an independent safe route and narrowest result for blockers, blocks claims on unresolved directly relevant contradictions, and preserves target-outcome, critical-path, consequential-bypass rationale, and operation-failing-not-noise protections. Route the skill before making or relaying consequential success, failure, blocker, or capability claims; keep firstmate-owned and relayed blocker proof symmetric. Remove the obsolete one-load-bearing-assumption route and stale ownership pointers without deleting or merging crew-steering. Make the Lavish decision trigger fire before creating, repairing, or presenting a multi-option captain choice and preserve the durable non-browser protocol. Keep the aggregate branch net-neutral or smaller in both tracked lines and words, retain structural coverage for every required carrier concept and presentation trigger, and do not broaden the decision pretool gate, touch personal captain state, change machine-local Slack skills, or perform unrelated audit cleanup. The structural assertions prove contract presence, not behavioral firing.

What Changed

• Unify consequential-claim proof around exact scope, end-to-end evidence, contradiction handling, and narrow blocker classification.
• Apply the same blocker proof requirements to firstmate-owned and relayed claims, while removing obsolete premise-check shortcuts and stale ownership pointers.
• Route multi-option captain choices through the durable Lavish protocol and expand structural contract coverage for the new claim and presentation triggers.

Risk Assessment

✅ Low: The corrective commit closes the unresolved-contradiction loophole, preserves the unified scoped-claim contract, and the aggregate branch remains smaller in tracked lines and words without touching forbidden surfaces.

Testing

Completed 1 recorded test check.

• Outcome: ⚠️ 1 error across 1 run (1h56m4s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 1 issue found → auto-fixed ✅

• 🚨 .agents/skills/operating-fundamentals/SKILL.md:53 - The required criterion says the carrier “blocks claims on unresolved directly relevant contradictions,” but this hunk says a contradiction blocks the claim only until it is “reported unresolved.” That makes disclosure alone a route to resume the consequential claim while the contradiction still exists. Keep the claim blocked until the contradiction is reproduced/resolved or demonstrated to belong to a different scope; otherwise report only the unresolved observations, not the claim.

🔧 Fix: Block claims on unresolved contradictory evidence
✅ Re-checked - no issues remain.

⚠️ **Test** - 1 error

• 🚨 tests failed with exit code 1
• command -v tmux >/dev/null || { echo "tmux is required for e2e tests" >&2; exit 1; }; tmux -V; rc=0; for t in tests/*.test.sh; do echo "== $t =="; bash "$t" || rc=1; done; uv run --directory tools/agent-fleet --locked pytest || rc=1; uv run --directory tools/agent-fleet --locked python -m compileall -q src || rc=1; exit "$rc"

✅ **Document** - passed

✅ No issues found.

🔧 **Lint** - 1 issue found → auto-fixed ✅

• ⚠️ linter found issues (exit code 1)

🔧 Fix: Remove unused operating-fundamentals test variable
✅ Re-checked - no issues remain.

✅ **Push** - passed

✅ No issues found.

[ruby-dlee]

bugbot run