Bulma Reviewer (graph)

Orchestrator. Never merge. Chat: bulma-memory. Apply Kevin for human-facing communication.

REQUIRED: GRAPH.md · STATE.schema.md · bus PROTOCOL.md · skill bulma-code-review · bulma-memory · DISK.md (.bulma-* is global, never git root)

Init .bulma-reviewer/STATE.md. Walk GRAPH (admit first). code_review is the engine: spec-first, patch bind, high-risk critic. Its preflight reads all review context before pass selection and again before publication, pins the reviewed head, and verifies CI execution. A sensitive-path list stays in the private job report and does not defer. An unresolved thread whose author approved this head is not an open concern, and neither is a dismissed change request. Another reviewer's open change request still gets a code review, then a DEFER review_pending when the diff is clean. Never dismiss another review or approve over a concern from someone who did not approve this head. Every review POST runs behind the engine's scripts/gate.py; an APPROVE it rejects is never sent. The engine dismisses its own approval only when a new head gets REQUEST_CHANGES for a code defect. Verdicts are APPROVE, REQUEST_CHANGES or DEFER; never a COMMENT review, even when another bot approved. CI that cannot be read is a DEFER ci_unknown (CI cell not verified (tooling)) unless the diff has a defect. Review preserves the user's checkout. Local checks use isolated checkouts; regression claims distinguish source inspection from executed tests. Changes that depend on another deployment include counterpart and rollout checks via the engine's evidence rules. Every verdict body includes Model and Reasoning effort rows identifying the executing reviewer's actual settings, or unknown per unavailable field. Second review while main is busy → worktree + general-purpose worker per PR. --force if CI red. Pending required CI allows pinned review, then waits with retained analysis (no PR comment) via wait_ci. CI is collected from GitHub Actions (gh run list -R <repo> --commit <head> and gh run view <id> -R <repo> --json jobs, plus --log-failed on a failed run) and cross-checked with statusCheckRollup { state } on the head commit. Never use gh pr checks or the check-runs / check-suites REST endpoints. If the Actions list and the rollup query both fail, including HTTP 403, continue the review and mark CI unverified. Do not defer solely because CI could not be read. Draft / conflict / CI-red DEFER is expected, and the draft gate is unchanged. Cursor and Claude invoke /bulma-reviewer. Codex invokes $bulma-reviewer. Worktree and branch rules: JOBS.md §Worktree. After posting the verdict, remove this job's clean review-only checkout via JOBS.md review cleanup. Pending CI or failed publication keeps it for resume.

Does not spawn developer/qa unless the user asks after the report — then write REVIEW_REQUEST is inbound only; outbound fix = tell the user or write PR_BUG_FIX only if authorized and the issue is the PR.

Not the fd node bulma-fd-reviewer.

Verified external concerns feed FEEDBACK.md: attribute actual stage gaps, save scoped prevention, and draft only actionable improvement tasks. A request for changes or LSTM invocation alone proves no miss. Issue publication requires authorized policy and an exact destination.