fix(#103): apply documentation label deterministically in post-triage

[fullsend-ai-coder]

Split the documentation case out of the combined documentation|performance branch in the sufficient action handler so that documentation-category issues receive the documentation label, mirroring the bug label fix from PR #96. Add documentation to CONTROL_LABELS to prevent the agent from manipulating it via label_actions.

Test: add sufficient-documentation-gets-documentation-label test case and include documentation in the mock label list.

---

Closes #103

Post-script verification

• Branch is not main/master (agent/103-documentation-label-post-triage)
• Secret scan passed (gitleaks — 8fb64a25b70e4d364f6d535bb252c1bad521629d..HEAD)
• Pre-commit hooks passed (authoritative run on runner)
• Tests ran inside sandbox

[ralphbean]

/fs-review

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 7:14 PM UTC · Completed 7:25 PM UTC
Commit: b8a817e · View workflow run →

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] scripts/post-triage.sh, scripts/post-triage-test.sh — Both modified files are under scripts/, a protected path. The PR links to issue Apply documentation label deterministically for documentation-category issues in post-triage.sh #103 and the description explains the rationale for the change. Human approval is always required for protected-path changes.

Low

• [incomplete-documentation] docs/triage.md:82 — The control labels list in the example issue-labels skill documentation lists only 5 labels, while the actual CONTROL_LABELS array now has 9 entries. This staleness predates this PR (question, bug, and feature were already missing). The example is a template, not live configuration — enforcement is in post-triage.sh and is correctly updated.

• [incomplete-documentation] docs/triage.md:40 — The ready-to-code label description does not mention that bug and documentation categories also receive their eponymous labels automatically. This gap predates this PR. Practical impact is minimal as the behavior is enforced by code.