docs(harness): reconcile implementation slate with lease-free production

[chughtapan]

What changed

• Reconciles the non-normative Harness implementation slate with lease-free production after refactor!: remove app principals, dispatch leases, and at-rest encryption; add programmable simulator links #941 and the daemon receive/reply foundation in Add daemon-backed HarnessClient receive path #942.
• Separates landed production from open candidates refactor(client): isolate presentation state #943 through feat(harness): start conversations through MCP #948 and from the target state.
• Records participant enrichment as loopback-MCP-only presentation data passed to the HarnessClient implementation; the canonical production Conversation and main WebSocket wire remain unchanged.
• Records the still-unselected production profile-to-MCP acquisition and durable checkpoint composition instead of inventing them.
• Makes the clean-slate prerequisites explicit: v2/transcript and v2/harness remain scaffolds, and Transcript/Ledger plus the remaining management, ingress, HarnessClient, checkpoint, and plural-action contracts must be admitted before their corresponding implementation slices.
• Flags existing v2 authority drift around production leases and registration recovery without changing an ADR or normative spec.

Why

The previous slate still described dispatch leases, conversation_busy, server grants, duplicate-reply suppression, and selected production registration recovery. Those claims no longer match current main or do not have a main-owned contract. The implementation handoff needs to describe current evidence without silently turning unresolved mechanics into requirements.

Scope

This is an implementation-state and sequencing update only. It does not modify an ADR, normative specification, main-wire schema, runtime code, or clean-slate contract.

Validation

• pnpm nx run workspace:precommit
• pnpm docs:check:drift
• git diff --check
• Independent factual review, followed by a clean re-review after both findings were corrected

Related

• Tracks One per-AgentId moltzapd and structurally compatible HarnessClient implementations #926
• Production candidate stack: refactor(client): isolate presentation state #943, feat(harness): add MCP read plane #944, feat(harness): add client context reconstruction #945, feat(harness): project client-owned turns #946, feat(client): package moltzapd process #947, feat(harness): start conversations through MCP #948
• Upstream v1 control-plane simplification: refactor!: shrink the v1 control plane to a router #924