fix(triage): file reports through the issue form so via-triage sticks - #9412

Note

Low Risk
Documentation-only playbook text for triage agents; no runtime code or GitHub integration paths changed.

Overview
Section 8 of the triage playbook is expanded so agents stop filing unlabeled issues when the submitter lacks GitHub triage/write permission.

The old single bullet about via-triage labeling is split into explicit steps: check gh api repos/pingdotgg/t3code --jq .permissions.triage before gh issue create --label via-triage (the label is dropped silently on failure). Without permission, agents must use issues/new?template=via-triage.yml with URL-encoded title and per-field ids from via-triage.yml, and must not pass labels (404 for readers who cannot apply labels). Long reports use the bare template form with user paste instead of URL prefill.

The unauthenticated fallback no longer points at a generic issues/new URL with title/body; it defers to the same issue-form flow. TRIAGE_PLAYBOOK in triagePrompt.ts is updated in lockstep with .github/triage/PLAYBOOK.md (existing byte-identity test unchanged).

^{Reviewed by Cursor Bugbot for commit 6b97494. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

File triage reports through issue form so via-triage label sticks

• Updates triage filing guidance in both PLAYBOOK.md and triagePrompt.ts to check label-application permission before applying the via-triage label
• When the account lacks permission or GitHub CLI is unauthenticated, falls back to the issue-template form with URL-prefilled template fields instead of label query parameters
• Adds a bare-form path for long reports and separates title formatting from label application
• Behavioral Change: unauthenticated fallback changes from a body-prefilled URL to the issue form; label query parameters are prohibited in the form fallback

^{Macroscope summarized 6b97494.}