coulomb/markitect-main
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: restore legacy task backing and document successor transition
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e77b-9d43-7432-9301-e5cb6ad05ef6
This commit is contained in:
tegwick 2026-09-28 12:15:49 +02:00
parent d741661679
commit 8b9f599931
6 changed files with 189 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

105
workplans/MARKITECT-WP-0002-testdrive-jsui-publication.md
View file

@ -43,3 +43,108 @@ 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.
The following blocks restore file backing for the nine **existing** legacy P.1–P.9
tasks. Their State Hub UUIDs are preserved verbatim; no task is being created.
The file record IDs provide stable local references. The roadmap retains the
historical checklist and the current release acceptance criteria.
## P.1 — Decide repository structure (monorepo vs standalone)
```task
id: MARKITECT-WP-0002-T02
status: done
priority: high
state_hub_task_id: "81c03377-9083-42eb-be33-d202069afc02"
```
2026-09-28: Done: `.gitmodules` and the existing standalone checkout establish Option B. Publish the library from `testdrive-jsui`, not the Markitect root package.
## P.2 — Verify Markitect integration still works
```task
id: MARKITECT-WP-0002-T03
status: wait
priority: high
state_hub_task_id: "f518601b-396a-46a3-a5af-152bde48c313"
```
2026-09-28: Waiting for the pinned TestDrive submodule to be initialized and the JS/Python checks and actual Markitect view/edit behavior to be verified. The current checkout has no discoverable integration make target.
## P.3 — Resolve STANDALONE_PLAN.md status
```task
id: MARKITECT-WP-0002-T04
status: wait
priority: medium
state_hub_task_id: "d700098c-449d-44ba-ab02-cc3571bf6587"
```
2026-09-28: Waiting for the standalone package owner to reconcile its Python standalone plan. npm bundles do not establish Python packaging acceptance.
## P.4 — Pack and dry-run publish
```task
id: MARKITECT-WP-0002-T05
status: wait
priority: high
state_hub_task_id: "94dd2a30-fa38-471e-b19a-ed0913579524"
```
2026-09-28: Waiting for P.2/P.3 and standalone package fixes: resolve the missing advertised declaration file and verify ESM, CommonJS, browser and CSS consumption from an actual packed tarball. Run lint, tests, production build and publish dry-run; retain artifact evidence.
## P.5 — Create v1.0.0 release tag
```task
id: MARKITECT-WP-0002-T06
status: wait
priority: medium
state_hub_task_id: "d7c2ce00-00ad-431c-b036-64e727e49e48"
```
2026-09-28: Waiting for a verified candidate. Create the matching release tag only in the standalone repository after checking version availability and aligning manifest, lockfile and changelog.
## P.6 — Publish to npm and verify CDN
```task
id: MARKITECT-WP-0002-T07
status: wait
priority: high
state_hub_task_id: "8bcde75e-bca2-428e-893f-1d88036f746c"
```
2026-09-28: Waiting for package and integration gates, a verified tag, registry ownership/access, and npm/CDN publication receipts from the standalone maintainer.
## P.7 — Fresh install test in clean environment
```task
id: MARKITECT-WP-0002-T08
status: wait
priority: high
state_hub_task_id: "61d14b53-4ecf-4c0a-a676-b5530f706378"
```
2026-09-28: Waiting for publication. Install the published version and supported marked peer in an isolated consumer; verify initialization, edit/view behavior and styles without source-checkout references.
## P.8 — Create GitHub release
```task
id: MARKITECT-WP-0002-T09
status: wait
priority: medium
state_hub_task_id: "22d0cf0e-34a1-49f7-b1c1-7c5a1ae9ce16"
```
2026-09-28: Waiting for publication evidence. Use the standalone repository’s actual forge; the historical GitHub destination is not established.
## P.9 — Add npm badges to README and monitor
```task
id: MARKITECT-WP-0002-T10
status: wait
priority: low
state_hub_task_id: "75e785ac-4e35-4789-bcc2-d542db96d998"
```
2026-09-28: Waiting for verified publication. Add accurate badges in the standalone README and name responsibility for the one-week follow-up.