[noctem-o]

Ticket 0009: cog anchor reconcile

Scans a directory tree for sealed bundles, folds the anchor log into an AnchorSet projection, and anchors exactly the sealed-but-unanchored remainder. Idempotent by construction: the second run anchors nothing. Deliberately the first consumer of anchors — it validates the seam by using it.

• AnchorSet (cog-anchor): BTreeSet fold over LogReader::replay; exhaustive Payload match (no _ => {}); replay verifies the chain first, so a tampered log refuses to reconcile.
• read_verifying_key (cog-anchor): read-side companion to generate_key_file, same 64-lowercase-hex rules.
• Scan detects bundles by the four witness manifest filenames and reuses the emitters'"'"' per-kind AnchorRequest builders (visibility bump only) — single source of truth for manifest→request. Roots are re-validated reconcile-side (64 lowercase hex) because reconcile anchors bundles it did not just verify.
• Deterministic: candidates sorted by path before acting. Exit nonzero only for anchoring failures; unparseable/foreign bundles are reported and skipped.
• Reviewer fix on the Codex implementation: kernel-arm profile gate (the kernel request builder debug-asserts a profile that untrusted on-disk manifests can violate; hostile input must skip, not panic).

P2 remediation (codex bot review of #318/#319)

1. Flags beat config (Ticket 0007b: anchor emission at the kernel witness seal point #318): complete --anchor-key/--anchor-log no longer consult deadbolt-anchor.toml, so a malformed config cannot veto explicit paths.
2. Init preflights the log before minting a key (Ticket 0007b: anchor emission at the kernel witness seal point #318): missing log parent / existing non-empty log are refused before key creation; if the open still fails, the freshly minted key is removed. No more stranded keys blocking re-init.
3. Kernel anchor gate runs the CLI verifier'"'"'s source preflight (Ticket 0007b: anchor emission at the kernel witness seal point #318): symlinked/reparse-point source artifacts are refused before the library verifier (which follows them) — the gate is no longer weaker than cog verify kernel-witness.
4. Pending markers moved beside the run dir (Ticket 0008: fan anchor emission out to the remaining seal points #319): <run>.pending-anchor.json. Anchoring debt is operational state, not evidence; the observation verifier'"'"'s strict uncommitted_artifact_present no longer fails a sealed bundle whose anchor attempt failed. Kernel stale-artifact clearing follows the marker.

Validation (run on Windows by the reviewer)

• cargo test -p cog-anchor: 9/9 pass (incl. tamper-refusal)
• cargo test -p cog-cli: 545 pass / 7 fail — the 7 are the known pre-existing style_plan snapshot failures on native Windows, identical on clean main
• New tests: reconcile idempotence / mixed-state / tamper / uppercase-root / determinism / foreign-kernel-profile; flags-over-malformed-config; init-preflight-no-stranded-key; kernel-gate symlink refusal (symlinks supported on the runner — executed, not skipped); observation bundle with anchoring debt still verifies Pass
• cargo tree -i magpie-log: cog-anchor remains the sole direct dependent (pin 7c7f043 unchanged)

Codex (gpt-5.5) implemented ticket 0009 (.agent-runs/20260705T093018Z-1991177716); Claude reviewed, applied the reviewer fix and P2 remediations, and ran validation. Merge is George'"'"'s call, as always.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4dcca9793c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Clear sibling pending markers after successful seals

When the marker is moved beside the run directory, rerunning a previously failed observation/codelet/transaction seal with a valid anchor configuration no longer overwrites or removes the old <run>.pending-anchor.json; those success paths return Anchored without calling delete_pending_anchor_marker_if_present (kernel has a separate stale-marker cleanup). This leaves operational debt visible even though the bundle has just been anchored, so the non-kernel seal paths should clear the sibling marker on successful anchoring as reconcile does.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Verify bundles before anchoring them

For a scanned bundle whose evidence was tampered after sealing, this path builds an AnchorRequest and only checks that the requested root is lowercase hex before appending it. For example, changing witness_root.txt in an observation/codelet/transaction bundle to any other 64-character lowercase hex value is caught by the normal bundle verifiers as witness_root_mismatch, but reconcile will still anchor that false root because it never runs those verifiers before this format check. Reconcile should gate each candidate with the same per-kind verification used by the live seal paths before writing an anchor.

Useful? React with 👍 / 👎.