740 and 762 disagree on writ reconcile: flags that will not exist, and an ordering that no longer holds #772

Two plans describe the same command differently, and one of them describes flags the command will not
have.

The settled surface

writ reconcile produces a report. It has no command flags — only the globals: --output/-o,
--filter, --jq, --store, --dry-run — and it must utilize all of them faithfully. The selector
between fix, diff, and summary behaviors is deferred to the reconciliation epic and is not designed here.

What disagrees

762-lifecycle-scopes.md:51 records the shape as
writ reconcile [--drift] [--fix] [--json] [<project>...], quoted from writ-deploy-family.md:31. None
of those three flags will exist: --json is replaced by the shared -o, and --drift and --fix are
the deferred selector under another name.

762-lifecycle-scopes.md:96 says "5.1's 'there is no --fix' is retired as the stale claim it
is." Reconcile will repair, but it has no --fix today and the surface for choosing is undecided, so
this overstates what is settled.

5.1-reconciliation.md:12 carries the same overstatement.

740-cli-output-conventions.md:365 is a forward-looking test row asserting -o json and -o yaml
work on writ status — a command being retired, not modernized.

740-cli-output-conventions.md:27 claims the epic rewrites status/report.go before #762 moves it.
The work lands as writ reconcile, so that ordering does not hold.

What is NOT wrong in 740

Seven of its eight writ status mentions are dated measurements or current file paths — lines 27 (path
half), 114, 171, 212, 231, 237, 242. They record what was found on 2026-08-30 and where the code lives
today. Rewriting them would falsify a record rather than correct one, and they are deliberately left
alone.