[lilyshen0722]

This is the docs follow-up promised on #3295. It answers CodeRabbit's body point at 733b09f, which arrived after that PR entered the queue.

docs/runbooks/litellm-guardrails.md said the canary exits 3 "if the guard stops one." The script exits 3 only when the guard stops a turn on both attempts, because one stop alone is inconclusive. The sentence now says that.

🤖 Generated with Claude Code

https://claude.ai/code/session_015AKgpQ2pr6xRMhN5mcfoHF

[lilyshen0722]

HEAD: 2dd1a1a — GATE: PASS

One review round (D218), Tier 0, a one-line doc change checked against the source on main. In scripts/guard-name-canary.js, exitCodeFor returns BLOCKED_EXIT (3) when a check's verdict is blocked. The verdict docblock just below it says "Blocked needs both attempts blocked", and a single stop reads as inconclusive (2). The runbook sentence now says the same.

GATE: PASS

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Team-Commonly/commonly
• Branch: cto/d230-canary-doc-followup
• File: .coderabbit.yaml
• Commit: 2dd1a1a
• Layers: Repository YAML
• Review profile: QUIET
• Plan: Advanced
• Run ID: 8bb55a5a-51d4-42c9-9df6-6de0a24938d3

Commits

Reviewing files that changed from the base of the PR and between bdd549c and 2dd1a1a.

Files selected for processing: 1

• docs/runbooks/litellm-guardrails.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 3 remain after this review.

Walkthrough

The runbook now documents that the guard-name canary exits with code 3 only when both attempts stop. A stop on one attempt is inconclusive. Deploy Dev still runs the canary after verification and rolls back on exit code 3.

Changes: Guardrail canary documentation

Layer / File(s)	Summary
Canary result and deployment response docs/runbooks/litellm-guardrails.md	The runbook changes the exit-3 condition to require stops on both attempts. It describes one stop as inconclusive and retains the documented Deploy Dev rollback on exit code 3.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Possibly related issues

• Team-Commonly/commonly#541 — The runbook documents the canary outcome for LiteLLM guardrail blocking, but does not change enforcement behavior.

Merge Risk: Minimal · up to 2dd1a

The canary behavior is documented consistently with the deployment rollback flow.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely states the main documentation change: exit 3 requires both canary attempts to be stopped.
Description check		The description directly explains the documentation correction and its relationship to the canary behavior.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts