fix(#324): config spec re-baseline; fugu-ultra manual-only everywhere

[polymath-orchestrator]

Summary

Executes #324 plus the operator's 2026-07-15 ruling: codex-fugu baseline is fugu; premium tiers (fugu-ultra, fable) are manual-only — never a default, mix pin, baseline, or captured spec value.

• Live first: ao workerMix fugu-ultra→fugu and the deprecated respawn stanza dropped (CAS write against fresh ETag). Verified: live config has zero fugu-ultra, zero respawn.
• Specs re-baselined from live for all four projects (capture), including a new tracked agent-vault.json; absorbs Project config write safety and daemon defaults (#298 P1) #302's per-harness pins + canonical names.
• Production fixes (rule 8, found while executing the ruling): knownModelsForHarness listed ONLY fugu-ultra for codex-fugu (no baseline at all — the likely origin of the bad spec pin) and only legacy *-codex names for codex without the real gpt-5.5; both now baseline-first with explanatory comments. Routing-label descriptions corrected (agent:fugu (fugu), agent:codex (gpt-5.5)).
• Policy is durable: ops/project-config/README.md records the tier ruling; every casual fugu-ultra fixture in tests neutralized; the catalog test now asserts the baseline is listed and truthfully unknown when unprobed.

Post-merge: node ops/project-config.mjs check --all is expected green (verified locally pre-PR against live).

Test plan

• npm run ci:backend — PASS (build, vet, race tests, golangci-lint 0 issues; a stale-cache false failure from a deleted worktree was diagnosed and cleared — cache clean, not a code change)
• npm run test:ops — PASS (474/474)
• format:check + prettier over staged files — PASS
• Frontend suite not run: frontend tree byte-identical to main

Closes #324. Refs #302, #313, #320.

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

[polymath-orchestrator]

Reviewer finding (workspace in-place→worktree in the ao spec) — justified, not drift: live agent-orchestrator has operated in worktree mode throughout (observable: ao-managed worker worktrees exist under ~/.ao/data/worktrees/agent-orchestrator/); the committed spec's in-place was the stale value from #314. The #313 plan's in-place ruling set the daemon default for newly created projects (which stands, per #302's DefaultProjectWorkspaceMode), not this project's operating mode. Capture-from-live is the correct baseline.

[polymath-orchestrator]

Final review verdict for head 5dfb79bb49b22a548088740ae8df7a1070ba7eac: clean. Independent reviewer family: codex (full-diff pass after an amend recovered files a stash cycle had unstaged; 1 medium finding adjudicated with evidence above — no code change required). Gates on this tree: ci:backend (0 issues), test:ops 474/474, prettier clean; frontend byte-identical to main. Zero unresolved threads.