markitect-main/workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md
tegwick d741661679
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
docs: close publication readiness and record remaining release blockers
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e77b-9d43-7432-9301-e5cb6ad05ef6
2026-09-28 12:11:36 +02:00

45 lines
1.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: MARKITECT-WP-0002
type: workplan
title: "TestDrive-JSUI — npm Publication"
domain: communication
repo: markitect-main
status: blocked
flavor: implementation
owner: codex
topic_slug: communication
created: "2026-06-22"
updated: "2026-09-28"
state_hub_workstream_id: "e03ef262-5284-5dd3-92d2-dbd85c6b6159"
---
# TestDrive-JSUI — npm Publication
Publication workstream for the standalone TestDrive-JSUI package.
The local readiness definition is complete; actual release remains blocked.
## Publication Readiness
```task
id: MARKITECT-WP-0002-T01
status: done
priority: medium
state_hub_task_id: "1852eca1-92e2-518e-bb21-9dffbeb32a4f"
```
Define package scope, versioning, and publication checklist for TestDrive-JSUI.
Result 2026-09-28: Defined package ownership, distribution scope, versioning,
and an evidence-based release checklist in
[the existing publication roadmap](../roadmap/testdrive-jsui-publication/PLAN.md).
The repository split already exists: `.gitmodules` points to the standalone
`coulomb/testdrive-jsui` repository. No new tasks or workplans were created.
Remaining publication work stays in the roadmap's existing P.2–P.9 steps.
This workplan is **blocked**, despite T01 being done, because completing a
readiness definition does not establish a published release. The standalone
package owner must resolve its missing advertised declaration file, validate
packed consumer entry points, and supply release evidence. Markitect's pinned
submodule must also be initialized and its view/edit integration verified.
No release tag, registry publication, or browser acceptance is claimed.