docs(fleet): add operator configuration guide

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

docs/fleet/operations/env-quarantine.md

@@ -0,0 +1,20 @@
+# Environment Quarantine Operations
+
+Legacy `<name>.env` is input evidence, never current launch authority. Projection preparation classifies it deterministically:
+
+- generated roster keys → discard and regenerate;
+- allowed strict local keys → relocate to private `.env.local`;
+- malformed, duplicate, unknown, sensitive-looking, shell-bearing, unsafe, or command-override entries → move the legacy input to private `.env.quarantine`.
+
+## Safe response
+
+1. Stop and read the stable error code and reported key name/hash. Do not request or paste the value.
+2. Confirm the canonical roster contains the intended non-sensitive desired state.
+3. If the key is an allowed local machine-data field, place only its validated data form in `.env.local` under private permissions.
+4. Remove unsupported intent rather than translating it into commands, channels, secret references, or unknown `MOSAIC_AGENT_*` keys.
+5. Regenerate `.env.generated` from the roster and rerun a dry-run/verification gate.
+6. Retain quarantine evidence privately until the operator's normal retention process permits removal.
+
+The launcher never reads quarantine. Public/JSON diagnostics expose stable code, key name where safe, and SHA-256 only—never a legacy sensitive value, credential, rejected command, or full line. Quarantine does not prove remediation, backup, migration, or rollback.
+
+See [generated launch chain](../concepts/generated-env-launch-chain.md), [generated environment boundary](../reference/generated-env-boundary.md), and [migration field disposition](../migration/v1-to-v2.md#field-disposition).

docs/fleet/operations/reconcile-and-recover.md

@@ -7,6 +7,8 @@
 3. Resolve stale generation, ownership mismatch, unsafe path, projection validation, or unmanaged-session findings before applying.
 4. Run `mosaic fleet apply --expected-generation <n>` only after the plan is understood.
 
+This is per-generation convergence, not a rolling canary. Executable canary cutover/rollback remains held for FCM-M4-002; rolling local release evidence remains FCM-M5-002. Do not approximate either with repeated live apply commands.
+
 The reconciler uses the exact roster tmux socket, exact holder session, private installation holder identity, and the complete expected global environment. For mutations it acquires its exclusive lock before rereading the canonical roster and fencing its generation; only that under-lock roster drives validation, planning, projections, and lifecycle effects. Before effects, its exclusive lock proves real private `MOSAIC_HOME` and `fleet` ancestors, uses a private `0600` lock leaf, and binds cleanup to the created file identity and ownership token. A fake holder, contaminated global environment, missing identity, unsafe lock path, or unmanaged session fails closed. It does not adopt, kill, or rename any unproven session. A crash can leave a stale lock for explicit operator inspection; reconciliation deliberately does not guess ownership or remove it.
 
 ## Partial results

docs/fleet/operations/systemd-tmux-troubleshooting.md

@@ -0,0 +1,24 @@
+# Systemd and tmux Troubleshooting
+
+Start with read-only `mosaic fleet status`, `doctor`, and `verify`. Do not manually adopt, rename, terminate, or recreate sessions while ownership is ambiguous.
+
+## Decision table
+
+| Finding                         | Meaning                                              | Safe next step                                                                        |
+| ------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| Empty roster `tmux.socket_name` | Literal default tmux server                          | Do not substitute the named `mosaic-fleet` socket. Use roster-derived commands only.  |
+| Non-empty socket                | Exact named socket                                   | Never target another socket or infer a per-agent socket.                              |
+| `holder: missing`               | Required exact holder absent                         | Inspect installation/projection readiness; do not create an unproven holder manually. |
+| `ownership-mismatch`            | Holder identity or global environment differs        | Stop. Verify private install identity and managed paths before retry.                 |
+| `missing-session`               | Desired-running roster agent lacks exact session     | Check service/runtime preconditions; review apply dry-run.                            |
+| `unexpected-session`            | Desired-stopped roster agent still has exact session | Confirm ownership; only reconciler may target the exact proven roster member.         |
+| `disabled-running`              | Disabled roster member is observed running           | Inspect and reconcile only after ownership proof.                                     |
+| `unmanagedSessions`             | Unknown session exists on configured named socket    | Report and investigate separately. Reconciler will not kill or adopt it.              |
+| stale/concurrent generation     | Desired state changed since plan                     | Reload roster/generation and recompute the plan.                                      |
+| stale or ambiguous lock         | Prior writer/cleanup cannot be proven                | Inspect ownership; do not blindly remove the lock.                                    |
+| projection failure              | Derived files incomplete                             | Keep roster as authority and regenerate projections.                                  |
+| lifecycle failure               | Projections complete, runtime convergence incomplete | Inspect the exact owned resource, then rerun with current generation.                 |
+
+Systemd state, tmux state, heartbeat, and generated files are observations/projections, not alternate desired state. Explicit apply/reconcile honors stopped/disabled intent, but current unit enablement and launcher projections do not yet prove lifecycle-safe reboot; inspect unit enablement before reboot and treat stopped/disabled boot preservation as an FCM-M3-002 hold. Current roster-v2 status commands also do not read heartbeat files. Executable gates do not provide site cutover/rollback or package asset-revision repair.
+
+Errors and troubleshooting output never print legacy sensitive values, credential contents, or privileged command text. Use stable codes, key names/hashes, exact roster identities, and bounded recovery actions. See [status and drift](../reference/status-and-drift.md) and [reconcile and recover](reconcile-and-recover.md).

docs/fleet/operations/upgrade-assets.md

@@ -0,0 +1,18 @@
+# Upgrade and Installed-Asset Drift
+
+Fleet source assets and installed assets can differ after an update, but FCM-M5-001 does not add a trustworthy source-versus-installed revision detector or refresh command. Do not infer freshness from checkout presence, timestamps, generated environment files, running sessions, or a ready migration preview.
+
+## Current safe boundary
+
+- The canonical roster remains authority and must survive package/framework refresh.
+- Generated projections are rebuilt from that roster after the installed contract is independently verified.
+- Operator `roles.local`, `.env.local`, and private quarantine evidence are not generated assets and must not be overwritten.
+- Baseline roles, schemas, examples, service presets, launcher helpers, and systemd templates must move as one reviewed release set.
+- Remote/connector inventory and `mos-comms` are not promoted into permanent architecture by an update.
+- No update may start an agent persisted stopped, adopt an unmanaged session, or bypass generation/ownership checks.
+
+## Explicit hold
+
+FCM-M5-002 owns deterministic asset-drift checks, safe package/update refresh evidence, rolling local canary, independent validation certificate, and release evidence. Until that card lands, this page is an operational hold rather than an executable procedure: use the repository/release review path, preserve backups, and do not claim source/installed parity without exact revision evidence from the future validator.
+
+See [approved deferrals](../../reports/deferred/758-fleet-config-deferrals.md) and [backup/restore boundary](backup-restore.md).