triage

# Triage: Work-Unit Formation Form executable work units from GitHub issue substrate, handing execution — branches, PRs, applied fixes — to a normal session. It reads raw issues, groups related issues, fuses each group with the project's inscribed northstar and the user's current-session judgment, forms one or more focused work units, and — once the user routes a unit for handoff — externalizes it to a substrate-owned record a continuing collaborator session is pointed at. ## Core Contract `/triage` owns work-unit formation: ``` BacklogIntake -> RawIssueSet -> IssueGroup -> NormalizedProblemFrame -> NorthstarFusion -> FocusedWorkUnit -> RouteChoice -> independent session: externalize -> WorkUnitRecord -> re-triage: back to the relevant earlier phase, no record externalized ``` Execution is not `/triage`'s. The receiving session starts from the record's canonical locator, dereferences the work-unit record with its own tools, grounds the premises it needs, and does the branching, editing, and PR work itself as a continuing collaborator, not a mere executor. Arranging how several routed units run is likewise outside this skill: `/triage` externalizes one record per routed unit and stops. ## Types | Type | Meaning | |---|---| | `BacklogIntake` | The scale-aware intake step that binds an explicit issue scope or, when no scope is supplied, inspects the current repository's open GitHub issue backlog through lightweight metadata before deciding how mu...