docs(m07): close ZCode feasibility track — owner Stage-2 NO-GO decision D-047 (issue #92) #103

Merged

adrian.tkacz merged 1 commit from docs/close-zcode-m07 into develop

2026-09-20 00:13:02 +00:00

kilo commented

2026-09-20 00:01:35 +00:00

Member

Summary

Program closeout of the ZCode feasibility track (M07) after the owner's post-Stage-1 decision. Documentation, decision records and Forgejo issue state only — no runtime code, no contract change, no adapter implementation.

docs/decisions.md: new D-047 — owner product decision (2026-09-20): M07 Stage 1 COMPLETE, Stage 2 NO-GO / cancelled; no ZCode execution adapter is planned; undocumented internal IPC / unofficial wrappers are explicitly not an acceptable implementation path; reopen only on an official supported ZCode programmatic interface (or other official supported integration surface) AND applicable vendor terms permitting the intended use; Z.ai Coding Plan execution stays on M04's generic HTTP-provider path. U-013 marked resolved by Stage-1 evidence + owner decision, with its historical question list and Stage-1 answer provenance preserved unchanged.
docs/roadmap.md / docs/architecture.md: M07 rows, dependency prose, topology and module-map table updated so ZCode Stage 2 is no longer presented as planned implementation work; M07's existence and Stage-1 evidence (docs/zcode-adapter-stage1-evidence.md) are preserved as history, nothing deleted or renumbered.
docs/product.md / AGENTS.md: gateway resource lists no longer name ZCode as an expected native-worker backend.
docs/providers.md: M04 generic-adapter section now states explicitly that the Z.ai preset is the vendor-documented OpenAI-compatible Coding Plan endpoint (the supported subscription-backed Z.ai execution channel), that ZCode Desktop is not an M04 backend, and that the M07 NO-GO does not remove Z.ai HTTP/API support.

Deliberately unchanged

docs/zcode-adapter-stage1-evidence.md — stays as the dated historical evidence record (its bottom line was a research recommendation; D-047 records the owner's decision).
Milestone numbering (M01–M10), all prior decisions, and the frozen D-042 contracts (the local_app_adapter execution channel remains a contract value).
Issue #89 scope — only a clarifying comment is added there; no implementation work is started.

Reopen condition (recorded, not implemented)

M07 may be reconsidered only when ZCode ships an official supported programmatic interface (CLI/API/SDK/headless automation surface) — or another official supported integration surface becomes available — AND applicable vendor terms permit the intended use, via a new superseding decision. No repository-side polling/monitoring code is added.

Validation gate

uv sync --only-dev ✅
make check ✅ (1183 tests OK)
uv run basedpyright ✅ (0 errors, 0 warnings, 0 notes)
git diff --check ✅
make package-check ✅ (all checks passed)

Refs: #92 (closeout), #89 (clarification), #85 (program root).

## Summary Program closeout of the ZCode feasibility track (M07) after the owner's post-Stage-1 decision. Documentation, decision records and Forgejo issue state only — **no runtime code, no contract change, no adapter implementation**. - **`docs/decisions.md`:** new **D-047** — owner product decision (2026-09-20): M07 Stage 1 COMPLETE, Stage 2 **NO-GO / cancelled**; no ZCode execution adapter is planned; undocumented internal IPC / unofficial wrappers are explicitly not an acceptable implementation path; reopen only on an official supported ZCode programmatic interface (or other official supported integration surface) AND applicable vendor terms permitting the intended use; Z.ai Coding Plan execution stays on M04's generic HTTP-provider path. **U-013** marked resolved by Stage-1 evidence + owner decision, with its historical question list and Stage-1 answer provenance preserved unchanged. - **`docs/roadmap.md` / `docs/architecture.md`:** M07 rows, dependency prose, topology and module-map table updated so ZCode Stage 2 is no longer presented as planned implementation work; M07's existence and Stage-1 evidence (`docs/zcode-adapter-stage1-evidence.md`) are preserved as history, nothing deleted or renumbered. - **`docs/product.md` / `AGENTS.md`:** gateway resource lists no longer name ZCode as an expected native-worker backend. - **`docs/providers.md`:** M04 generic-adapter section now states explicitly that the Z.ai preset is the vendor-documented OpenAI-compatible Coding Plan endpoint (the supported subscription-backed Z.ai execution channel), that **ZCode Desktop is not an M04 backend**, and that the M07 NO-GO does not remove Z.ai HTTP/API support. ## Deliberately unchanged - `docs/zcode-adapter-stage1-evidence.md` — stays as the dated historical evidence record (its bottom line was a research recommendation; D-047 records the owner's decision). - Milestone numbering (M01–M10), all prior decisions, and the frozen D-042 contracts (the `local_app_adapter` execution channel remains a contract value). - Issue #89 scope — only a clarifying comment is added there; no implementation work is started. ## Reopen condition (recorded, not implemented) M07 may be reconsidered only when ZCode ships an official supported programmatic interface (CLI/API/SDK/headless automation surface) — or another official supported integration surface becomes available — AND applicable vendor terms permit the intended use, via a new superseding decision. No repository-side polling/monitoring code is added. ## Validation gate - `uv sync --only-dev` ✅ - `make check` ✅ (1183 tests OK) - `uv run basedpyright` ✅ (0 errors, 0 warnings, 0 notes) - `git diff --check` ✅ - `make package-check` ✅ (all checks passed) Refs: #92 (closeout), #89 (clarification), #85 (program root).

kilo added 1 commit

2026-09-20 00:01:35 +00:00