Packet: R76.S2 — Seal-audit staging file

Task: R76.S2 Chain position: Step 3 of 5 (Audit → Contract → Packet → Implement → Verify) Target: .agents/spawns/r76-phase-0-to-1-bridge/seal-audit.md

1. Execution plan

Step 1 — Frontmatter block (lines 1–13)

Ship exactly the 10-field YAML block declared in contract §2. Keep created: 2026-04-19 as an unquoted ISO date; merkle_root: TBD, seal_commit: TBD as bare tokens.

# Round R76: phase-0-to-1-bridge — Seal Audit

> **Staging document.** This file is created in Wave 4 (R76.S2) as a placeholder. Sigma fills the `TBD` fields during Phase B after running `audit_verify_chain`, `merkle_finalize`, and `merkle_root`.

Step 3 — Section 1: Phase A reference (lines 19–22)

One-line cite of the manifest with GitHub PR #152 link.

Step 4 — Section 2: Wave-by-wave PR map (lines 23–~62)

Four sub-tables matching contract §3, with merge SHAs from audit §3. Columns: Task Branch PR Merge commit. Tasks with a TBD merge SHA explicitly include the string TBD.

Sub-table	Row count	SHAs known
Wave 1 — Hygiene track A	3 (H1/H2/H3)	All 3 known
Wave 2 — Hygiene track B	3 (H4/H5/H6)	All 3 known
Wave 3 — Planning track	3 (P1/P2/P3)	All 3 known
Wave 4 — Ceremony track	2 (S1/S2)	Both TBD

Plus a Phase B artefact table with 5 rows, all TBD.

Step 5 — Section 3: Writeback chain manifest (lines ~63–72)

Prose paragraph: “11 T3 tasks + Sigma Phase A + Phase B = 13 entries.” Cite CLAUDE.md §7 ordering rule. Note that PR bodies carry queued writebacks + Sigma memory entries hold Phase A/Phase B reflections.

Step 6 — Section 4: Acceptance claims (lines ~73–82)

7 unchecked markdown checkboxes covering: T3 task status, thought_record presence, audit_verify_chain green, merkle_finalize success, merkle_root propagation into session-seal-s8.md, build/lint/test green at 1085/1085, Obsidian vault resync.

Step 7 — Section 5: Failure modes (lines ~83–90)

4 bullets reproducing Sigma contract §4 failure-mode language: chain verify fails, writeback missing, merkle finalize fails, T0 declines merge.

Step 8 — Section 6: Phase B checklist (lines ~91–107)

Verbatim code block of Sigma contract §8’s 12-item checklist, all unchecked.

Italic italicized trailer reiterating staging status + pointing back to docs/agents/sigma-orchestrator.md §4 Phase B.

2. Data dictionary — SHAs to embed

Task	Merge commit
R76.H1	`a6a6e9a1`
R76.H2	`d4a11ab6`
R76.H3	`9a42df53`
R76.H4	`a30ea6dd`
R76.H5	`92ad99a7`
R76.H6	`e455b00a`
R76.P1	`4307ba57`
R76.P2	`46935def`
R76.P3	`7c6fc8e9`

Short SHAs match the 8-char convention used in CLAUDE.md memory entries. Each row also embeds a GitHub PR link of the form [#NNN](https://github.com/LastEld/AMS/pull/NNN).

3. Style + formatting rules

Markdown GFM tables (pipes + dashes) — matches donor conventions.
Relative link to manifest: [manifest.md](./manifest.md).
Backticked code tokens for SHAs and tool names.
No emojis (CLAUDE.md default).
No hard wrapping — let Obsidian and GitHub flow.
Italic trailer terminal line only.

4. Verification targets (preview for Step 5)

wc -l output in [130, 160].
grep -c "TBD" ≥ 9 (4 frontmatter + 2 Wave-4 rows × 2 columns + 5 Phase-B-artefact rows + 7 acceptance claims + 12 checklist items — but only strict “TBD” string occurrences counted).
Frontmatter parse via node -e with gray-matter.
Test gate: npm run build && npm run lint && npm test all green, 1085/1085.

5. Risks at implement time

Risk	Response
PR links broken	Use fully-qualified `https://github.com/LastEld/AMS/pull/N` format
Frontmatter YAML invalid	Keep field values unquoted bare tokens; verify with node gray-matter
Table overflow	No line width constraint; GitHub renders fine
Line count out of target range	Adjust §3 or §5 prose for ±10 lines if off
TBD tokens inadvertently capitalized inconsistently	Always `TBD` (uppercase), no variants