Skip to content

chore: record wave-0 GitHub-archived repos in the catalog - #279

Merged
saagpatel merged 4 commits into
mainfrom
chore/catalog-archive-reckoning-wave0
Oct 13, 2026
Merged

saagpatel merged 4 commits into
mainfrom
chore/catalog-archive-reckoning-wave0

Conversation

@saagpatel

Copy link
Copy Markdown
Owner

What

Records the repos archived on GitHub in reckoning wave 0 in the auditor's local records.

  • config/portfolio-catalog.yaml: lifecycle_state: archived, operating_path: archive on portfolio-tribunal, consolidation-map, Lazarus, repository-renaissance and portfolio-health. Only the public flags change. project-discovery-corpus has no catalog row, so it needs no edit.
  • tests/test_portfolio_catalog.py: Lazarus and portfolio-health leave the live-file manual-only pin, and a new pin asserts the five archived rows.
  • config/notion-repo-map.json: drops the portfolio-health key, the only wave-0 repo with one (91 to 90 keys).
  • codex_restart_packet.py: drops portfolio-health from DEFAULT_OPERATING_REPOS.

The _archive group already exists on main, so this PR doesn't add it.

Deliberately untouched

operator-os-explainer stays active/maintain until after its own GitHub archive and the next nightly security receipt. evals, portfolio-index, cross-system-smoke, harnessbench, transcript-autopsy, proof-pr and sovereign are also unchanged. Wave 1 is not flipped yet, so it isn't included.

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 built from the saved truth snapshot, no GitHub calls) gives 278 rows. The catalog loads with no errors or warnings, and the five rows resolve as archived.

Set lifecycle_state: archived and operating_path: archive on the
portfolio-tribunal, consolidation-map, Lazarus, repository-renaissance
and portfolio-health rows, and move the live-file test pins to match.
The repo is archived on GitHub, so it leaves the Notion sync cohort.
@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-13T00:42:40.653761Z 7eebbcb 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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7eebbcbc6a

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

Comment thread config/notion-repo-map.json
Comment thread config/portfolio-catalog.yaml
Lazarus no longer claims a manual-only contract, and the tribunal and
consolidation-map notes no longer describe on-demand runs.
@saagpatel
saagpatel merged commit 99eaac6 into main Oct 13, 2026
4 checks passed
@saagpatel
saagpatel deleted the chore/catalog-archive-reckoning-wave0 branch October 13, 2026 00:53
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