diff --git a/.ceremony/LABELS.md b/.ceremony/LABELS.md index 61ffcfc..3d56b6b 100644 --- a/.ceremony/LABELS.md +++ b/.ceremony/LABELS.md @@ -27,8 +27,10 @@ and the reconciler recomputes it from GitHub's own facts. `state:needs-human` means exactly one thing — a human could merge this now — so it requires zero blockers and head-current approvals; anything less and the reconciler takes it back. The author sets it at handoff (the one -hand-set state); the `labeled` event fires the sweep that validates the -write within seconds. +hand-set state). On a same-repository head, the `labeled` event fires the +sweep that validates the write within seconds; on a fork head whose +`pull_request_target` token is read-only, validation waits for the scheduled +sweep cadence (#241). ## PR blockers — what is in the way? (facts, as many as apply) @@ -49,7 +51,7 @@ strips it on sight). | Label | Color | Means | Set by | |---|---|---|---| -| `needs-triage` | `#FBCA04` | an issue that did not come through triage — it owes normalization or conversion back to a discussion | anyone who spots one; cleared by triage | +| `needs-triage` | `#FBCA04` | a proposal or stray issue that did not come through triage — it owes normalization into work or a reasoned refusal | anyone who spots one; cleared by triage | | `ready` | `#0E8A16` | triaged, spec complete, unblocked — a builder can start now and succeed | triage | | `claimed` | `#1D76DB` | a builder owns it: assignee set, a draft PR expected shortly | the claiming builder | | `blocked` | `#6A737D` | waiting on another issue or PR (`Blocked by #N` in the body names it) | triage; anyone may correct it | @@ -240,4 +242,4 @@ full-board reconcile. The sweep warns when the core taxonomy declares a label the repository lacks. The same workflow reconciles issue-flow labels on issue events and during the scheduled sweep. Default GitHub labels (`duplicate`, `invalid`, `question`, `wontfix`, `help wanted`, `good first issue`) are -deleted at bootstrap — a `question` is a discussion, not an issue. +deleted at bootstrap — a `question` belongs in a proposal, not a work issue.