Ironai Merge Lite

1) Sync main

Run:

git switch main
git fetch origin
git pull --rebase --autostash origin main
git status -sb
git log -1 --oneline

Confirm whether main is up to date and report the latest commit line.

2) PR runway check (GitHub CLI)

1. List open PRs with gh and classify each as:
   • automerge-labeled
   • checks failing
   • merge conflicts / not mergeable
2. Output one line per PR:

#<num> <title> — <mergeable/blocked/conflicts/checks failing> — labels: [...]

3) Verdict (strict)

• If 0 open PRs OR all open PRs are mergeable with green checks/auto-merging:
  • Print: ✅ RUNWAY CLEAR
  • Continue to task only if a task is provided.
• If any PR is blocked by conflicts/check failures OR there are 2+ PRs piling up:
  • Print: ⚠️ RUNWAY NOT CLEAR — RUN ironai-flow (mega)
  • List blocked PRs and reason (conflict vs checks failing).
  • Stop. Do not continue to task work.

4) If task is provided after runway check

Proceed only after ✅ RUNWAY CLEAR.

1. Create a new branch from updated main.
2. Keep change small and safe.
3. Run verification before finishing:

npm run build
npm test

If npm test is unavailable, run npm run test.

4. For shipping, hand off to ironai-ship workflow (PR + auto-merge).

End-of-run Output (always)

Provide exactly these sections:

1. Repo status: clean/dirty + what you did
2. Main sync: up to date / pulled commits + last commit line
3. Open PRs: count + list
4. Verdict: ✅ RUNWAY CLEAR / ⚠️ RUN ironai-flow (mega)
5. If proceeded: Traceability checklist

Traceability Checklist (only if code changes were made)

• Reqs understood: 1-3 bullets
• Files changed: paths + why
• Acceptance criteria: bullets with ✅ when met
• Tests/build: commands + results
• Risks: remaining risks + mitigation
• Rollback: how to revert (PR/commit)