Skip to content

Add Saffron Phase 1 runtime smoke checklist #52

Closed

Description

@joryirving

Before Saffron stops grooming GitHub Projects and starts using Mission Control as her task visibility layer, we need a clear runtime smoke checklist.

Acceptance criteria — Document checks for:

  • GET /api/health returns healthy (ok: true, database: ok)
  • POST /api/automation/sync succeeds
  • GET /api/automation/repos returns repos
  • POST /api/sync returns syncedCount > 0
  • GET /api/issues returns issues
  • Board shows issues
  • Projects shows repo groups
  • Saffron heartbeat appears in Agents
  • Moving one low-risk test issue updates GitHub labels and writes AuditLog
  • Logs show no Prisma, BigInt, or FK errors
  • Mission Control failures do not break Saffron heartbeat

This should be documented as a runnable checklist (e.g., a script, markdown doc, or CI step) that can be executed before cutover.

Activity

  1. itsmiso-ai commented on May 15, 2026

    @itsmiso-ai
    Contributor

    Superseded by issue #60 (Add assignment-layer runtime smoke checklist) which covers the same runtime smoke checklist requirement generically for all agents. PR #73 was closed as stale.

  2. added and removed
    status/backlogNot ready for worker pickup yet.
    on May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions