Skip to content

chore: record waves 1-3 GitHub-archived repos in the catalog - #280

Merged
saagpatel merged 2 commits into
mainfrom
chore/catalog-archive-reckoning-waves1-3
Oct 13, 2026
Merged

saagpatel merged 2 commits into
mainfrom
chore/catalog-archive-reckoning-waves1-3

Conversation

@saagpatel

Copy link
Copy Markdown
Owner

What

Records the repos archived on GitHub in reckoning waves 1-3 in the auditor's local records. It follows #279, which did wave 0.

Catalog (config/portfolio-catalog.yaml): 38 rows get lifecycle_state: archived and operating_path: archive. Earlier states: 25 dormant, 7 active, 6 manual-only.

  • Wave 1: canon-court, DNSWatcher, OddworksCabinet, Premise
  • Wave 2: ApplyKit, Chronomap, stockpulse, TerraSynth, AIWorkFlow, AssistSupport, Calibrate, Chromafield, Echolocate, HowMoneyMoves, IncidentMgmt (repo IncidentManagement), LifeCadenceLedger, Nocturne, prompt-englab, Redact, RedditSentimentAnalyzer, ResumeEvolver, RoomTone, ScreenshotAnnotate, Seismoscope, SignalFlow, SmartClipboard, SnippetLibrary, TideEngine, Wavelength, GhostRoutes, ITServiceHealth, job-search-2026, JSMTicketAnalyticsExport, Terroir
  • Wave 3: _machine/machine-control-tower, operating-memory-os, operator-os-docs, knowledgecore

Rows were matched through each repo's local path, not just its name. KBFreshness's row (KBFreshnessDetector) was already archived. Five flipped repos have no catalog row: warm-workbench-archive, renovate-config, astra-september-snapshot-hardened, SecondBrain and living-studio-bench.

Follow-on catalog fixes:

  • Notes: OddworksCabinet, machine-control-tower, operating-memory-os and operator-os-docs had notes describing live or pending use. They now give history only, plus the archive date.
  • TideEngine: its automation_eligible goes to false. That flag isn't gated by lifecycle, so the repo would otherwise stay in the automated action-sync set while read-only on GitHub.

Notion map (config/notion-repo-map.json): drops the 23 keys belonging to these repos, taking the file from 90 to 67 keys.

Tests:

  • Five repos leave the live manual-only pin, and the archived-row pin now covers the 13 rows that were active or manual-only.
  • The Tier 0 generated-output pin now expects ApplyKit to derive archived. ApplyKit stays in the fixture, so the coverage counts don't change.

Deliberately untouched

operator-os-explainer was flipped in wave 3, but its row and Notion key stay until after the next nightly security receipt. evals, portfolio-index, cross-system-smoke, harnessbench, transcript-autopsy, proof-pr and sovereign are unchanged. Wave 4 has no GitHub flips yet.

Validation

  • pytest tests/: 3777 passed, 2 skipped
  • ruff check src/ tests/, CI's mypy set, and the truth-contract fixture --check: clean
  • load_reckoning_overlay on the verdict overlay: 278 families, no errors. The overlay smoke (Reckoning rows from the saved truth snapshot, no GitHub calls) gives 278 rows. The catalog loads with no errors or warnings, and all 39 mapped rows resolve as archived.

Set lifecycle_state: archived and operating_path: archive on each
flipped repo's row, drop live-use claims from four notes, take
TideEngine out of automation eligibility, and move the live-file
test pins to match.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T01:13:23.432749Z 9ad07ef PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@saagpatel
saagpatel merged commit 0ff90d8 into main Oct 13, 2026
4 checks passed
@saagpatel
saagpatel deleted the chore/catalog-archive-reckoning-waves1-3 branch October 13, 2026 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant