rite-seallisted

# /rite-seal: GO / NO-GO The decision gate before shipping. **Read the active workspace first**; if none, tell the user to run `/rite-spec <feature>`. Produces `seal.md` with a clear verdict. `/rite-seal` **decides**; the irreversible git commit/push/tag and the task close-out live in `/rite-ship`, which refuses to run without a GO recorded here. ## Rules consulted (read on demand from `.claude/skills/devrites-lib/reference/standards/`) **Step 0:** Read `.claude/skills/devrites-lib/reference/standards/core.md` first. The other rule files load on demand: pull these via `Read` before sealing: - `agents.md`: review-subagent fan-out at seal. - `code-review.md`: severity labels (Critical / Important / Suggestion / Nit / FYI). - `review-checklist.md`: compact final review pass/fail sweep. - `test-proof-checklist.md`: compact proof-quality gate for tests and evidence. - `browser-proof-checklist.md`: for UI scope, the browser-state and Visual Verdict gate. - `security-checklist.md`: when input / auth / data / integrations / secrets are in scope. - `principles.md`: declared project invariants (`.devrites/principles.md`) are a pass/fail gate; a diff that violates one with no recorded, human-approved exception is a NO-GO. - `documentation.md`: record decisions in `decisions.md` before sealing. - `observability.md`: a runtime surface that ships blind is an Important finding. - `deprecation.md`: when the diff removes / migrates code, API, or data (read with the risk-and-rollback step