change-request-gatelisted

# Change-request gate A change-request task cannot go straight to implementation. In files-backed task records this is typically `type: change-request`; in GitHub-backed task records it is typically the `type:change-request` label. It changes a locked decision, so the decision must be reviewed as documentation before code follows it. ## Gate 1. The maintainer drafts or updates the affected durable docs. Use [[decision-capture]] when the decision should be tracked under `.agenticloop/decisions/`. Use an ADR only when the decision earns one. 2. The docs-only change is reviewed by a human. 3. A human marks the task approved in the active backend. 4. Implementation proceeds through [[task-record-contract]] and [[review-and-accept]]. Until approval is present, hold the task in [[blocked-state]] with category `contract`. ## Backend projections ### Neutral rule - Classify the task record as a change request before implementation starts. - Hold the task in blocked or contract state until human approval is durably recorded. - Human-authored work enters the loop only after the task record is clearly marked ready for the agent roles that will continue it. ### GitHub projection - Classify with the configured `type:change-request` label. - Record approval with the configured `approved` label. - Until approval exists, keep the task blocked under [[blocked-state]] with category `contract`. - A human-authored issue enters the loop only when it carries `agent-ready` and the configu