Clear the operations-layer alignment residuals

[boshu2]

What

Closes out the residual items that #1051 (operations-layer alignment) explicitly disclosed rather than fixed in-scope. Six items:

1. Terminology residue on non-authority surfaces — docs/contracts/lesson-format.md speaks of an RPI traversal; the dated-PROPOSED docs/architecture/eval-architecture.md carries a terminology note instead of being rewritten; a stale check-flywheel-compounding.sh mention leaves measure_test.go; the dormant scripts/check-pillar-coverage.sh (self-skipping, no invoker) is deleted along with its now-stale preamble-grandfather entry.
2. Eval smoke fixture defect — cli-command-surface-smoke.sh counted #{3,4} while the canonical count spans #{3,5}, so the fixture failed when executed (all=76 vs the pinned 89). Widening the regex makes it pass end to end and strengthens the check: 13 five-hash eval subcommand headings now enter the help matrix. The pinned counts are unchanged.
3. Vacuous retrieval-quality canary — the suite and its smoke named eight Go tests that no longer exist anywhere (verified at main), so the canary ran zero tests. Retired honestly: suite + smoke deleted, delisted from the official canary list, the nightly job whose only step ran that smoke removed (with all five summary-job references), and docs/contracts/retrieval-comparison.md marked dormant. The blocking always.retrieval-manifest-paths gate remains the live retrieval guard (verified registered and green).
4. Consumer-free dream: config block removed, along with the four resolution helpers it exclusively used. Existing configs carrying dream: keys still parse — covered by a new tolerance test exercising the production loader.
5. Remaining knowledge-shaped writers moved to the scratch tier — provenance miner, team-runner, and bin/ralph now write under .agents/scratch/. bin/ralph still resumes legacy .agents/ralph/ checkpoints, so the documented backwards-compat contract holds with no migration; the suite grows 3 → 5 tests covering both paths and proving a path outside both dirs is still refused.
6. MEMORY.md consumer audit recorded in docs/contracts/agents-documentation-authority.yaml: two live read-only consumers found (the corpus-delta eval harness and the root-memory convention), so it is retained with a named retirement condition rather than removed.

Deliberately not changed: the ao status "loop evidence" copy. It mirrors the loop_evidence machine key, is permitted by the ubiquitous language's local-control-structure carve-out, and is pinned by a frozen compatibility baseline — completing that cosmetic rename would have meant editing a frozen behavioral record.

Why

Every item was a disclosed residual from #1051: dead surfaces that still had to be swept, one fixture that never actually passed, and a knowledge-store-shaped writer set that hadn't reached the ADR-0016 tiers. Left alone they decay into exactly the drift the alignment set out to remove — a canary that proves nothing, a fixture nobody runs, a config block with no consumer.

How I tested

• cd cli && go build ./... && go vet ./... && go test ./... — clean (64 packages ok)
• python3 scripts/check-cathedral-cut-conformance.py — PASS
• bats product-boundary + operating-contract + mine-all-sessions + ralph-budget-contract — 23 tests green
• bash scripts/regen-all.sh --check — all projections current; check-test-count-regression.sh PASS via the Test-Removal-Reason trailer
• bash evals/agentops-core/fixtures/cli-command-surface-smoke.sh — exit 0 at this head, exit 1 at main (the defect it fixes, demonstrated in both directions)
• bash scripts/ci-local-release.sh --quick — PASSED; full ci-local-release.sh — PASSED (154s)
• ao gate check --full — 67/68; the lone failure (go.cli-architecture) reproduces with byte-identical output on unmodified main in this container (shallow-clone git-ancestry artifact) and passed on GitHub CI last round
• Fresh author-distinct validation: PASS (validator context 9fad04ff984f2162, not_checked: []). An earlier revision of this commit failed its first fresh validation with two HIGH findings — a dangling nightly invoker of the deleted smoke, and the ralph back-compat test regression. Both were fixed, and this validator independently re-verified each prior finding, re-ran the battery at both trees, and adversarially probed the ralph guard across four path classes to confirm it wasn't loosened.

Disclosed, pre-existing, and not repaired here (verified present on main too): two frozen compatibility baselines are stale — families/status/case.json asserts ao status --help contains "loop evidence" (cobra renders Long, not the Short it greps) and families/config/case.json asserts a dream_report_dir key that untouched tests already pin as absent at base. Neither has an automated runner in-tree. They deserve a follow-up bead alongside each other rather than an edit smuggled into this diff. The team-runner dry-run harness fails identically at both trees (codex absent in this container).

Checklist

• make build && make test passes (if Go changes)
• No secrets or credentials in code
• Breaking changes documented (CHANGELOG.md [Unreleased] Removed entry, mirrored in docs/CHANGELOG.md)

🤖 Generated with Claude Code

https://claude.ai/code/session_01F5zgDPAfgMsQCN8H7W2sw4

---

Generated by Claude Code