chore(beads): complete native campaign migration

[Sinity]

Summary

Record the native Beads campaign migration and retire the deleted incident ledger. This PR is a migration record and staged adapter boundary, not campaign completion.

Problem

The original PR body claimed the native-control migration was satisfied, but the authoritative Beads state reopened that Bead after independent review. The current graph exists and carries the historical scope, yet its provenance and validator contracts remain incomplete.

Solution

• Preserve the guarded native Beads application and the graph-backed historical scope.
• Retire the obsolete ignored campaign directory and incident ledger without introducing a second authority.
• Keep the Polylogue AgentCTL adapter as a staged, source-cited boundary with no invented operation.
• Retain existing verification and command ownership until a direct replacement is demonstrated.

Whole-Bead disposition matrix

Bead	Disposition	Evidence	Remaining scope
polylogue-reindex-native-control-plane	Partial	Native root, workstream graph, historical bindings, and reviewed edges exist; current Beads status is open	Prove real formula materialization, immutable or source-backed provenance, graph-bound census, complete five-stage molecule DAG, strict stage authority, demotion resistance, malformed-container findings, and status-aware merge accounting
polylogue-incident-coverage-ledger	Satisfied	The obsolete ledger is deleted and archive verification remains registry-owned	No replacement ledger
polylogue-agentctl-adapter	Partial	Staged source-cited boundary exists	Wait for the prerequisite archive-location contract, a published source-scoped owner route, caller cutover, and deletion evidence

Verification

The migration and graph checks recorded by the original implementation remain useful evidence. They do not prove the reopened native-control acceptance criteria. No live archive action or AgentCTL route cutover is claimed by this PR.

The authoritative Beads export and current independent review findings supersede the earlier completion wording.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8559b05d-3f0d-4ad0-9c09-00a377c85a34

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/Sinity/polylogue/blob/0792f9fd23a757add617d68111dc0e9153213f57/.beads/issues.jsonl#L199
Revalidate the campaign after adding the adapter member

The successful 151-member parity validation recorded on the migration Bead predates this adapter (01:18 versus its 01:20 creation), yet the adapter is labeled as a campaign/workstream member without the historical membership marker and is not one of the ten declared controls. It therefore becomes the extra/unowned campaign row that acceptance criterion 8 says the validator must reject; either give it an explicit owned-control classification or keep it outside this campaign, then rerun parity before treating the migration as complete.

AGENTS.md reference: AGENTS.md:L410-L415

---

https://github.com/Sinity/polylogue/blob/0792f9fd23a757add617d68111dc0e9153213f57/.beads/issues.jsonl#L1
Keep the migration open until its validator is durable

After the old campaign plane is deleted, no executable campaign validator remains in the repository: a repo-wide search finds the WIP-limit keys and parity requirements only in Beads prose, while this note records only a one-time validation run. Subsequent label, edge, batch, lane, or merge-train changes can therefore violate acceptance criterion 8 without any gate detecting them; leave this Bead partial until the stateless validator is checked in and wired into verification.

AGENTS.md reference: AGENTS.md:L410-L415

---

https://github.com/Sinity/polylogue/blob/0792f9fd23a757add617d68111dc0e9153213f57/.beads/issues.jsonl#L1
Add the promised thematic-batch formula before closing

A fresh checkout contains no thematic-batch formula definition under .beads or elsewhere—only prose referring to one—so agents cannot instantiate the required prepare → implement → verify → merge-gate → disposition workflow after the former control plane is removed. Acceptance criterion 4 is therefore still outstanding and should be implemented or explicitly deferred rather than closing this Bead as complete.

AGENTS.md reference: AGENTS.md:L410-L415

---

https://github.com/Sinity/polylogue/blob/0792f9fd23a757add617d68111dc0e9153213f57/.beads/issues.jsonl#L1
Run the repository bead-graph gate before closing

This closure dismisses acceptance criterion 7 because the old devtools lab spelling no longer exists, but the current command catalog registers its replacement as devtools verify bead-graph, and the reported devtools verify --quick run does not execute that lab-tier step. The substituted bd graph check and offline topological check do not cover the repository gate's dependency-kind, parent-cardinality, archive-verification-registry, and live-proof-registry checks, so this Beads delta was closed without the required validation; run the current gate or repair its command surface rather than treating the criterion as obsolete.

AGENTS.md reference: AGENTS.md:L345-L350

ℹ️ 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".

[Sinity]

Actionable. I reopened polylogue-reindex-native-control-plane rather than treating the obsolete devtools lab spelling as a waiver. The current branch will add the required native thematic-batch formula and a read-only stateless campaign validator, run devtools verify bead-graph --export .beads/issues.jsonl --json, rerun campaign parity after explicitly classifying the AgentCTL staging edge, and preserve structured dependency rationale. This PR remains unmerged until those changes and their verification are present.

[Sinity]

The migration state from this PR has been reconciled into master at e41d7195f, including the current Beads graph and the reviewed partial dispositions. The PR branch is now stale relative to master and its quick-gate result is not an admission signal for the current tree. The underlying native-control and AgentCTL Beads remain open for their explicitly listed acceptance criteria; those residuals are recorded in live Beads notes. This PR is therefore being closed as superseded by the reconciled master state.