Complete CommerceCanon rename and declare concept ownership boundary

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b

.claude/rules/first-session.md

@@ -1,11 +1,11 @@
 ## First Session Protocol
 
-Triggered when `get_domain_summary("infotech")` shows **no workplans**.
+Triggered when `get_domain_summary("financials")` shows **no workplans**.
 The project is registered but work has not yet been structured.
 
 **Step 1 — Read, don't write**
-- `~/the-custodian/canon/projects/infotech/project_charter_v0.1.md` — purpose, scope
-- `~/the-custodian/canon/projects/infotech/roadmap_v0.1.md` — planned phases
+- `~/the-custodian/canon/projects/financials/project_charter_v0.1.md` — purpose, scope
+- `~/the-custodian/canon/projects/financials/roadmap_v0.1.md` — planned phases
 - Scan repo root: README, directory structure, existing code or docs
 
 **Step 2 — Survey in-progress work**
@@ -15,24 +15,24 @@ Look for TODOs, open branches, half-finished files. Note done vs. started but in
 Propose 1–3 workplans — each a coherent strand, weeks to months, anchored to a
 roadmap phase. **Wait for approval before creating.**
 
-**Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)**
+**Step 4 — Write the workplan file; Repo Manager projects it (ADR-001)**
 ```
-workplans/IDENTITY-WP-NNNN-<slug>.md   ← write this, commit it
+workplans/COMMERCE-WP-NNNN-<slug>.md   ← write this, commit it
 ```
-Then register by running the consistency check — do **not** call
-`create_workplan`/`create_task` yourself; manual registration duplicates what
-C-06 creates from the file:
+Then run the deterministic, forge-derived sync — do **not** call
+`create_workplan`/`create_task` yourself:
 ```bash
-statehub fix-consistency --repo identity-canon
+uv run --project ~/repo-manager rmgr sync --path . --push
 ```
-C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id`
-(legacy frontmatter name — holds the workplan UUID) and `state_hub_task_id`
-back into the file.
+Repo Manager writes deterministic `state_hub_workstream_id` and
+`state_hub_task_id` values, pushes the file, verifies `primary/railliance01`,
+and asks central to derive that exact Forgejo commit. If connectivity is down,
+the queued receipt is pending evidence; rerun the same command later.
 
 **Step 5 — Record the setup**
 ```
 add_progress_event(
-    summary="First session: structured infotech into N workplans, M tasks",
+    summary="First session: structured financials into N workplans, M tasks",
     event_type="milestone",
     topic_id="fe2aaa78-9c20-4feb-b3d2-4fe0529572a3",
     detail={"workplans": [...], "tasks_created": M}