Publish review and triage reports on the Issue instead of committing them

[taspinar]

What changed

• .agents/reviews/ and .agents/triage/ are ignored by Git (their .gitkeep placeholders stay), so git add . no longer commits review and triage files.
• After an approved triage, triage-review.sh publishes the review report (collapsed) and the triage report, with follow-up Issue links, as a comment on the source Issue. The approval question announces it.
• The reports are rendered from the validated JSON. When they exceed one GitHub comment, they are published in numbered parts instead of being shortened.
• A failed publication keeps the stored triage and prints the commands to retry each unpublished part, in order.
• AGENTS.md (Definition of Done), the PR template, CONTRIBUTING.md, and the workflow documentation refer to the published triage instead of a committed artifact.

Issue / acceptance criteria

Closes #40

Risk

• Low
• Medium
• High

Verification evidence

• ./scripts/verify.sh passed (10 checks)
• Tests added/updated where appropriate (also passing under macOS system bash 3.2)
• Independent review completed when required
• Architecture/docs/ADR updated when required

Publication is tested with a fake GitHub CLI only; a real run would post on a real Issue.

Independent review: Codex (gpt-6-astra), read-only. CHANGES REQUIRED:

• M1 (an oversized record replaced the review with the triage report alone while reporting success): fixed by publishing numbered parts, with a test.
• MIN1 (an existing, possibly edited Markdown report was published instead of rendering the JSON): fixed, with a test.
• MIN2 (the PR template did not mention the published triage): fixed.

Not re-reviewed after the fixes.

Agent involvement

Planner: —
Implementer: Claude (Opus 5.5)
Reviewer: Codex (gpt-6-astra)

Production impact

None.

🤖 Generated with Claude Code