Skip to content

epic: repository health and release-readiness swarm #308

Description

@WalksWithASwagger

Summary

Coordinate the remaining repository-health and release-readiness work as a dependency-ordered, GitHub-only ledger.

Current Audit Snapshot (2026-07-20)

Completed Foundation

Proven Human And External Gates

Dependency-Ordered Implementation

Collision Map

Shared surface Required order
Public keyframe boundary #322 -> #323 -> #332 -> #333
Package identity and portal #323 -> #332 -> #333
Live GitHub settings #327 only after exact maintainer approval
Publication #327 + #333 -> #334
Evaluation #335 -> #336
Curriculum Atlas #200 -> #201
Studio retirement retained tracks + explicit sign-off -> #267

Promotion Protocol

  1. Keep agent:ready off an issue until every named predecessor is merged, current main is green, and no human decision remains.
  2. Re-read the issue against current code immediately before promotion.
  3. Atomically remove blocked and add agent:ready; never remove needs-human without explicit maintainer approval.
  4. Use one issue, one codex/issue-<N>-<slug> branch, and one pull request with Closes #N or Refs #N.
  5. Stop at needs-human or blocked. Automation never grants approval, publishes, deploys, changes settings, or auto-merges.

Acceptance Criteria

  • All 35 issues open at audit start were inspected against current code, comments, dependencies, merged PRs, and live GitHub state.
  • Completed or superseded issues with direct evidence were closed.
  • Ambiguous legacy work has an explicit human decision gate.
  • Shared-surface collisions have a serialization order.
  • All currently executable repository work has been shipped or parked at a proven gate.
  • Current main CI/CodeQL, open PRs, ready labels, and branch-protection state were refreshed after the final merge.
  • Promote remaining dependencies only under the protocol above.

Tests/Evals

  • Promotion requires predecessor-specific verification plus current main CI.
  • No provider call, deployment, publication, generated-media commit, secret read, or automatic settings mutation is authorized by this tracker.

Verification

  • gh issue list --repo WalksWithASwagger/rafiki --state open --label agent:ready
  • gh pr list --repo WalksWithASwagger/rafiki --state open
  • gh run list --repo WalksWithASwagger/rafiki --branch main
  • gh api repos/WalksWithASwagger/rafiki/branches/main/protection

Agent Instructions

  • Use this issue only as the coordination ledger; do not create an implementation branch for epic: repository health and release-readiness swarm #308.
  • Preserve one-issue/one-branch/one-PR and repository size limits.
  • Never read ignored environment value files or print secrets.
  • Do not publish, deploy, rewrite history, delete worktrees, or mutate repository settings without the named gate.

Out Of Scope

  • Implementing child issues directly in this tracker.
  • Live provider calls, generated media, deployments, publication, branch deletion, destructive migration, or secret changes.

Linear

Not applicable. Rafiki delivery is GitHub-only; do not create or update a Linear issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    pipelineCore pipeline toolingroadmapRoadmap-derived planning and delivery worktrackingTracking issuetype:epicBig picture feature

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions