refactor: shrink devtools and split archive query reads

[Sinity]

Summary

Shrink duplicated developer tooling and split archive query reads on feature/overhaul/integration-batch. This branch contains the accepted timestamp-authority and public-origin projection chains in addition to the earlier integration batch.

Problem

The branch previously carried a self-contained PR carrier even though it includes work that overlaps open Beads. That made the GitHub summary weaker than the authoritative tracker and obscured which remaining work is intentionally outside this merge.

Solution

• Split terminal archive query reads from ArchiveStore while retaining the public delegates and row-type compatibility.
• Consolidate MCP, CLI, user-tier, and convergence test setup without dropping behavioral coverage.
• Remove retired devtools proof surfaces and unreachable production modules.
• Add ordered workspace-lane integration with explicit target, Git-state, conflict, and timeout handling.
• Add provenance-checked pre-push quick-receipt reuse with safe fallback to fresh verification.
• Preserve replay cursor continuity and operation-state compatibility across resumable runs.
• Repair timestamp authority across acquisition, live admission, replay, and raw revision paths.
• Derive public origin filters and discovery projections from OriginSpec across CLI, DSL, MCP, and completion.
• Preserve async admission through executor completion and merge delegation evidence deterministically.

Verification

Focused managed tests were run for the touched storage, query, devtools, replay, MCP, source, admission, timestamp, and origin surfaces. The exact branch head also passed devtools verify --quick. These checks do not claim a complete-corpus run; devtools verify --all was not run.

Bead disposition

Bead or workstream	Disposition	Evidence	Remaining scope
Replay continuity and cursor persistence	Partial	Focused replay and maintenance tests on the exact branch	Continue campaign acceptance and live-proof work through the authoritative Beads graph
Archive query-read split	Satisfied for this PR	Focused archive query/storage tests and quick verification	None in this PR
Public origin projections	Satisfied for this PR	Origin, query, CLI, MCP, completion, and discovery focused tests	None in this PR
Timestamp authority	Satisfied for this PR	Acquisition, replay, raw-admission, and revision focused tests	None in this PR
Native reindex campaign control	Not claimed	Current Beads status is open after independent re-review	Complete the remaining provenance, formula, census, DAG, and malformed-input contracts in its owning workstream
Other open maintenance and blob-retirement Beads	Not claimed	Current Beads status remains authoritative	Continue their independent acceptance and documentation work; this PR does not close them

The branch is a coherent integration batch, but it does not claim completion of the native reindex campaign or unrelated open Beads. The current Beads export is the authority for those residual scopes.

[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: 2e9245c3-6517-4416-8b98-91a027a42e7a

---

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

Here are some automated review suggestions for this pull request.

Reviewed commit: 466a0cab45

ℹ️ 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]

Document the new integration command in AGENTS.md

Add devtools workspace integrate to the standalone AGENTS.md command list in this change. The new command is registered here and documented in docs/devtools.md, but a repository-wide search finds no corresponding AGENTS.md entry, so agents relying on the mandated standalone instructions will not discover or use it. The repository explicitly requires every devtools extension to be listed there in the same change.

AGENTS.md reference: AGENTS.md:L512-L513

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Derive the commit range from the pinned source SHA

Use the already-resolved source SHA here instead of resolving source_ref again. In the parallel-lane scenario this command is designed for, a lane can advance its branch between _commit_sha()/merge-base and this rev-list; the new tip then bypasses the ancestry check performed against the old SHA, so commits from an unvalidated or divergent range can enter the integration plan. Passing f"{target_head}..{source}" keeps planning bound to the exact commit that was checked.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Translate invalid operation IDs at the public surfaces

Convert this new ValueError into each surface's typed invalid-argument response instead of allowing it to escape. For example, polylogue ops maintenance run --operation-id ../escape and run-preview reach this call through _run.py:162 without a catch; the similarly changed MaintenanceOperationRegistry.get_operation() is also called unchecked by _status.py:72 and the MCP status dispatcher at server_cutover.py:2037. Consequently ordinary hostile or mistyped user input now becomes an unexpected CLI/MCP exception rather than the structured error behavior already implemented for the daemon HTTP route.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a10765947b

ℹ️ 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]

Keep timestamp intervals ordered on ordinary replacements

When a non-force, non-append replacement carries a producer created_at later than the currently stored updated_at—for example, after a provider corrects or misreports the creation time—this branch unconditionally advances created_at_ms, while the updated_at_ms CASE falls through to preserving the old value because both force_replace and merge_append are false. The resulting row has created_at_ms > updated_at_ms, despite normalization only guaranteeing that the incoming pair is ordered; clamp the retained update time to the selected creation time or only replace creation time when stored provenance is known to be derived.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Store the campaign anchor in the checkout

In a shallow checkout such as git clone --depth=1, this fixed ancestor object is absent, so _source_evidence() converts git show's failure into a campaign-source-anchor finding whenever the live export contains the campaign marker. The required devtools lab policy bead-graph --export .beads/issues.jsonl gate therefore exits 1 for an otherwise valid graph; keep the immutable evidence in a tracked file available at HEAD, or explicitly fetch the required object before validating it.

AGENTS.md reference: AGENTS.md:L345-L347

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bd7b137520

ℹ️ 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]

Keep unknown-export available as a public origin filter

When an archive contains fallback sessions, this flag removes unknown-export from public_origin_tokens(), which now drives both DSL and parameter validation, so queries such as origin:unknown-export fail instead of returning those stored sessions. The repository defines unknown-export as a public query-origin token; keep it accepted by query validators even if completion visibility needs a separate policy.

AGENTS.md reference: AGENTS.md:L296-L300

Useful? React with 👍 / 👎.