2026-06-22 21:44:38 +02:00
|
|
|
|
---
|
|
|
|
|
|
id: MARKITECT-WP-0002
|
|
|
|
|
|
type: workplan
|
|
|
|
|
|
title: "TestDrive-JSUI — npm Publication"
|
|
|
|
|
|
domain: communication
|
|
|
|
|
|
repo: markitect-main
|
2026-09-28 12:11:36 +02:00
|
|
|
|
status: blocked
|
2026-09-14 15:50:43 +02:00
|
|
|
|
flavor: implementation
|
2026-06-22 21:44:38 +02:00
|
|
|
|
owner: codex
|
|
|
|
|
|
topic_slug: communication
|
|
|
|
|
|
created: "2026-06-22"
|
2026-09-28 12:11:36 +02:00
|
|
|
|
updated: "2026-09-28"
|
2026-08-22 16:45:51 +02:00
|
|
|
|
state_hub_workstream_id: "e03ef262-5284-5dd3-92d2-dbd85c6b6159"
|
2026-06-22 21:44:38 +02:00
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# TestDrive-JSUI — npm Publication
|
|
|
|
|
|
|
2026-09-28 12:11:36 +02:00
|
|
|
|
Publication workstream for the standalone TestDrive-JSUI package.
|
|
|
|
|
|
The local readiness definition is complete; actual release remains blocked.
|
2026-06-22 21:44:38 +02:00
|
|
|
|
|
|
|
|
|
|
## Publication Readiness
|
|
|
|
|
|
|
|
|
|
|
|
```task
|
|
|
|
|
|
id: MARKITECT-WP-0002-T01
|
2026-09-28 12:11:36 +02:00
|
|
|
|
status: done
|
2026-06-22 21:44:38 +02:00
|
|
|
|
priority: medium
|
2026-08-22 16:45:51 +02:00
|
|
|
|
state_hub_task_id: "1852eca1-92e2-518e-bb21-9dffbeb32a4f"
|
2026-06-22 21:44:38 +02:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
Define package scope, versioning, and publication checklist for TestDrive-JSUI.
|
2026-09-28 12:11:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|