Correct workplan prefix declarations to WNCTL-WP

Align the repo identity, file paths, and workplan/task examples with the registered owner and existing workplans. Resolves repo-manager RMGR-IN-0002.

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a100de-2e1c-7e23-9ae9-2da0e0499411

AGENTS.md

@@ -7,7 +7,7 @@
 **Domain:** consumer
 **Repo slug:** whynot-control
 **Topic ID:** `4c2e5315-2cb9-447c-9d16-a39bdb0aabd0`
-**Workplan prefix:** `WHYNOT-WP-`
+**Workplan prefix:** `WNCTL-WP-`
 
 ---
 
@@ -169,10 +169,10 @@ get wrong.
 Work items originate as files in this repo — not in the hub. The hub is a
 read/cache/index layer that rebuilds from files.
 
-**File location:** `workplans/WHYNOT-WP-NNNN-<slug>.md`
+**File location:** `workplans/WNCTL-WP-NNNN-<slug>.md`
 
 **Archived location:** finished workplans may move to
-`workplans/archived/YYMMDD-WHYNOT-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
+`workplans/archived/YYMMDD-WNCTL-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
 the completion/archive date; the frontmatter `id` does not change.
 
 **Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@@ -184,7 +184,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 
 ```yaml
 ---
-id: WHYNOT-WP-NNNN
+id: WNCTL-WP-NNNN
 type: workplan
 title: "..."
 domain: consumer
@@ -208,7 +208,7 @@ derived health labels, not frontmatter statuses.
 ## Task Title
 
 ` ` `task
-id: WHYNOT-WP-NNNN-T01
+id: WNCTL-WP-NNNN-T01
 status: wait | todo | progress | done | cancel
 priority: high | medium | low
 state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit