Docs: AUTHORING.md — manifest parser strips unknown fields, doesn't reject them

[selfcontained]

Nightly docs audit (2026-08-02, scheduled job).

Audited this run

• Diff since 5525021 (Docs: fix operations-runbook drift — artifact-only updates, real release-workflow shape, cursor in preflight #865–Cover use-release-stream: applyStreamEvent reducer and stream wiring #868): refactor/test-only, no doc-bearing changes.
• docs-pane Notifications section vs notification-settings.tsx + split section components, notification-runtime.ts, focus-tracker.ts, use-agent-focus.ts, slack.ts, agent-lifecycle-tools.ts: all claims verified accurate (3s web-notify ack fallback, 15s heartbeat / 30s TTL focus suppression, 4 status cues + mobile tap, Tips & Guidance controls, dispatch_notify params/limits, persona agents lacking the tool).
• docs-pane Repo Tools section vs repo-tools.ts, mcp/server.ts tool sets + toolsRoot, routes/mcp.ts scope, lifecycle-hooks.ts, setup-script.ts: all claims verified accurate (repo_ prefix, dot sanitization, param→flag mapping, effective agent/job scopes, stop hook 15s best-effort, DISPATCH_AGENT_ID, ~/.dispatch/env).

Changed

• release-notes/AUTHORING.md: the migration-manifest section claimed fields outside the V1 schema "will fail validation". UpdateMigrationManifestSchema is a plain z.object — unknown keys are silently stripped, never rejected — and nothing else (bin scripts, CI) validates manifests strictly. Reworded so authors don't rely on an error that never fires.

Deferred / noted

• Stale backlog item removed from Brain: "AUTHORING.md doesn't cover migration manifests" — it does now (Migration manifests section exists and its other claims verified against update-migrations.ts / update-migrations-evaluator.ts / assisted-update.ts).
• Next run: docs-pane Worktrees section vs apps/server/src/shared/git/worktree.ts after the Consolidate duplicated git helpers into shared git-context #867 git-context consolidation.

🤖 Generated with Claude Code