feat(harness-state): add v3 reader foundation

[schickling-assistant]

Problem

Harness readers cannot distinguish legacy absence from a v3 fault, ask, or conversation axis.

Goal

Introduce a strict, forward-compatible v3 reader and one normalized disposition without changing writer bytes.

Decisions

• reserve v2 for Implement immutable agent IDs and mutable addresses coherently #464 identity and use v3 for condition semantics
• keep v1/v2 condition explicitly absent
• derive { state, attention, primaryAction } once for roster, catalog, and Doctor
• reject unknown schema versions while tolerating additive fields inside v3

Verification

• harness-state reader suite: 55 passed
• agents, catalog graph, Doctor, and status suites passed
• nine golden fixtures cover supported record shapes
• independent review completed with no remaining P0-P2 findings

Complexity

The added types encode wire distinctions that must not collapse at consumer boundaries.

Concerns

Writer activation is intentionally absent; this is the reader-first slice.

Friction & bottlenecks

Linux draft CI exceeded its 90-minute job window and was cancelled; Darwin passed. Focused local suites pass.

Follow-ups

#470 adds the producer API. #479 activates v3 after every adapter is ready.

References

Depends on #464.

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