Set up to execute four threads under the revised process: plans and status brought current #768

Work is now organized as four threads, executed in order, one open worktree at a time. Before the first
of them starts, every thread needs a plan that is current, and one status document carries a tick that
is wrong.

The revised process

• One open worktree at a time. Other issues may be resolved in that same tree. No PR until every
  issue in that worktree is resolved.
• Issues are logged as they are discovered, and where each will be resolved is decided at that
  moment: in the current worktree (added to the current plan) or elsewhere (a plan created for that
  worktree and its issue, cross-referenced from the current plan).
• An issue is blocking when we cannot proceed without addressing it and it is either orthogonal —
  a hitherto unknown bug exposed by the current work — or complex enough to justify a new worktree.
• The plan is committed before the work begins, and every commit updates all documents it touches:
  plan, architecture, and user-facing. No deviations.

The threads, in order

1. Epic: Command line interface — one output convention, every app #740 — one output convention, every app. Four items remain: writ's renderings, lore, star
   (cmd/star/cli duplicates cmd/internal/cli, and the two now disagree on the flag surface #743), and enforcement. Three of the four still need issues.
2. Resource management — Sealed provider resources: every announced resource type is an interface #625 is 5 of 10 phases; Seal pkg — the widest consumer surface #644 is next. Four items stand outstanding on
   4-resource-management.status.md.
3. The writ lifecycle surface: reconcile, scopes, and the vocabulary settlement #762 — the writ lifecycle surface. Phase 1 landed with The CLI specification describes the code that exists #767; phases 2–4 remain.
4. Epic: Unified configuration #441 — unified configuration. Designed, essentially unbuilt, and scheduled nowhere.

What this chore lands

• A plan for thread 4, which has none. It records that unknown configuration keys are designed to be a
  loud error in three places and that the mechanism lives inside a single unticked status box, so a
  typo'd setting name is ignored in silence today. It also records the kv exemption that qualifies the
  finding, and the cross-thread dependency it creates for The writ lifecycle surface: reconcile, scopes, and the vocabulary settlement #762's migration note.
• The stale tick in 10-command-line-interface.status.md. Its first unchecked box — "writ consumes
  the set it registers" — was completed when writ registers --store and reads it nowhere: status reports on the default store regardless #753 and writ accepts any --output value: -o bogus prints the dashboard and exits 0 #754 closed, and the document still shows the work
  as outstanding. Stale status metadata is the failure mode the whole process exists to prevent, so it
  is corrected here rather than carried into the thread that would inherit it.
• Thread 1's plan updated to state where the epic actually stands.
• Thread 2's plan brought complete, accurate, and current, including the four outstanding items.

No code changes. This is setup.