Skip to content

fix: keep null-expiry lifecycle records inactive - #206

Merged
abrichr merged 1 commit into
mainfrom
codex/ops-lifecycle-inactive
Sep 3, 2026
Merged

fix: keep null-expiry lifecycle records inactive#206
abrichr merged 1 commit into
mainfrom
codex/ops-lifecycle-inactive

Conversation

@abrichr

@abrichr abrichr commented Sep 3, 2026

Copy link
Copy Markdown
Member

The public lifecycle projection still treated the synthetic records as active after the central policy restored bounded expiry.

This change pins OpenAdaptAI/.github commit 078db7a9399702d0b725676e4a427b1b52fb19ff and regenerates both public JSON projections. Records with expires_at: null don't produce an active target. A future v2 release must also expire within the policy's release-admission limit.

The technical reference and llms.txt now report the current state: seven retained release records and seven retained workflow records, with none actively admitted.

Verification

  • uv run pytest tests/ -q (312 passed, 3 subtests passed)
  • node --test tests/js/production_lifecycle.test.cjs (16 passed)
  • python scripts/render_production_lifecycle.py --check
  • python scripts/render_production_workflow_admissions.py --check
  • uv run python scripts/validate_docs.py
  • uv run mkdocs build --strict

@abrichr
abrichr merged commit b513a9c into main Sep 3, 2026
8 checks passed
@abrichr
abrichr deleted the codex/ops-lifecycle-inactive branch September 3, 2026 04:14
@abrichr

abrichr commented Sep 3, 2026

Copy link
Copy Markdown
Member Author

Closed by an agent session, not the founder.

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