test(backlog-triage): dogfood Decision Review on dev-backlog open issues

[sungjunlee]

Context

The first pass should be verified against this repo's own open issues so the report proves it can separate useful work from backlog noise.

Part of #167.

Acceptance Criteria

• Run the existing collect / relate / stale report flow against sungjunlee/dev-backlog.
• Add a manual Decision Review section using spec/charter.md and spec/capabilities.md as evidence.
• The report classifies current open issues into Do Now, Shape First, Defer, or Drop / Close with one-line rationale each.
• Capture any confusing rubric behavior as follow-up issues instead of expanding this issue's scope.

[coderabbitai]

🔗 Related PRs

#74 - feat(backlog-triage): triage report renderer (#64) [merged]
#80 - fix(backlog-triage): exclude progress issues from triage snapshots [merged]
#82 - feat(backlog-triage): add snapshot v2 collector [merged]
#110 - docs: dogfood spec/capabilities.md for dev-backlog itself (#105) [merged]
#160 - [codex] split spec charter and grill skills [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[sungjunlee]

Dogfooded in backlog/triage/2026-05-31-decision-review-dogfood.md using the collected dev-backlog snapshot, spec/charter.md, spec/capabilities.md, and spec/system-map.md. The report classifies all current open issues into Do Now, Shape First, Defer, or Drop / Close and records no new follow-up issues from rubric confusion. Verified with node --test skills//scripts/.test.js and bash skills/dev-backlog/scripts/smoke-test.sh.