docs: residual convention + AWQ-011/012 handoffs for WP-0006

Align AGENTS, AutonomyPolicy, SCOPE, OperatingRhythm with fleet residual
role (live intakes, not SCOPE prose). Capture BINKY-WP-0006 leftovers as
AWQ-011 (brief-weekly) and AWQ-012 (open-weights retarget).

AGENTS.md

@@ -116,8 +116,12 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 
 **Close:**
 1. Update workplan file task statuses to reflect progress
-2. Log: `POST /progress/` with a summary of what changed
-3. After workplan file changes, run:
+2. If finishing a workplan: hand off **residuals** as live work records first
+   (intake with `origin: residual` + `origin_ref: <WP-id>`, or a next workplan /
+   decision / engagement). Do not park leftovers only in prose or `SCOPE.md`.
+   Canon: `the-custodian/canon/standards/work-record-types_v0.1.md` § Residuals.
+3. Log: `POST /progress/` with a summary of what changed (name handoff ids)
+4. After workplan file changes, run:
    ```bash
    statehub fix-consistency
    ```
@@ -193,6 +197,12 @@ Task description text.
 
 Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
 
+**Residuals when finishing:** actionable leftovers become live work records
+before `status: finished` — usually an intake in `AutopilotWorkQueue.md`
+(`origin: residual`, `origin_ref: BINKY-WP-NNNN`) or a spawned workplan.
+Residual is a *role*, not a kind. Fleet list lives on State Hub, not in
+`SCOPE.md`. See OperatingRhythm residual note and work-record-types § Residuals.
+
 To create a new workplan:
 1. Write the file following the format above
 2. Run `statehub fix-consistency` locally; ask the operator only if the CLI or