CI Triage Workflow

Prioritization Order

1. Build failures
2. Lint failures
3. Type failures
4. Test failures
5. Review comments (after CI blockers)

Failure Handling Rules

• Investigate each failing job as if it is caused by the current changes.
• Do not assume flakiness by default.
• If the job output has a "Known Flaky Tests" section, use it as historical context, not as automatic dismissal.

Common Patterns

• rust check / build:
  • Run cargo fmt -- --check
  • Fix with cargo fmt
• lint / build:
  • Run pnpm prettier --write <file>
  • Run the repo lint command if needed
• test failures:
  • Run the exact failing test file locally
  • Match dev vs start mode to the CI job

Resolving Review Threads

After addressing a review comment (e.g., making the requested code change), or when you detect the current code already addresses it:

1. Reply to the thread describing what action was taken:

   node scripts/pr-status.js reply-thread <threadNodeId> "Done -- <description of changes>"

2. Then resolve the thread:

   node scripts/pr-status.js resolve-thread <threadNodeId>

Or do both in one step:

node scripts/pr-status.js reply-and-resolve-thread <threadNodeId> "Done -- <description of changes>"

The ready-to-use commands with the correct thread IDs are at the bottom of each thread-N.md file in scripts/pr-status/results/.

Important: Always reply with a description of the actions taken before resolving. This gives the reviewer context about what changed.