schickling assistant/2026 09 05 harness v3 activation

[schickling-assistant]

Problem

A v3 reader and dormant adapters do not improve live producer truth until every writer and terminal owner can emit the tuple safely.

Goal

Integrate the reviewed slices and activate v3 through one writer selector, with legacy reads and rollback proofs intact.

Decisions

• supersede the single v2 selector; do not add a second switch
• state condition, ask, and conversation as one tuple
• centralize terminal bootstrap in provider_session::write_terminal
• preserve standing conditions on exit; bootstrap only an unstated axis
• keep delivery evidence independent from condition/disposition
• retain explicit v2 test seams and the one-way schema fence

Verification

• cargo test -p st2 --lib: 879 passed; only three merge-base-identical environment/timing tests failed
• the Nix build used by dotfiles passed all 881 st2 library tests and integration suites
• cargo check -p st2 --all-targets
• delivery migration suite passed
• nix flake check --no-build
• Darwin CI passed; Linux CI was still running at handoff
• independent review completed with no remaining P0-P2 findings

Complexity

Integration centralizes the one terminal bootstrap rule; adapter reducers remain the single native-event authority.

Concerns

This PR contains the integration commits so sibling review slices shrink as they land.

Friction & bottlenecks

Local teardown fixtures cannot observe provider readiness in this agent environment and fail identically on #469. One inherited #464 invariant names an absent resource test.

Follow-ups

Dotfiles #2509 pins this exact commit after Fractal #2501. Live activation and seat drain require separate approval.

References

Depends on #470. Integrates #471 and #474-#478.

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