Refresh operating guidance and standardize new workplan naming

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e77d-47a4-7771-8e34-7339c7fac0e4

AGENTS.md

@@ -169,10 +169,14 @@ 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/NET-WP-NNNN-<slug>.md`
+New workplans use the registered **`NK-WP-`** prefix. Existing `NK-WP`,
+`NET-WP` and `ADHOC` IDs, filenames and hub UUIDs remain unchanged; do not
+renumber historical records to match this convention.
+
+**File location:** `workplans/NK-WP-NNNN-<slug>.md`
 
 **Archived location:** finished workplans may move to
-`workplans/archived/YYMMDD-NET-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
+`workplans/archived/YYMMDD-NK-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 +188,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 
 ```yaml
 ---
-id: NET-WP-NNNN
+id: NK-WP-NNNN
 type: workplan
 title: "..."
 domain: infotech
@@ -208,7 +212,7 @@ derived health labels, not frontmatter statuses.
 ## Task Title
 
 ` ` `task
-id: NET-WP-NNNN-T01
+id: NK-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
@@ -221,5 +225,6 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
 
 To create a new workplan:
 1. Write the file following the format above
-2. Notify the custodian operator to run `make fix-consistency REPO=net-kingdom`
-   (or send a message to the hub agent via `POST /messages/`)
+2. Run `statehub fix-consistency --repo net-kingdom` directly, as required by
+   the session close protocol. Ask the operator only if the CLI or API is
+   unavailable.