(triage): Let triage-apply set the native issue Type on org repos

[evanharmon1]

Problem

On an organization repo the triage contract says native issue Type owns work classification, and triage-apply.sh correctly writes no work-type label there. But it also cannot write the native Type, so on a fresh org backlog the skill adds needs-triage to every issue (native Type unset) and can never remove it — 41 of 41 issues on harmonops/harmon-infra ended that way on 2026-08-22 until Types were set by hand. gh issue edit --type NAME exists (gh ≥ 2.98) and the org's Types are readable via GraphQL organization.issueTypes, so the loop can be closed inside the contract.

Acceptance criteria

• [CI] triage-apply.sh gains a --native-type TYPE option (org repos only) that validates the name against the org's enabled issue Types and sets it via gh issue edit --type, dry-run by default and gated by --execute like labels.
• [CI] The scan's native_type read and the needs-triage removal check treat a Type set in the same apply call as satisfying the work-type requirement.
• [HUMAN] SKILL.md step 2a documents choosing a Type on org repos with the same decision table used for work-type labels on personal repos.

Verify

grep -n -- '--native-type' ai/skills/universal/triage/assets/triage-apply.sh

No match means the option does not exist yet; the observation (41/41 issues stuck in needs-triage) is reproducible on any org repo whose issues have no Type.

Out of scope

Writing Types on personal-account repos (GitHub does not offer them there).

Provenance

Follow-on to #485 (axes and native Type derived from the taxonomy). Observed on harmonops/harmon-infra during the 2026-08-22 triage pass.

[evanharmon1]

Corroborating evidence, 2026-08-22: on sommerlawn/sommerlawn-site 33 of 45 open issues and on sommerlawn/sommerlawn-zoho 10 of 16 had no native Type, so the first /triage pass could only add needs-triage to all 43; Types were then set by a raw updateIssueIssueType GraphQL mutation outside the skill, after which a second pass cleared needs-triage where the axes were complete. A gated --native-type on triage-apply would have made that one pass.

[evanharmon1]

Claiming — starting implementation on branch 587-triage-set-issue-type (session triage-set-issue-type-587).

Preflight (§3):

• credentials/scopes: ok — the active gh credential has repo and read:org, covering issue edits and enabled-Type discovery; Project scopes are not used by the claim or implementation lifecycle
• human/out-of-band steps: none
• plan-vs-apply blind spots: dry-run can validate the Type and proposed mutation; stubbed execute-mode tests must prove gh issue edit --type without mutating a real org backlog
• stale references: none — cited apply, scan, docs, and test surfaces exist on fetched origin/main; the triage skill is repository-owned shipped content; overlap with actively claimed (triage): don't require a layer label to clear needs-triage #592 must be accommodated

Claim record (for /wrap — undo only what this claim added):

• harness: Codex CLI
• model: gpt-5.6-sol
• family: gpt
• runtime environment: host
• session: triage-set-issue-type-587
• assignee added by this claim: yes
• claim: label added by this claim: claim:gpt
• claim: model label added by this claim: n/a
• claim: label displaced by this claim: none
• assignee logins owned by this claim chain: evanharmon1
• claim: label owned by this claim chain: claim:gpt
• claim: model label owned by this claim chain: n/a
• claim: label displaced by this claim chain: none

[evanharmon1]

Partial delivery: PR #611 landed the organization native-Type apply path, state handling, documentation, and regressions. Remaining: attributable human review of the Step 2a Type-selection wording.

Claim released — partial delivery landed and the remaining human verification is not in flight. (Supersedes the claim record above.)

[evanharmon1]

Claim released — partial delivery landed and the remaining human verification is not in flight. (Supersedes the claim record above.)

Partial delivery: PR #611 landed the organization native-Type apply path, state handling, documentation, and regressions. Remaining: attributable human review of the Step 2a Type-selection wording.