adapter.md: reconcile to v1 CANONICAL

Session 3 commit 2 (atomic): frontmatter re-tag and H1 title
update landed together per the Session 3 plan at 5c2dc67 §2.2
and §5.1 Option (a). Body audit against host-boundary.md §§3-4
and freeze-v1.md §3 surfaced no drift sites; no body rewrites
were needed.

Frontmatter re-tag (v0 FROZEN → v1 CANONICAL):

- Authority: FROZEN → CANONICAL
- Version: v0 → v1
- Last Updated: 2026-03-26 → 2026-04-24
- Owner: Documentation (added)
- Change Rule: v1 only → Operational log
- Verified Against Tag: v1.0.0-alpha.1 (dropped)
- 2026-04-20 in-body pre-migration note (prior lines 10-15) removed

Doc-wide consistency-scan sites (per plan §2.2 pattern,
inherited from commit 1 f55fda2):

- H1 title (line 17): "# Adapter Contract — v0" → "# Adapter
  Contract — v1".

Consistency-scope slots that are N/A for adapter.md:

- No aspirational-FROZEN preamble line (equivalent to
  supervisor.md's "freeze-candidate specification. Treat it as
  law."); preamble is purely descriptive.
- No §N Freeze Status section to rewrite to Authority Status.
- No §N Revision History section to add a re-tag row to.
- No §N Signatures block to preserve as historical artifact.

adapter.md is substantially shorter (120 lines) and has a simpler
structural shape than supervisor.md; the full commit-1 pattern
applies in principle, but only the frontmatter + H1 title slots
have concrete sites here.

Body audit results (per plan §2.2):

- §1 Determinism Under Replay: no drift.
- §2 Capture Support: "The host writes the replay bundle and
  enriches it with host-owned provenance and effect records"
  correctly names host ownership of the capture write path.
- §3 Declared Semantic Shaping: adapter manifest structure and
  composition-validation language is v1-correct.
- §4 Scope and Responsibility: "Adapters are not responsible
  for: Owning live ingress or egress I/O processes..."
  correctly places live I/O with host.
- §5 Trust Boundary: "External nondeterminism enters through
  ingress payloads and leaves through post-episode host dispatch
  to boundary channels" verified against
  crates/prod/core/host/src/runner.rs:837 (inside the post-episode
  egress dispatch loop calling egress.dispatch_intent).
- §6 Out of Scope: no drift on bullets. §6 closing phrase
  rephrased from "These concerns are deferred beyond v0" to
  "These concerns remain deferred beyond the current contract
  scope." — version-agnostic, durable across future version tags,
  matches the forward-deferral role of the phrase (distinct from
  historical scope-boundary statements preserved elsewhere per
  §5.1 Option (a) precedent).

Pre-draft grep categorization
(grep -nE "FROZEN|v0|freeze-candidate|freeze"
 docs/orchestration/adapter.md, 5 hits pre-edit):

- Line 2 (Authority: FROZEN) — drift site, updated.
- Line 3 (Version: v0) — drift site, updated.
- Line 13 (../system/freeze-v1.md path reference inside the
  pre-migration note) — removed along with the pre-migration
  note itself; the cross-reference was transitional scaffolding.
- Line 17 (# Adapter Contract — v0) — drift site, updated.
- Line 127 (prior line number; now 120) ("These concerns are
  deferred beyond v0.") — rephrased to "These concerns remain
  deferred beyond the current contract scope." per Sebastian's
  line-120 arbitration (2026-04-24, option C: version-agnostic).

Post-edit grep: 0 residual hits.

Code-reality anchors (for Codex verification):

- Host dispatches egress-owned effects through configured egress
  channels (§5 Trust Boundary claim):
  crates/prod/core/host/src/runner.rs:837 — inside the
  post-episode egress dispatch loop, calling
  egress.dispatch_intent(intent) and mapping dispatch failures
  to HostedStepError::EgressDispatchFailure.
- Host writes the replay bundle and enriches it with host-owned
  provenance and effect records (§2 Capture Support claim):
  verified consistent with the replay-bundle enrichment path in
  host/runner.rs post-S2.2.

Prior context:

- Session 3 plan (commit 1 patterns folded): commit 5c2dc67.
- Commit 1 (supervisor.md re-tag): commit f55fda2 — established
  the doc-wide consistency-scan pattern this commit inherits.

No §6 invocation — doc-only work; no §3 symbol changes.

Author: sf19-97

docs/orchestration/adapter.md

@@ -1,20 +1,13 @@
 ---
-Authority: FROZEN
-Version: v0
-Last Updated: 2026-03-26
+Authority: CANONICAL
+Version: v1
+Last Updated: 2026-04-24
+Owner: Documentation
 Scope: Trust boundary, replay guarantees, capture requirements
-Verified Against Tag: v1.0.0-alpha.1
-Change Rule: v1 only
+Change Rule: Operational log
 ---
 
-> **Version-tag note (2026-04-20).** The frontmatter above is the
-> pre-migration tag; the body of this document describes v1 adapter
-> contract behavior as committed by
-> [`../system/freeze-v1.md`](../system/freeze-v1.md) and specified by
-> [`../system/host-boundary.md`](../system/host-boundary.md).
-> Frontmatter re-anchoring is deferred to the Session 3 doc rewrite.
-
-# Adapter Contract — v0
+# Adapter Contract — v1
 
 This document defines the minimal compliance requirements for adapter
 manifests used by adapter-bound runs.
@@ -124,4 +117,4 @@ This contract does not define:
 - Capture/adapter migration strategy across incompatible versions
 - Custom discovery/plugin systems beyond the current project/profile loading model
 
-These concerns are deferred beyond v0.
+These concerns remain deferred beyond the current contract scope.