Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 2)

Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

.claude/rules/first-session.md

@@ -1,11 +1,11 @@
 ## First Session Protocol
 
-Triggered when `get_domain_summary("markitect")` shows **no workstreams**.
+Triggered when `get_domain_summary("communication")` shows **no workstreams**.
 The project is registered but work has not yet been structured.
 
 **Step 1 — Read, don't write**
-- `~/the-custodian/canon/projects/markitect/project_charter_v0.1.md` — purpose, scope
-- `~/the-custodian/canon/projects/markitect/roadmap_v0.1.md` — planned phases
+- `~/the-custodian/canon/projects/communication/project_charter_v0.1.md` — purpose, scope
+- `~/the-custodian/canon/projects/communication/roadmap_v0.1.md` — planned phases
 - Scan repo root: README, directory structure, existing code or docs
 
 **Step 2 — Survey in-progress work**
@@ -17,20 +17,20 @@ roadmap phase. **Wait for approval before creating.**
 
 **Step 4 — Create workplan file first, then DB record (ADR-001)**
 ```
-workplans/markitect-project-WP-NNNN-<slug>.md   ← write this first
+workplans/MARKITECT-WP-NNNN-<slug>.md   ← write this first
 ```
 Then register in the hub:
 ```
-create_workstream(topic_id="5571d954-0d30-4950-980d-7bcaaad8e3e2", title="...", owner="...", description="...")
+create_workstream(topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", title="...", owner="...", description="...")
 create_task(workstream_id="<id>", title="...", priority="high|medium|low")
 ```
 
 **Step 5 — Record the setup**
 ```
 add_progress_event(
-    summary="First session: structured markitect into N workstreams, M tasks",
+    summary="First session: structured communication into N workstreams, M tasks",
     event_type="milestone",
-    topic_id="5571d954-0d30-4950-980d-7bcaaad8e3e2",
+    topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc",
     detail={"workstreams": [...], "tasks_created": M}
 )
 ```

.claude/rules/repo-boundary.md

@@ -1,6 +1,6 @@
 ## Repo boundary
 
-This repo owns **markitect-main** only. It does not own:
+This repo owns **Markitect Main** only. It does not own:
 
 <!-- TODO: List what belongs in adjacent repos, e.g.:
 - SSH key management → railiance-infra/

.claude/rules/repo-identity.md

@@ -1,5 +1,5 @@
-**Purpose:** Knowledge artifact management system. Handles structured content creation, versioning, and publication workflows for the markitect domain.
+**Purpose:** Markitect Main - (fill in purpose)
 
-**Domain:** markitect
-**Repo slug:** markitect-project
-**Topic ID:** 5571d954-0d30-4950-980d-7bcaaad8e3e2
+**Domain:** communication
+**Repo slug:** markitect-main
+**Topic ID:** 36c7421b-c537-4723-bf75-42a3ebc6a1dc

.claude/rules/session-protocol.md

@@ -1,6 +1,7 @@
 ## Session Protocol
 
-State Hub: http://127.0.0.1:8000
+Dev Hub (State Hub API): http://127.0.0.1:8000
+MCP server name in `~/.claude.json`: `dev-hub`
 
 **Step 1 — Orient**
 
@@ -10,7 +11,7 @@ cat .custodian-brief.md
 ```
 Then call the MCP tool for richer cross-domain context when MCP tools are exposed:
 ```
-get_domain_summary("markitect")
+get_domain_summary("communication")
 ```
 If MCP tools are unavailable in the current agent session, use the REST API:
 ```bash
@@ -21,14 +22,14 @@ If the hub is offline: `cd ~/state-hub && make api`
 **Step 2 — Check inbox**
 With MCP tools:
 ```
-get_messages(to_agent="markitect-project", unread_only=True)
+get_messages(to_agent="markitect-main", unread_only=True)
 ```
 Mark read with `mark_message_read(message_id)`. Reply or act on coordination
 requests before proceeding.
 
 Without MCP tools:
 ```bash
-curl -s "http://127.0.0.1:8000/messages/?to_agent=markitect-project&unread_only=true" \
+curl -s "http://127.0.0.1:8000/messages/?to_agent=markitect-main&unread_only=true" \
   | python3 -m json.tool
 curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
   -H "Content-Type: application/json" -d '{}'
@@ -39,12 +40,12 @@ curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
 ls workplans/
 ```
 For each file with `status: ready`, `active`, or `blocked`, note pending
-`todo`/`in_progress` tasks.
+`wait`/`todo`/`progress` tasks.
 
 **Step 4 — Present brief**
 
-1. **Active workstreams** for `markitect` — title, task counts, blocking decisions
-2. **Pending tasks** from `workplans/` + any `[repo:markitect-project]` hub tasks
+1. **Active workstreams** for `communication` — title, task counts, blocking decisions
+2. **Pending tasks** from `workplans/` + any `[repo:markitect-main]` hub tasks
 3. **Goal guidance** — if `goal_guidance` in summary:
    - `needs_workplan`: surface as top action — *"Repo goal '{title}' has no workplan yet"*
    - `alignment_warnings`: flag if active work is not aligned with current goal
@@ -61,23 +62,23 @@ If no workstreams: follow First Session Protocol (`first-session.md`).
 **Session close:**
 With MCP tools:
 ```
-add_progress_event(summary="...", topic_id="5571d954-0d30-4950-980d-7bcaaad8e3e2", workstream_id="<uuid>")
+add_progress_event(summary="...", topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", workstream_id="<uuid>")
 ```
 Without MCP tools:
 ```bash
 curl -s -X POST http://127.0.0.1:8000/progress/ \
   -H "Content-Type: application/json" \
-  -d '{"topic_id":"5571d954-0d30-4950-980d-7bcaaad8e3e2","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
+  -d '{"topic_id":"36c7421b-c537-4723-bf75-42a3ebc6a1dc","workstream_id":"<uuid>","event_type":"note","summary":"what changed","author":"codex"}'
 ```
 If workplan files were modified, ensure the local copy is up to date first:
 ```bash
 git -C <repo_path> pull --ff-only
-cd ~/state-hub && make fix-consistency REPO=markitect-project
+cd ~/state-hub && make fix-consistency REPO=markitect-main
 ```
 For repos where implementation runs on a remote machine (e.g. CoulombCore),
 use the combined target which pulls before fixing:
 ```bash
-cd ~/state-hub && make fix-consistency-remote REPO=markitect-project
+cd ~/state-hub && make fix-consistency-remote REPO=markitect-main
 ```
 **C-15** (DB task ahead of file) is normal in multi-machine workflows — writeback
 will sync the file to match DB.  **C-16** (repo behind remote) blocks all writes

.claude/rules/stack-and-commands.md

@@ -1,19 +1,16 @@
 ## Stack
 
-<!-- TODO: Fill in language, frameworks, and key dependencies -->
-- **Language:**
-- **Key deps:**
+- **Language:** Python 3.12+ (monorepo) + JavaScript UI (testdrive-jsui)
+- **Key deps:** uv/pip, pytest, npm; see `pyproject.toml`, `package.json`, `Makefile`
 
 ## Dev Commands
 
 ```bash
-# TODO: Fill in the standard commands for this repo
-
-# Install dependencies
-
-# Run tests
-
-# Lint / type check
-
-# Build / package (if applicable)
+make setup
+make test
+make test-js
+make test-all
+make lint
+make build
+make help
 ```

.claude/rules/workplan-convention.md

@@ -1,7 +1,7 @@
 ## Workplan Convention (ADR-001)
 
-File location: `workplans/markitect-project-WP-NNNN-<slug>.md`
-ID prefix: `MARKITECT-WP`
+File location: `workplans/MARKITECT-WP-NNNN-<slug>.md`
+ID prefix: `MARKITECT-WP-`
 
 Work items originate as files in this repo **before** being registered in the hub.
 
@@ -12,7 +12,7 @@ repo state, and `finished` when implementation is complete. `stalled` and
 `needs_review` are derived health labels, not stored statuses.
 
 Closed workplans may be moved to `workplans/archived/` with a completion-date
-prefix: `YYMMDD-markitect-project-WP-NNNN-<slug>.md`. The frontmatter id remains
+prefix: `YYMMDD-MARKITECT-WP-NNNN-<slug>.md`. The frontmatter id remains
 unchanged; the prefix is only for quick visual reference.
 
 Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**:
@@ -21,8 +21,20 @@ Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**
 directly. Promote anything requiring analysis, design, approval, dependencies, or
 multiple planned phases into a normal workplan.
 
-Ecosystem todos from other agents arrive as `[repo:markitect-project]` hub tasks —
+Ecosystem todos from other agents arrive as `[repo:markitect-main]` hub tasks —
 visible at session start. Pick one up by creating the workplan file, then registering
 the workstream.
 
+Task blocks use this shape:
+
+```task
+id: MARKITECT-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
+```
+
+Status progression is `todo` → `progress` → `done`; use `wait` for waiting or
+blocked work and `cancel` for stopped work.
+
 <!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->

.custodian-brief.md

@@ -1,42 +1,18 @@
 <!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief — markitect-project
+# Custodian Brief — markitect-main
 
-**Domain:** markitect  
-**Last synced:** 2026-05-03 17:31 UTC  
+**Domain:** communication  
+**Last synced:** 2026-06-22 21:32 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
 
-### TestDrive-JSUI — npm Publication
-Progress: 0/9 done  |  workstream_id: `e203d487-01f1-494a-b14d-a436241a4c01`
-
-**Open tasks:**
-- · P.1 — Decide repository structure (monorepo vs standalone)  `81c03377`
-- · P.2 — Verify Markitect integration still works  `f518601b`
-- · P.3 — Resolve STANDALONE_PLAN.md status  `d700098c`
-- · P.4 — Pack and dry-run publish  `94dd2a30`
-- · P.5 — Create v1.0.0 release tag  `d7c2ce00`
-- · P.6 — Publish to npm and verify CDN  `8bcde75e`
-- · P.7 — Fresh install test in clean environment  `61d14b53`
-- … and 2 more open tasks
-
-### Infospace Tooling — Stage 3 Close-out
-Progress: 0/8 done  |  workstream_id: `830c888e-e1d4-43e6-8093-9b61e7578257`
-
-**Open tasks:**
-- · C.1 — Evaluate the 3 missing entities  `0fa8f461`
-- · C.2 — Run eval-summary and verify viability (6/6 PASS)  `ba7d992c`
-- · C.3 — Refresh metrics report from full 988-entity set  `84a59244`
-- · C.4 — Document advanced usage patterns  `0ef75ee5`
-- · C.5 — Add composition guide referencing supply-chain-vsm  `864977db`
-- · C.6 — Write performance notes  `414496b0`
-- · C.7 — S3.2: Complete clean per-chapter git history  `21c865c1`
-- … and 1 more open tasks
+*(none — repo may need first-session setup)*
 
 ---
 ## MCP Orientation (when available)
 
 If the state-hub MCP server is reachable, call:
-`get_domain_summary("markitect")`
+`get_domain_summary("communication")`
 This provides richer cross-domain context.
 If the MCP call fails, use this file as your orientation source.

AGENTS.md

@@ -1,12 +1,12 @@
-# markitect-main — Agent Instructions
+# Markitect Main — Agent Instructions
 
 ## Repo Identity
 
-**Purpose:** Knowledge artifact management system. Handles structured content creation, versioning, and publication workflows for the markitect domain.
+**Purpose:** Markitect Main - (fill in purpose)
 
-**Domain:** markitect
-**Repo slug:** markitect-project
-**Topic ID:** `5571d954-0d30-4950-980d-7bcaaad8e3e2`
+**Domain:** communication
+**Repo slug:** markitect-main
+**Topic ID:** `36c7421b-c537-4723-bf75-42a3ebc6a1dc`
 **Workplan prefix:** `MARKITECT-WP-`
 
 ---
@@ -28,11 +28,11 @@ there is no MCP server for Codex agents.
 cat .custodian-brief.md
 
 # Active workstreams for this domain
-curl -s "http://127.0.0.1:8000/workstreams/?topic_id=5571d954-0d30-4950-980d-7bcaaad8e3e2&status=active" \
+curl -s "http://127.0.0.1:8000/workstreams/?topic_id=36c7421b-c537-4723-bf75-42a3ebc6a1dc&status=active" \
   | python3 -m json.tool
 
 # Check inbox
-curl -s "http://127.0.0.1:8000/messages/?to_agent=markitect-project&unread_only=true" \
+curl -s "http://127.0.0.1:8000/messages/?to_agent=markitect-main&unread_only=true" \
   | python3 -m json.tool
 ```
 
@@ -63,8 +63,8 @@ Omit `workstream_id` / `task_id` when not applicable.
 ```bash
 curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
   -H "Content-Type: application/json" \
-  -d '{"status": "in_progress"}'
-# values: todo | in_progress | done | blocked
+  -d '{"status": "progress"}'
+# values: wait | todo | progress | done | cancel
 ```
 
 ### Flag a task for human review
@@ -81,9 +81,9 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 
 **Start:**
 1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
-2. Check inbox: `GET /messages/?to_agent=markitect-project&unread_only=true`; mark read
+2. Check inbox: `GET /messages/?to_agent=markitect-main&unread_only=true`; mark read
 3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
-4. Check blocked tasks: `GET /tasks/?needs_human=true`
+4. Check human-needed tasks: `GET /tasks/?needs_human=true`
 
 **During work:**
 - Update task statuses in workplan files as tasks progress
@@ -95,7 +95,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 3. Note for the custodian operator: after workplan file changes, run from
    `~/state-hub`:
    ```bash
-   make fix-consistency REPO=markitect-project
+   make fix-consistency REPO=markitect-main
    ```
    This syncs task status from files into the hub DB.
 
@@ -151,6 +151,11 @@ every repo's agent instructions because it is high-frequency, high-risk, and eas
 get wrong.
 
 **Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`
+
+<!-- REPO-AGENTS-EXTENSIONS -->
+<!-- Append repo-specific agent instructions below this marker.
+     The state-hub template sync preserves content after this line. -->
+
 ---
 
 ## Workplan Convention (ADR-001)
@@ -176,8 +181,8 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 id: MARKITECT-WP-NNNN
 type: workplan
 title: "..."
-domain: markitect
-repo: markitect-project
+domain: communication
+repo: markitect-main
 status: proposed | ready | active | blocked | backlog | finished | archived
 owner: codex
 topic_slug: ...
@@ -198,7 +203,7 @@ derived health labels, not frontmatter statuses.
 
 ` ` `task
 id: MARKITECT-WP-NNNN-T01
-status: todo | in_progress | done | blocked
+status: wait | todo | progress | done | cancel
 priority: high | medium | low
 state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 ` ` `
@@ -206,9 +211,9 @@ state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 Task description text.
 ```
 
-Status progression: `todo` → `in_progress` → `done` (or `blocked`)
+Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
 
 To create a new workplan:
 1. Write the file following the format above
-2. Notify the custodian operator to run `make fix-consistency REPO=markitect-project`
+2. Notify the custodian operator to run `make fix-consistency REPO=markitect-main`
    (or send a message to the hub agent via `POST /messages/`)

CLAUDE.md

@@ -1,4 +1,4 @@
-# markitect-main — Claude Code Instructions
+# Markitect Main — Claude Code Instructions
 
 @SCOPE.md
 @.claude/rules/repo-identity.md

registry/capabilities/capability.communication.markitect-legacy-platform.md

@@ -0,0 +1,124 @@
+---
+id: capability.communication.markitect-legacy-platform
+name: MarkiTect Legacy Platform
+summary: Intelligent markdown engine and information-management platform treating documents as structured,
+  queryable information spaces with schema validation, transclusion, and LLM-driven evaluation; the legacy
+  umbrella now being split into markitect-tool, infospace-bench, and kontextual-engine.
+owner: markitect-main
+status: draft
+domain: communication
+tags:
+- markitect
+- markdown
+- legacy
+maturity:
+  discovery:
+    current: D3
+    target: D3
+    confidence: medium
+    rationale: INTRODUCTION.md and SCOPE.md describe a mature, broad platform (schema validation, transclusion,
+      LLM evaluation, infospace lifecycle); GUARDRAILS.md and DEPENDENCIES.md indicate an actively-managed
+      but legacy codebase now being superseded by successor repos (markitect-tool, infospace-bench, kontextual-engine
+      each reference a markitect-main-scope-assessment.md boundary doc).
+  availability:
+    current: A1
+    target: A1
+    confidence: medium
+    rationale: Extensive real application code (application/, domain/, services/ dirs) with both a Python
+      package and a package.json; availability target is intentionally capped at A1 since the successor
+      repos are the forward path, not this legacy platform.
+external_evidence:
+  completeness:
+    level: C1
+    confidence: low
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+    - broad legacy feature set (schema validation, transclusion, LLM evaluation)
+    broken_expectations: []
+    out_of_scope_expectations: []
+  reliability:
+    level: R0
+    confidence: low
+    basis: consumer_quality_signals
+    known_reliability_risks:
+    - actively being superseded by markitect-tool/infospace-bench/kontextual-engine; new consumers should
+      prefer the successors per each successor's own scope-assessment docs
+discovery:
+  intent: Document the legacy MarkiTect platform honestly as a superseded predecessor, so planners route
+    new work to the successor repos rather than extending this one.
+  includes:
+  - legacy markdown engine, schema validation, transclusion, LLM-driven evaluation, infospace lifecycle
+    (as originally built)
+  excludes:
+  - new feature development (happens in markitect-tool, infospace-bench, kontextual-engine)
+  assumptions: []
+  use_cases: []
+  research_memos: []
+availability:
+  current_level: A1
+  target_level: A1
+  current_artifacts:
+  - legacy Python/Node application
+  target_artifacts: []
+  consumption_modes:
+  - application (legacy, not recommended for new integration)
+relations:
+  depends_on: []
+  supports: []
+  related_to: []
+evidence:
+  documentation:
+  - INTRODUCTION.md
+  - SCOPE.md
+  - GUARDRAILS.md
+  tests:
+  - tests/
+  - pytest.ini
+  consumer_feedback: []
+  bug_reports: []
+  incidents: []
+consumer_guidance:
+  recommended_for:
+  - understanding the historical design this scope split from; not for new integrations
+  not_recommended_for:
+  - new consumers — use markitect-tool, infospace-bench, or kontextual-engine instead, per their own scope-assessment
+    docs
+  known_limitations:
+  - actively being split apart; treat as reference/legacy, not a forward-looking target
+promotion_history: []
+---
+
+# MarkiTect Legacy Platform
+
+## Overview
+
+`markitect-main` is the legacy MarkiTect umbrella platform — an intelligent markdown engine and information-management system. It is actively being split into successor repos (`markitect-tool` for syntax-layer tooling, `infospace-bench` for the application layer, `kontextual-engine` for the knowledge-operations runtime); this entry is registered mainly so planners can see it is superseded rather than accidentally building against it.
+
+## Assessment notes
+
+### Discovery
+
+INTRODUCTION.md and SCOPE.md describe a mature, broad platform (schema validation, transclusion, LLM evaluation, infospace lifecycle); GUARDRAILS.md and DEPENDENCIES.md indicate an actively-managed but legacy codebase now being superseded by successor repos (markitect-tool, infospace-bench, kontextual-engine each reference a markitect-main-scope-assessment.md boundary doc).
+
+### Availability
+
+Extensive real application code (application/, domain/, services/ dirs) with both a Python package and a package.json; availability target is intentionally capped at A1 since the successor repos are the forward path, not this legacy platform.
+
+### Completeness
+
+First-pass honest assessment from the REUSE-WP-0017 coverage campaign
+(reuse-surface). No external consumer feedback exists yet; levels reflect
+scope-vs-intent documentation quality, not internal code quality.
+
+### Reliability
+
+No production consumer telemetry exists yet; reliability level is
+intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
+
+## Promotion checklist
+
+- [x] ID follows `capability.<domain>.<name>` pattern
+- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
+- [x] `external_evidence` is populated separately from `maturity`
+- [ ] Relations reference valid capability IDs (none yet)
+- [x] Index entry added in `registry/indexes/capabilities.yaml`

registry/indexes/capabilities.yaml

@@ -1,4 +1,20 @@
 version: 1
-updated: '2026-06-16'
+updated: '2026-07-06'
 domain: helix_forge
-capabilities: []
+capabilities:
+- id: capability.communication.markitect-legacy-platform
+  name: MarkiTect Legacy Platform
+  summary: Intelligent markdown engine and information-management platform treating documents as structured,
+    queryable information spaces with schema validation, transclusion, and LLM-driven evaluation; the
+    legacy umbrella now being split into markitect-tool, infospace-bench, and kontextual-engine.
+  vector: D3 / A1 / C1 / R0
+  domain: communication
+  status: draft
+  owner: markitect-main
+  path: registry/capabilities/capability.communication.markitect-legacy-platform.md
+  tags:
+  - markitect
+  - markdown
+  - legacy
+  consumption_modes:
+  - application (legacy, not recommended for new integration)

workplans/MARKITECT-WP-0001-statehub-bootstrap.md

@@ -0,0 +1,67 @@
+---
+id: MARKITECT-WP-0001
+type: workplan
+title: "Bootstrap State Hub integration"
+domain: communication
+repo: markitect-main
+status: finished
+owner: codex
+topic_slug: communication
+created: "2026-06-22"
+updated: "2026-06-22"
+state_hub_workstream_id: "dfc40b03-fe8e-49fe-b8d4-86eb1fe26b4a"
+---
+
+# Bootstrap State Hub integration
+
+Knowledge artifact management and markdown engine platform.
+
+## Review Generated Integration Files
+
+```task
+id: MARKITECT-WP-0001-T01
+status: done
+priority: high
+state_hub_task_id: "7455a381-a93d-4220-8f80-3b6ccf953cff"
+
+```
+
+Result 2026-06-22: SCOPE.md and INTRODUCTION.md reviewed; AGENTS.md confirmed.
+
+Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
+Replace generated placeholders with repo-specific facts where needed.
+
+## Verify Local Developer Workflow
+
+```task
+id: MARKITECT-WP-0001-T02
+status: done
+priority: high
+state_hub_task_id: "7e34bdab-aa49-49ca-b28a-b254725dd8db"
+
+```
+
+Result 2026-06-22: Documented make-based Python/JS workflow.
+
+Identify the repo's install, test, lint, build, and run commands. Add or refine
+those commands in the agent instructions so future coding sessions can verify
+changes confidently.
+
+## Seed First Real Workplan
+
+```task
+id: MARKITECT-WP-0001-T03
+status: done
+priority: medium
+state_hub_task_id: "35a64da7-dda9-4315-901d-88c6827432d9"
+
+```
+
+Result 2026-06-22: MARKITECT-WP-0002 already exists (TestDrive npm publication).
+
+Create the first implementation workplan for the repository's most important
+next change. After workplan file updates, run from `~/state-hub`:
+
+```bash
+make fix-consistency REPO=markitect-main
+```

workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md

@@ -0,0 +1,28 @@
+---
+id: MARKITECT-WP-0002
+type: workplan
+title: "TestDrive-JSUI — npm Publication"
+domain: communication
+repo: markitect-main
+status: backlog
+owner: codex
+topic_slug: communication
+created: "2026-06-22"
+updated: "2026-06-22"
+state_hub_workstream_id: "e203d487-01f1-494a-b14d-a436241a4c01"
+---
+
+# TestDrive-JSUI — npm Publication
+
+Backlog workstream for publishing the TestDrive JSUI package to npm.
+
+## Publication Readiness
+
+```task
+id: MARKITECT-WP-0002-T01
+status: todo
+priority: medium
+state_hub_task_id: "88b3c206-4d45-4bb3-bbb3-47443cdf2123"
+```
+
+Define package scope, versioning, and publication checklist for TestDrive-JSUI.