chore(devtools): prune retired-workflow fossils (tranche 1)

[Sinity]

Summary

Deletes 5 of the 8 devtools modules the WS-C pruning ledger's tranche-1 table
listed for deletion, plus their catalog entries and tests. Three named rows
(dev_loop, mutmut_campaign/run_campaign, proof_world_real_slice)
turned out to be live or contested on verification and are explicitly
excluded — see Problem below.

Problem

.agent/campaigns/2026-08-overhaul/ws-c-devtools-pruning.md catalogs ~139
devtools modules toward a ~45k LOC / ~55 command target. Tranche 1 lists 8
"retired-workflow fossil" rows as high-confidence deletions, gated on a
per-row checklist (rule 5, "EVIDENCE BEFORE DELETION"): re-grep
.beads-hooks/, .circleci/config.yml, .claude/hooks/, scripts/, and
.github/workflows/*.yml for module invocations before deleting, because
string-keyed CLI dispatch and shell-invoked entrypoints don't show up in an
import-graph grep (this is exactly how pre_push_gate and coverage_gate
were wrongly flagged for deletion in the ledger's own 2026-08-18 correction
pass).

Re-running that checklist per row (the ledger's 2026-08-19 spot-check had
already run it, but omitted .github/workflows/*.yml from the grep target
list) found two more wrong entries before this PR was first opened, and a
third was caught afterward by cold adversarial re-verification:

• dev_loop (3,844 LOC + a cited product-side family in daemon/http.py,
  daemon/cli.py, route_contracts.py) is not dead. It's catalog-registered
  as workspace dev-loop with a large flag surface
  (--prepare/--launch-daemon/--capture-cli/--receiver-smoke/etc.), has
  a 1,629-line test file, and a 757-line doc (docs/dev-loop.md) linked from
  docs/README.md's nav — last touched by a real feature commit 5 days before
  this PR (feat(devloop): close remaining polylogue-5en gaps (stale-run detection, MCP recipe) #3333, "close remaining polylogue-5en gaps"). The ledger's citation
  ("devloop workflow explicitly retired, CLAUDE.md: do not resurrect") is a
  name collision: CLAUDE.md's retirement note is about the unrelated bespoke
  Beads/conductor-packet workflow, not this branch-local
  daemon/browser-capture preflight tool.
• mutmut_campaign + run_campaign (624 LOC) are two unrelated modules
  the ledger conflated by name similarity. mutmut_campaign.py (catalog:
  bench mutation) is invoked weekly by
  .github/workflows/mutation-testing.yml (devtools bench mutation run "$campaign") — exactly the grep the spot-check missed by skipping
  .github/workflows/. run_campaign.py (catalog: bench synthetic) is a
  separate, live-tested command
  (test_benchmark_campaigns.py::test_run_campaign_skips_seed_archive_for_daemon_live)
  driving the ledger's own NEEDS-EVIDENCE/default-keep large_archive_generator
  • synthetic_benchmark_runtime modules; it has nothing to do with mutation
    testing.
• AUDITED AND EXCLUDED (found by cold verification after this PR's first
  push, restored in a follow-up commit): proof_world_real_slice (440 LOC +
  test). The ledger's row cited it as belonging to the closed jxe uplift
  campaign, but the module's own docstring and its test both cite
  polylogue-212.11 instead — an open, P3 bead whose notes name this
  tool as "the harness half of the real-archive-data extension" with a
  pending, unpromoted deliverable. Same name-collision failure class as the
  dev_loop/mutmut_campaign catches above, just missed on this row during
  the original per-row pass. Restored verbatim (module, test, and the
  demo real-slice-screen CommandSpec) from before deletion.

All three exclusions were reported to the coordinator (the first two before
this PR was opened, the third as soon as cold review surfaced it).

Solution

Deletes the remaining 5 rows, each independently re-verified clean (no
hook/CI/doc/production references beyond the module's own catalog entry and
test file):

• claim_vs_evidence.py + claim_vs_evidence_evidence.py (+ both test
  files) — the polylogue-sru campaign closed with terminal artifacts
  2026-07-06; this CLI re-proved an already-recorded claim. The durable
  production primitive it wrote through, PublicClaimProjection
  (polylogue/insights/measurement/public_claims.py), is untouched and lives
  independently. Trimmed docs/findings/claim-vs-evidence.md's now-dead
  "Reproduce"/"Regenerate" sections (they invoked the deleted command) while
  keeping the finding's substantive text as a frozen historical record — the
  2026-08-14 purge (refactor: remove self-attesting campaign bureaucracy #3950) had already retired "the closed claim-vs-evidence
  campaign's private-report/calibration/publishing harness" in spirit; this
  PR finishes that.
• turso_probe.py (+ test) — Turso storage-backend research (research(storage): evaluate SQLite to Turso Database backend swap #2257/research(storage): benchmark Turso ops workload (#2257) #2281,
  June) concluded; direction settled on SQLite independence + Sinex mode.
• resume_ranking_eval.py (+ test) — orphan: no catalog entry, no importers
  beyond its own test.
• help_latency_probe.py (no dedicated test file existed) — one-shot
  CLI-latency research; not wired into any gate.
• temporal_read_profile.py + temporal_archive_aggregates.py (+ both test
  files) — one-shot read-profiling research (July 2).

Each deleted module's CommandSpec was removed from
devtools/command_catalog.py, then devtools render devtools-reference
regenerated docs/devtools.md. No CLAUDE.md tooling-list lines named any of
the six deleted commands, so none needed trimming there.
proof_world_real_slice's CommandSpec was restored to the same spot in the
follow-up commit and devtools render devtools-reference re-run.

Verification

• devtools render all --check — exit 0, no out of sync surfaces.
• devtools verify --quick — "status": "success", "exit_code": 0 (run
  again after the proof_world_real_slice restore, still green).
• devtools verify (full, complete-corpus) — "status": "success",
  "exit_code": 0, "terminal_green": true, "complete_corpus_covered": true, "non_green_count": 0, "release_baseline_allowed": true.
• devtools test tests/unit/devtools/test_proof_world_real_slice.py — 20/20
  passed, confirming the restored module's tests are intact.
• python -m devtools.verify_doc_commands — 67 doc files scanned, no stale commands (caught and fixed one accidental literal reference to the
  now-deleted claim-vs-evidence command in the trimmed findings doc).

Anti-vacuity: pure deletion (plus one restoration); reachability evidence per
surviving row is in the ledger plus the re-verification above (all rows
independently re-grepped against .beads-hooks/, .circleci/config.yml,
.claude/hooks/, scripts/, .git/hooks/, and .github/workflows/*.yml,
and cross-checked against docs/ and git log recency).

Bead disposition matrix

This PR does not close, claim, or otherwise mutate any Beads issue — it is
pure code/doc deletion against the campaign's markdown ledger, not a Beads
tracker item. mutated_beads is empty; using the self_contained scope
carrier. polylogue-212.11 is cited as evidence for the
proof_world_real_slice exclusion but is not touched, claimed, or closed by
this PR.

Candidate follow-ups for the coordinator (not closed by this PR):

Item	Note
Tranche 1 revision	The ledger's tranche-1 table and its "Est. ~8.6k LOC" total need updating to remove dev_loop, mutmut_campaign/run_campaign, and proof_world_real_slice as confirmed-live/contested, plus record the .github/workflows/ gap in the spot-check methodology so future tranches don't repeat it.
Tranche 2 execution	Unblocked to proceed independently; nothing in this PR touches tranche-2 rows.

Verification commands run

devtools render all --check
devtools verify --quick
devtools verify
devtools test tests/unit/devtools/test_proof_world_real_slice.py
python -m devtools.verify_doc_commands

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[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: a2b02124-e3d9-4fa8-8265-ddbac275ee9e

---

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.}