chore: resolve iss-35, the brief-surface reconciliation

[REPPL]

Resolves ledger issue iss-35 (brief-surface reconciliation, critical) — a record-only move, open/ → resolved/ with impact: internal, performed by the resolve verb itself.

Chained PR: base is feat/iss-75-dev-install-mode (#139) — the resolve uses the chained --impact verb from #136. Merge order #136 → #137 → #138 → #139 → this; GitHub retargets automatically.

Why it resolves now

The 2026-07-24 maintainer grill decided it (recorded in .abcd/work/DECISIONS.md): everything iss-35 stayed open for is verified shipped — the surface_coverage record-lint blocker is armed, the 16 surface chapters exist (including docs/history/version), the skills→commands relabel landed, the staged Status column is machine-checked, and the crosscheck is wired as a release gate. The only residue is the gate's scope/depth pinning, tracked separately as iss-122 (queued next in this run).

Verification

• The decision entry was verified against the record before resolving — fail-closed rule: the queue's claim was checked, not trusted.
• record-lint exit 0 and make preflight exit 0 after the move.
• Reviews: skipped under the run contract's conservative classifier and stated openly — the diff is a pure record move (one file relocation plus the impact stamp), with no code, docs-claim, or trust-boundary content.