feat: add 3 new error entries (known-unsolved, silent-failures, permissions-auth)

[htekdev]

Summary

Add 3 new error entries discovered via GitHub Issues Mining (Strategy 1, round 249).

New Entries

ku-138: GitHub Actions Runners Have No Pseudo-Terminal — bash -i Fails with 'no job control'

• Category: known-unsolved | Severity: limitation
• Source: Not a tty actions/runner#241 (107 reactions, 67 comments)
• Patterns: 'bash: cannot set terminal process group', 'bash: no job control in this shell', 'not a tty'
• Root cause: GitHub Actions run steps via pipe-connected subprocess with no PTY allocation; bash interactive mode (-i) fails; isatty() returns false

sf-222: \gh run download\ Uses REST API — Cannot Access Artifacts from an In-Progress Run

• Category: silent-failures | Severity: silent-failure
• Source: gh run download can't download artifacts from current run when executed in a workflow cli/cli#5625 (16 reactions, 13 comments)
• Pattern: gh run download exits 0 but downloads nothing when run in the same ongoing workflow
• Root cause: gh uses REST API (only sees completed-run artifacts); actions/download-artifact uses internal pipeline API (real-time visibility)

pa-122: \GITHUB_TOKEN\ Cannot Access Organization Membership or Team APIs

• Category: permissions-auth | Severity: error
• Source: GitHub Docs / community (documented limitation)
• Pattern: 'Resource not accessible by integration' when calling /orgs/{org}/members, /orgs/{org}/teams
• Root cause: read:org is not a grantable scope for GITHUB_TOKEN; use PAT or GitHub App token instead

Dedup Verification

• ku-138: No existing entry for 'cannot set terminal process group' or 'no job control'
• sf-222: triggers-108 covers workflow_run in_progress artifact timing (different scenario); no entry covers gh CLI REST API limitation
• pa-122: No existing entry for GITHUB_TOKEN read:org scope limitation