enhance(spec-grill): make Grill Report the default diagnostic output

[sungjunlee]

Summary

Define the required report shape for spec-grill diagnosis so capability work starts with evidence, questions, and recommendations before any file edit.

Required Report Sections

• Evidence Read
• Evidence Missing
• Raw Candidates
• Accepted / Rejected / Merged / Split Candidates
• Sharp Questions
• 3-Axis Predicate Findings
• Proposed Next Capability
• Recommended Edit

Acceptance Criteria

• skills/spec-grill/SKILL.md defines the Grill Report sections.
• The report contract records rejected predicates, rewritten predicates, behaviors promoted to constraints, and missing proof/evidence when applicable.
• The contract distinguishes diagnosis from editing.
• spec-grill <capability> style deep review remains scoped to one capability block.

Notes

Part of #176. Builds on #177.

[coderabbitai]

🔗 Related PRs

#74 - feat(backlog-triage): triage report renderer (#64) [merged]
#110 - docs: dogfood spec/capabilities.md for dev-backlog itself (#105) [merged]
#160 - [codex] split spec charter and grill skills [merged]
#174 - feat(backlog-triage): add spec-aware Decision Review [closed]

---

📝 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!