coulomb/testdrive-jsui
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
testdrive-jsui/docs/STANDALONE_PLAN_STATUS.md
tegwick 7bac45e5e9 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
2026-10-03 00:05:00 +02:00

3.5 KiB
Raw Permalink Blame History

STANDALONE_PLAN.md - reconciliation status

Reconciled 2026-10-02 by markitect-tool (request MARKITECT-WP-0002 P.3, from markitect-main). Verified against standalone repo HEAD 701341d (markitect-main pins older b8f13b4).

Decision

STANDALONE_PLAN.md (Python packaging, dated 2025-12-16) is NOT satisfied and is NOT superseded by the npm publication. The npm bundles (NPM_PUBLICATION_PLAN.md, JSUI-WP-0002) deliver the JavaScript editor only. The plan stays open and deferred: the Python rendering engine still lives in markitect-main (markitect/plugins/testdrive_jsui.py, which imports markitect.plugins.rendering / .base). No workplan is scheduled for it; that needs an owner decision (see "Open decisions").

Status per phase

Phase Plan State
1 Move rendering engine into src/testdrive_jsui/ (engine.py, standalone RenderingConfig, TestDriveJSUIEngine export, MarkiTect shim, deps) Move engine out of markitect Not done. src/testdrive_jsui/ holds only JavaScriptTestRunner and PythonJSBridge (testing helpers) plus empty core/, components/, utils/ packages. from testdrive_jsui import TestDriveJSUIEngine raises ImportError (verified).
2 Standalone examples (standalone_basic.py, Flask, Django) Python examples Not done. examples/ has HTML demos only.
3 Docs (docs/STANDALONE_GUIDE.md, README standalone section) Docs Partly wrong. README "Standalone Usage" documents TestDriveJSUIEngine, which does not exist (flagged in README as of this commit). No STANDALONE_GUIDE.
4 Isolated standalone tests Tests without MarkiTect Not done for the engine (nothing to test). Existing 15 pytest tests cover the runner/bridge and pass.
5 PyPI packaging sdist/wheel, publish Not done / not needed yet. pyproject.toml (0.1.0) builds an installable package, but it contains only the test helpers, not assets or an engine. Repository URLs in it are stale (github.com/markitect).

Success-criteria checklist: every item is unmet except "pytest passes" for the helper package; "no MarkiTect imports in standalone code" is trivially true because the engine is absent.

What the npm work does cover (separately)

JS bundles (esm/cjs/umd/min + css), 68 Jest tests, lockfile fix, hand-written types/index.d.ts. Python pip install testdrive-jsui still cannot render documents.

Open decisions (owner: Bernd)

  1. Pursue the plan (move engine here, break the markitect import) or drop it. Context: markitect-main is in a retirement transition (INTENT.md), so its successors may instead consume the npm package and need no Python engine.
  2. If dropped: remove README "Standalone Usage" Python section and the empty core/components/utils packages, and archive STANDALONE_PLAN.md with status dropped (not done).
  3. markitect-main submodule pin should move from b8f13b4 to a commit containing the lockfile fix (0deddaf and later).

Running Python tests under WSL

pytest-xvfb hangs at startup under WSL. Use:

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.