docs: retire STANDALONE_PLAN (Python engine move) as dropped
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 299063@bnt-lap001 Assistant-Session: 53eb1e1c-c13a-4277-9ce2-3702960d93f7
This commit is contained in:
parent
c79cfd19c9
commit
7bac45e5e9
4 changed files with 64 additions and 59 deletions
|
|
@ -217,7 +217,7 @@ make testdrive-jsui-test-all # Run all tests
|
|||
|
||||
## 📦 **Standalone Usage**
|
||||
|
||||
> **Not yet available:** `TestDriveJSUIEngine` still lives in MarkiTect (`markitect/plugins/testdrive_jsui.py`); the Python examples below do not work from this package alone. See [docs/STANDALONE_PLAN_STATUS.md](docs/STANDALONE_PLAN_STATUS.md). The JavaScript library (npm) is standalone.
|
||||
> **Python engine: dropped.** `TestDriveJSUIEngine` stays in MarkiTect (`markitect/plugins/testdrive_jsui.py`); this package does not provide it, and the Python examples below do not work from this package alone. See [docs/STANDALONE_PLAN_STATUS.md](docs/STANDALONE_PLAN_STATUS.md). The JavaScript library (npm) is the supported standalone artifact.
|
||||
|
||||
### As a Rendering Engine Plugin
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
> **STATUS (2026-10-02): OPEN / DEFERRED - not implemented, not superseded by the npm package.**
|
||||
> See [docs/STANDALONE_PLAN_STATUS.md](docs/STANDALONE_PLAN_STATUS.md) for the phase-by-phase reconciliation.
|
||||
> **STATUS (2026-10-03): DROPPED - not implemented.** The Python engine move is retired; the npm package is the supported standalone artifact.
|
||||
> Reconciliation and rationale: [docs/STANDALONE_PLAN_STATUS.md](docs/STANDALONE_PLAN_STATUS.md). Kept for history only.
|
||||
|
||||
# TestDrive-JSUI Standalone Reusability Plan
|
||||
|
||||
|
|
|
|||
112
TODO.md
112
TODO.md
|
|
@ -1,56 +1,56 @@
|
|||
# Todofile
|
||||
|
||||
This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync.
|
||||
|
||||
The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile).
|
||||
|
||||
The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact.
|
||||
|
||||
***
|
||||
|
||||
## [Unreleased] - *Active Vibe-Coding State* 💡
|
||||
|
||||
This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
|
||||
|
||||
### NPM Publication - Remaining Tasks
|
||||
|
||||
**Status**: Phases 1-6 complete ✅ (build system, bundling, testing)
|
||||
**Remaining**: Phases 7-9 (pre-publication, publication, post-publication)
|
||||
|
||||
#### Phase 7: Pre-Publication Setup
|
||||
- [ ] Run `npm pack` to create package tarball
|
||||
- [ ] Test packed version locally (`npm install ./testdrive-jsui-1.0.0.tgz`)
|
||||
- [ ] Setup npm account (`npm login` or create account)
|
||||
- [ ] Decide repository structure (separate repo vs monorepo)
|
||||
- [ ] Create git tag: `git tag -a v1.0.0 -m "Release v1.0.0"`
|
||||
- [ ] Run final pre-publish checks:
|
||||
- `npm run lint` (no errors)
|
||||
- `npm test` (all tests pass)
|
||||
- `npm run build:prod` (clean build)
|
||||
- `npm publish --dry-run` (verify what will be published)
|
||||
|
||||
#### Phase 8: Publication
|
||||
- [ ] Publish to npm: `npm publish`
|
||||
- [ ] Verify package on npmjs.com
|
||||
- [ ] Wait 5-10 minutes, then verify CDN availability:
|
||||
- jsdelivr: `https://cdn.jsdelivr.net/npm/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js`
|
||||
- unpkg: `https://unpkg.com/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js`
|
||||
- [ ] Create GitHub release from v1.0.0 tag
|
||||
- [ ] Test fresh install: `npm install testdrive-jsui marked`
|
||||
|
||||
#### Phase 9: Post-Publication
|
||||
- [ ] Add npm badges to README.md
|
||||
- [ ] Create live demo page (optional)
|
||||
- [ ] Setup GitHub Pages for demo (optional)
|
||||
- [ ] Create announcements (optional)
|
||||
- [ ] Monitor downloads and feedback
|
||||
|
||||
### Other Tasks
|
||||
- [ ] Make sure that Markitect integration still works fine
|
||||
- [ ] Update STANDALONE_PLAN.md and decide if it should be implemented
|
||||
|
||||
***
|
||||
|
||||
## Completed Tasks
|
||||
|
||||
*Recent completed tasks have been documented in CHANGELOG.md following Keep a Changelog format.*
|
||||
# Todofile
|
||||
|
||||
This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync.
|
||||
|
||||
The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile).
|
||||
|
||||
The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact.
|
||||
|
||||
***
|
||||
|
||||
## [Unreleased] - *Active Vibe-Coding State* 💡
|
||||
|
||||
This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
|
||||
|
||||
### NPM Publication - Remaining Tasks
|
||||
|
||||
**Status**: Phases 1-6 complete ✅ (build system, bundling, testing)
|
||||
**Remaining**: Phases 7-9 (pre-publication, publication, post-publication)
|
||||
|
||||
#### Phase 7: Pre-Publication Setup
|
||||
- [ ] Run `npm pack` to create package tarball
|
||||
- [ ] Test packed version locally (`npm install ./testdrive-jsui-1.0.0.tgz`)
|
||||
- [ ] Setup npm account (`npm login` or create account)
|
||||
- [ ] Decide repository structure (separate repo vs monorepo)
|
||||
- [ ] Create git tag: `git tag -a v1.0.0 -m "Release v1.0.0"`
|
||||
- [ ] Run final pre-publish checks:
|
||||
- `npm run lint` (no errors)
|
||||
- `npm test` (all tests pass)
|
||||
- `npm run build:prod` (clean build)
|
||||
- `npm publish --dry-run` (verify what will be published)
|
||||
|
||||
#### Phase 8: Publication
|
||||
- [ ] Publish to npm: `npm publish`
|
||||
- [ ] Verify package on npmjs.com
|
||||
- [ ] Wait 5-10 minutes, then verify CDN availability:
|
||||
- jsdelivr: `https://cdn.jsdelivr.net/npm/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js`
|
||||
- unpkg: `https://unpkg.com/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js`
|
||||
- [ ] Create GitHub release from v1.0.0 tag
|
||||
- [ ] Test fresh install: `npm install testdrive-jsui marked`
|
||||
|
||||
#### Phase 9: Post-Publication
|
||||
- [ ] Add npm badges to README.md
|
||||
- [ ] Create live demo page (optional)
|
||||
- [ ] Setup GitHub Pages for demo (optional)
|
||||
- [ ] Create announcements (optional)
|
||||
- [ ] Monitor downloads and feedback
|
||||
|
||||
### Other Tasks
|
||||
- [ ] Make sure that Markitect integration still works fine
|
||||
- [x] Update STANDALONE_PLAN.md and decide if it should be implemented (2026-10-03: dropped)
|
||||
|
||||
***
|
||||
|
||||
## Completed Tasks
|
||||
|
||||
*Recent completed tasks have been documented in CHANGELOG.md following Keep a Changelog format.*
|
||||
|
|
|
|||
|
|
@ -48,3 +48,8 @@ Python `pip install testdrive-jsui` still cannot render documents.
|
|||
pytest -p no:xvfb --no-cov
|
||||
|
||||
(15 passed). `--no-cov` also avoids the `--cov-fail-under=58` gate on a subset run.
|
||||
|
||||
|
||||
## Decision (2026-10-03)
|
||||
|
||||
Bernd decided to **retire** the Python standalone plan; its status is `dropped`, not done. Rationale: the npm release does not need the Python engine, the only known consumer (`markitect-main`) keeps its own adapter and is itself being retired, and phases 1, 2, 4 and 5 were never started. If a successor repo later needs a reusable Python engine, start a fresh plan there rather than reviving this one.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue