feat(harness-state): add v3 producer API

[schickling-assistant]

Problem

Five adapters need one typed write contract before v3 bytes can be activated safely.

Goal

Provide frames, faults, exact clears, conversations, and typed refusals while production remains on v2.

Decisions

• one writer selector only
• closed fault categories with provider-prefixed open codes
• exact (category, code) paired clears
• positive typed progress for clear-all
• preserve PTY fences and semantic fault clocks

Verification

• 66 harness-state tests passed
• Linux and Darwin CI passed
• Darwin-only heartbeat timing failure was root-caused and replaced by a deterministic same-iteration proof
• independent review completed with no remaining P0-P2 findings

Complexity

The API centralizes validation and refusal semantics that would otherwise diverge across five adapters.

Concerns

Condition operations intentionally refuse on v2; adapters retain their exact legacy path until #479.

Friction & bottlenecks

Draft CI is long-running on both architectures; the final run passed.

Follow-ups

Adapter PRs #474-#478 and activation PR #479.

References

Depends on #469.

Posted on behalf of @schickling

field	value
agent_identity	dev3.direct.omp.9exwnk6h
session	dev3.9exwnk6h
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.1.7
agent_runtime	OMP 18.1.7
tooling_profile	dotfiles@931583a

[schickling-assistant]

Parking this PR (closed, branch kept) per decision Q1 incidents-first in seat dev3.direct.omp.43sz6ujq (record 2we9ak / answer 8b0ow1, 2026-09-06): the harness-state v3 stack ships only once a named consumer requirement or incident calls for the fault/ask/conversation axes.

Findings that shape re-entry (evidence: an independent 12-reviewer pass + orchestrator reports in the orch worktree, tmp/orch-reconcile/reports/{stack,migrations,complexity}.md):

• The stack bases on the CLOSED Implement immutable agent IDs and mutable addresses coherently #464 branch; the harness-state.v2 it supersedes exists only there, never on main. Re-entry rehomes feat(harness-state): add v3 reader foundation #469's real content (one commit, df327b5, +2773/-120) onto main after Split the agent route from its durable key: mutable address, optional immutable id #468 -> feat(agent): mutable address, immutable positional identity #467, and drops the v2 layer (SCHEMA_V2, EMIT_SCHEMA_V2, RecordSubject, v2 fixtures).
• Policy Q2 previous-release-rollback: writers emit the newest format only; no compile-time gates (EMIT_SCHEMA_*, writes_condition_axis()) and no rollback floors; readers keep tolerant arms with a named deletion trigger.
• Activation re-enters as an activation-only PR (schickling assistant/2026 09 05 harness v3 activation #479's own delta is +916/-318); schickling assistant/2026 09 05 harness v3 activation #479 as opened is the union of feat(delivery): add durable delivery ledger #471 + five adapters and would be reviewed twice.
• feat(delivery): add durable delivery ledger #471 (delivery ledger) is NOT parked: it is independent of v3 and will be rebased onto main by the integrator lane.

Posted on behalf of @schickling

field	value
agent_identity	dev3.direct.omp.43sz6ujq
session	dev3.43sz6ujq
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.1.7
agent_runtime	OMP 18.1.7
tooling_profile	dotfiles@39a19af