docs(fleet): add operator configuration guide

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/fleet/FLEET-CONFIG-DOCS-IA-CHECKLIST.md

@@ -5,27 +5,27 @@
 This checklist is an acceptance contract for documentation and examples. It does not authorize
 schema, runtime, systemd, role, profile, or live-fleet changes. An item is complete only when its
 named artifact exists, is linked from the fleet documentation entry point, and its evidence is
-recorded in the M0 task/PR.
+recorded in the M5 closure report and linked deferral evidence.
 
 ## M0 baseline acceptance
 
-- [ ] `docs/PRD.md` states the roster as desired-state SSOT; generated environment, systemd,
+- [x] `docs/PRD.md` states the roster as desired-state SSOT; generated environment, systemd,
       tmux, and heartbeat artifacts as non-authoritative projections; and fail-closed handling of
       unsupported or quarantined legacy input.
-- [ ] `docs/PRD.md` defines the required classes and authority boundary: `validator` certifies but
+- [x] `docs/PRD.md` defines the required classes and authority boundary: `validator` certifies but
       does not merge; `merge-gate` remains sole approve-to-land/merge authority; `team-leader`
       capacity is lease-bounded; `interaction` is request/status only; instance names such as Tess
       and Ultron remain configurable.
-- [ ] `docs/PRD.md` defines local lifecycle semantics for `enabled`, persisted desired state, and
+- [x] `docs/PRD.md` defines local lifecycle semantics for `enabled`, persisted desired state, and
       observed state, including stopped-state preservation through migration, apply, and reboot.
-- [ ] `docs/PRD.md` defines the generated-env/local-override boundary, explicitly denies arbitrary
+- [x] `docs/PRD.md` defines the generated-env/local-override boundary, explicitly denies arbitrary
       command overrides in M1–M5, and requires key-name/hash-only quarantine diagnostics.
-- [ ] `docs/PRD.md` identifies the M1–M5 local-tmux scope and excludes remote reconciliation,
+- [x] `docs/PRD.md` identifies the M1–M5 local-tmux scope and excludes remote reconciliation,
       connector mutation, secret references, arbitrary commands/channels, gateway convergence, and
       UI configuration storage.
-- [ ] `docs/TASKS.md` contains the complete M0–M5 one-card/one-PR dependency DAG for #758 with
+- [x] `docs/TASKS.md` contains the complete M0–M5 one-card/one-PR dependency DAG for #758 with
       agent tier, branch, dependency, estimate, and evidence expectations.
-- [ ] `docs/fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md` classifies every current shipped
+- [x] `docs/fleet/LEGACY-EXAMPLE-PROFILE-DISPOSITION-INVENTORY.md` classifies every current shipped
       fleet example, profile, and service preset before M1 implementation starts.
 
 ## Required documentation IA for M1–M5
@@ -72,15 +72,24 @@ recorded in the M0 task/PR.
 
 ## Cross-cutting evidence gates
 
-- [ ] Every retained or migrated YAML/JSON example, profile, and service preset validates through the
-      same executable schema and shared baseline-plus-`roles.local` resolver used by the CLI.
-- [ ] Every retired example/profile/service preset has a replacement link and deprecation note; no
+- [x] Every retained or migrated YAML/JSON example, profile, and service preset validates through the
+      same declared executable production parser/resolver path recorded by the disposition inventory;
+      versioned v1 fixtures are not forced through the v2 compiler.
+- [x] Every retired example/profile/service preset has a replacement link and deprecation note; no
       unresolved legacy class or tool-policy alias remains silently shipped.
-- [ ] Documentation examples contain no secret values, arbitrary command override, or product-hardcoded
+- [x] Documentation examples contain no secret values, arbitrary command override, or product-hardcoded
       Tess/Ultron identity.
-- [ ] CLI snippets distinguish local fleet desired-state commands from the separate gateway-backed
+- [x] CLI snippets distinguish local fleet desired-state commands from the separate gateway-backed
       `mosaic agent` catalog.
-- [ ] Migration, quarantine, lifecycle, status, and troubleshooting documentation state that values of
+- [x] Migration, quarantine, lifecycle, status, and troubleshooting documentation state that values of
       legacy sensitive keys are never printed.
-- [ ] M5 release review verifies links, schema/example validation, and that all checklist rows have
-      owner/evidence or an explicit approved deferral.
+- [x] M5 documentation validation verifies links, schema/example validation, and that checklist
+      rows have owner/evidence or an explicit approved-existing deferral.
+
+## Held downstream gates
+
+These unchecked items are intentionally outside FCM-M5-001 and are not authorized by this checklist:
+
+- [ ] FCM-M4-002 executes and evidences live cutover, canary, stopped-state preservation, and rollback.
+- [ ] FCM-M5-002 completes independent exact-head review and issues the validator certificate.
+- [ ] The exact PR head reaches terminal-green CI after independent review.