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

Intake Repair and Near-Ready Work

Human Decisions and External Gates

Dependency-Ordered Implementation

Collision Map

Shared surface Required order
Agentic runtime #320 -> #338 -> #324 -> #325 -> #326
Project skills #338 -> #315 -> #318; #315 + #324 -> #325
Frontend lock and CI #338 -> #328 -> #329 -> #330 -> #331 -> #333
Setup and package identity #338 -> #321 -> #329 and #332
Public keyframe boundary #322 -> #323 -> #332 -> #333
Live GitHub settings #321 + #326 -> #327
Publication #327 + #333 -> #334

Promotion Protocol

  1. A blocked issue remains without agent:ready until every named predecessor is merged and current main is green.
  2. Until pipeline: make agent-ready intake atomic and idempotent #338 is fixed, do not add agent:ready to newly prepared issues.
  3. After pipeline: make agent-ready intake atomic and idempotent #338, the coordinator re-reads the issue against current code, removes blocked, and adds agent:ready only if scope and verification still match.
  4. skill: remove machine-specific paths from the real-sky upscaler #318 and build: align fresh-clone setup with the canonical verification gate #321 additionally require explicit maintainer re-arm because they were falsely escalated by the observed race.
  5. Use one issue, one codex/issue-- branch, and one pull request with Closes #N or Refs #N.
  6. Agents stop at needs-human or blocked. Automation never grants approval, publishes, deploys, changes settings, or auto-merges.

Acceptance Criteria

Tests/Evals

  • Promotion requires predecessor-specific verification plus current main CI.
  • No provider call, deployment, publication, generated-media commit, secret read, or automatic merge 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 the repository size limits.
  • Never read ignored environment value files or print secrets.
  • Do not publish, deploy, merge, rewrite history, or mutate repository settings without the named gate.

Human Checkpoints

Out of Scope

  • Implementing child issues in this tracker.
  • Live provider calls, generated media, deployments, publication, branch deletion, or destructive migration.
  • Generic large-file refactors without characterization tests.

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