MDS Roadmap — Post-v0.1.0 Progress Tracker

[dean0x]

MDS Roadmap

Master tracking issue for all planned work after the v0.1.0 release. Each item links to a detailed issue with its own PRD.

Status Key

• ✅ Complete
• 🚧 In Progress
• ⚪ Not Started

---

Checkbox convention. A checked box means the referenced issue is closed. Partial
progress is recorded as a prose bullet with no checkbox, naming what landed and what
remains. This exists because (partial) / (doc half) qualifiers previously allowed
incomplete work into sections headed "landed" — readers scan checkboxes and section
headings before qualifier text.

v0.2.0 — Language Enrichment ✅

The core language gets the features users will hit first. Focus: make templates self-sufficient without external preprocessing.

• feat: built-in functions (upper, lower, join, trim, length, etc.) #53 — Built-in functions (upper, lower, join, trim, length, etc.)
• feat: default function arguments #54 — Default function arguments
• feat: logical operators in @if conditions (&&, ||) #55 — Logical operators in @if conditions (&&, ||)
• chore: re-enable wasm-opt for WASM size optimization #68 — Re-enable wasm-opt for WASM size optimization
• feat: expression support in @for and @if directives #74 — Expression support in @for and @if directives
• feat: frontmatter imports #75 — Frontmatter imports
• Add CODE_OF_CONDUCT.md (Contributor Covenant 2.1) #38 — Add CODE_OF_CONDUCT.md — carried from v0.2.0, landed in v0.4.0 Wave 1 (PR v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308)

Released: 2026-06-06 — v0.2.0

---

v0.3.0 — Production Readiness ✅

Bridge MDS from "template language" to "production LLM input format." Add the developer workflow tooling that makes daily use pleasant.

Released: 2026-06-28 — v0.3.0

Headline Features (Complete)

• feat: structured JSON output (chat message arrays) #56 — Structured output → shipped as the intrinsic output format: @message templates compile to a JSON array, all others to Markdown; mixed content is a hard error (mds::mixed_content)
• feat: mds watch command (file watcher with auto-recompile) #57 — mds watch command (file watcher with auto-recompile) — merged in feat(cli): add mds watch subcommand with auto-recompile on save #93
• feat: template inheritance (@extends / @block) #58 — Template inheritance (@extends / @block) — merged in feat(core): template inheritance via @extends / @block (#58) #95
• feat: verify & harden hot-reload (HMR) across bundler plugins — Vite, Rollup, Webpack, Rspack #94 — Hot-reload (HMR) across bundler plugins (Vite, Rollup, Webpack, Rspack) — merged in feat(ecosystem): verify & harden HMR across bundler plugins + add @mdscript/rspack-loader #105
• rspack-loader: verify @rspack/core 2.x compat and widen peer range to ^1.0.0 || ^2.0.0 #106 — rspack-loader: verify @rspack/core 2.x compat + widen peer to ^1.0.0 || ^2.0.0 — merged in feat(ecosystem): verify & harden HMR across bundler plugins + add @mdscript/rspack-loader #105

Tech-Debt Sweep (Complete)

Do-set — all 11 landed in PR #117 (88ddbcc):

• tech-debt: Deduplicate arity-check logic across evaluator and validator #71 — Deduplicate arity-check logic across evaluator and validator
• tech-debt: Extract generic quote-aware byte scanner from parser_helpers.rs #72 — Extract generic quote-aware byte scanner from parser_helpers.rs
• Unify CondValue and Expr literal types #78 — Unify CondValue and Expr literal types
• Delegate parse_interpolation_expr to parse_expr_inner #79 — Delegate parse_interpolation_expr to parse_expr_inner
• tech-debt: Share @for loop machinery between text and messages modes #88 — Share @for loop machinery between text and messages modes
• tech-debt: Add resolver-backed compile_messages_file for CLI messages-mode symlink parity #89 — Messages-mode symlink parity — superseded by the intrinsic output format
• tech-debt: Harden CLI/NAPI boundaries with escaping and injection tests #90 — Harden CLI/NAPI boundaries with escaping and injection tests
• tech-debt: Parse WASM return shape at FFI boundary #91 — Parse WASM return shape at FFI boundary (canonical method manifest / backend contract)
• tech-debt: Split resolver.rs into inheritance and frontmatter submodules #96 — Split resolver.rs into inheritance and frontmatter submodules
• tech-debt: Extract build_merged_extends_scope resolver helper #99 — Extract build_merged_extends_scope resolver helper
• tech-debt: Extract resolve_intermediate_base resolver helper #100 — Extract resolve_intermediate_base resolver helper

Already Closed (verified done): #98, #101, #80, #77

---

v0.4.0 — Ecosystem Expansion ✅ SHIPPED

Expand reach beyond JS/TS. Add the quality-of-life tooling that mature languages provide.

Released: 2026-09-02 — tag v0.4.0 at 6673dc3,
cut by release run 33569514359 (attempt 2, after a
crates.io token rotation). Published and independently verified: mds-core and mds-cli at 0.4.0 on crates.io
(not yanked); all 15 @mdscript/* npm packages at 0.4.0 with SLSA provenance (8 published packages + 7 native
platform packages); the GitHub Release is live. The v0.4.0 milestone is closed (0 open / 18 closed).
Wave 1 closed in PR #308 (339df37), watch-correctness in PR #323 (b34d8ac), the dogfood defect sweep in
PR #335 (0cd08d6), release prep in PR #338 (df2fe71), the version bump in PR #343 (c0aa732), and the
CI-history gate fix in PR #344 (6673dc3).

Ship gate — cleared ✅

• Fix the CHANGELOG LintConfig::from_rules entry — it documented a deprecation with migration path for a function REMOVED in 339df37. Nothing published ever exposed LintConfig::from_rules since lint/config.rs did not exist at v0.3.0, so it was not breaking; the entry now sits under ### Removed with the migration text dropped.
• Clean the working tree: uncommitted .gitignore edit (+!.devflow/conventions.md). RELEASING.md pre-flight requires a clean working tree.
• node scripts/bump-version.mjs 0.4.0, landed via CI-gated PR chore(release): v0.4.0 #343 (c0aa732), verified with node scripts/verify-pr-checks.mjs (PF-017) and merged with the exact printed command.
• git tag -a v0.4.0 -m v0.4.0 && git push origin v0.4.0

Two release-prep fixes landed on main before the tag: PR #338 (df2fe71) — aarch64-musl link flag, linux-x64-musl now genuinely musl-linked behind a readelf gate, setup-zig pin, verifier allowance — and PR #344 (6673dc3) — the CI-history gate now asserts from the CI workflow run rather than branch protection. The release run itself needed a second attempt after a crates.io token rotation; recovery was a rerun of the staged run, never a re-tag. The run's gates all passed at 6673dc3: version-gate (synchronized versions, live credential probe, CI-history assertion), the A3 napi name↔loader gate, and the readelf musl-linkage assertion on both musl legs.

Headline Features — landed ✅

• feat: Python bindings (PyO3) #59 — Python bindings (PyO3) — PR feat(python): native Python bindings via PyO3 (mdscript) #131
• feat: mds fmt — auto-formatter #60 — mds fmt (auto-formatter) — PR feat: mds fmt auto-formatter #137
• feat: mds lint — static analysis and diagnostics #61 — mds lint (static analysis) — PR feat: mds lint — static analysis and diagnostics (#61) #171
• feat: source maps for compiled output #62 — Source maps for compiled output
• Interpolation syntax migration: {x} → {{x}} (v0.4.0) #236 — BREAKING: {x} → {{x}} double-brace interpolation, with a lint --fix migration path — PR feat!: double-brace {{x}} interpolation with lint --fix migration (v0.4.0) #237 (aac4070)

Fix / hardening waves — landed ✅

• Indented code fences are not recognized; {…} inside them is interpolated #149 Blank line after frontmatter is stripped on compile #150 Blank lines at @block/@end boundaries are consumed (blank runs collapse to 1) #151 --set x=true coerces to boolean, silently breaking x == "true" #152 Interpolation error suggests the wrong escape; hint \{{ fails, \{ works #153 Base-only frontmatter keys are in scope but omitted from the child output frontmatter #154 — v0.4.0 bug batch: indented + wide fences, interior-verbatim whitespace, --set-string type safety, merged @extends frontmatter, \{ hint — PR fix!: v0.4.0 bug batch — fences, whitespace, type safety, @extends FM (#149–#154) #161 (3ce9f1d)
• core: base_path relative imports fail on Windows for string sources (verbatim canonicalize + '/' join) #133 — Windows base_path relative-import resolution for string sources — PR fix(core): resolve string-source @import on Windows verbatim paths #146
• Add per-branch offset to IfBlock.elseif_branches for precise @elseif diagnostics #181 — per-branch offsets on IfBlock.elseif_branches for precise @elseif diagnostics — PR fix: v0.4.0 remediation — dogfooding blockers, bug batch, UX polish, docs sweep #196 (3aef465)
• First dogfood remediation: blockers, bug batch, span attribution, UX polish, docs sweep — PR fix: v0.4.0 remediation — dogfooding blockers, bug batch, UX polish, docs sweep #196 (3aef465)
• lint --fix: full-block-span removal for block-spanning Tier A fixes (empty-block, unreachable-branch) #172 — lint --fix full-block-span removal for block-spanning Tier A fixes; CLI/config UX; typed Python lint; WASM guard → 850K — PR fix: v0.4.0 dogfooding remediation — block-span lint fixes, span attribution, CLI/config UX, binding alignment, docs (#172 batch) #228 (f06a2d1)
• Harden terminal-escape rendering across all MdsError variants (CWE-150) #176 — Harden terminal-escape rendering across all MdsError variants (CWE-150) — PR fix: harden terminal-escape rendering across all MdsError variants (CWE-150) #253 (b681129). Render path rebuilt per PF-014: sanitize inputs, not frames.
• atomic_write_file: metadata() failure silently yields mode 0600 via .ok() #225 — atomic_write_file warns on metadata() failure instead of silently falling back to mode 0600 — PR fix: atomic_write_file: warn on metadata failure instead of silently using 0600 #240 (de8857d)
• atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226 — doc half only; issue remains OPEN. PR doc: add note about atomic_write_file not preserving hard links, ACLs, xattrs, owner/group #239 (acb8a86) landed the limitation note at crates/mds-cli/src/output.rs:600-602 and RELEASING.md:164, closing the "won't fix: hard links" documentation deliverable. The implementation half did not land: atomic_write_file (output.rs:603-664) still restores only the Unix mode (output.rs:641); no copyfile/setxattr/chown call exists anywhere in crates/. ACLs, xattrs and owner/group remain unpreserved — tracked under "Deferred past v0.4.0 › Write path" below.
• PRE-TAG DECISION: mark LintDiagnostic as #[non_exhaustive] #259 — BREAKING: LintDiagnostic marked #[non_exhaustive] + constructor added — PR feat(mds-core)!: mark LintDiagnostic #[non_exhaustive] and add constructor [#259] #286 (d8766af)
• release: workflow_dispatch path fails GH006 on protected main (prepare can't push) #127 — release machinery hardened: broken workflow_dispatch -f version= path deleted, cargo publish idempotency check, bounded crates.io index poll, bump-version.mjs CHANGELOG link-table corruption fixed, examples/ outputs gitignored + examples-gitignore-coverage CI job — PR chore: harden release machinery (5 independent fixes) #287 (cb44b56)
• fix(deps): clear Dependabot dev-dep advisories (vite, js-yaml, esbuild) #125 (partial) — relax 30-day soak pins for vite and js-yaml — PR chore: relax 30-day soak pins for vite and js-yaml (deferred from #125) #266 (c8b4062)
• Release hygiene: fix config drift and close gold-standard gaps #182 — config-drift cleanup only; issue remains OPEN (milestone v0.5.0). PR chore(docs): remove dead Discussions link and stale version table (#182) #291 (113f472) removed the dead Discussions link (.github/ISSUE_TEMPLATE/config.yml) and the stale supported-versions table (SECURITY.md) — both already listed under "Config drift — RESOLVED, no longer in scope" in Release hygiene: fix config drift and close gold-standard gaps #182's own body. None of the six gold-standard gaps were closed by chore(docs): remove dead Discussions link and stale version table (#182) #291. See "Deferred past v0.4.0 › Release infrastructure" below.

Wave 1 — pre-tag set ✅ all 12 closed in PR #308 (339df37)

Wire format — bytes consumers parse; cheap today, a semver event after the tag

• lint: diagnostic ordering — sort by offset within a file #202 — lint JSON diagnostics emit in rule-dispatch order, not source order. Array order is part of the --format json contract.
• lint: unused-import span should anchor at the unused name in multi-name imports #203 — unused-import span is hardcoded to the @import keyword: wrong offset/length in JSON output, wrong squiggle for any future LSP client.
• CLI quiet-mode and directory-summary consistency gaps: build --quiet prints summary while lint/check/fmt suppress; lint has no directory summary #216 — build.rs:1596 prints the directory summary unconditionally, violating the documented --quiet contract; lint has no aggregate summary at all.

Decisions resolved

• DECISION NEEDED: unify stdin label conventions across lint/fmt/build — three conventions in four contexts affect the --format json wire format #211 — stdin labels. Resolved: stdin label unified to <stdin> across all four CLI subcommands. Bindings (napi/WASM/Python) still emit input.mds and mds::STRING_SOURCE_MAP_LABEL is unchanged. Documented at spec.md:1033, :1071.
• Core: warn on unknown lint rule names instead of silently accepting them #224 — unknown lint rule names. Resolved: unknown rule names now warn and continue; from_rules_checked returns an unknowns report; from_rules removed.

Deprecation window

• Deprecate apply_fixes from public mds-core API and schedule removal — 0 callers since apply_fixes_incremental shipped #209 — deprecate apply_fixes (0 production callers). Deprecated at v0.4.0, scheduled for removal at v0.5.0.

TS public surface

• Expose basePath on CompileOptions to match LintOptions #180 — BUG (live, shipped): basePath is accepted by assertKnownKeys and then silently discarded by compileOpt()/varsOpt(). Affects both compile and check in the published npm package. Fixed.
• Add lint/lintFile/lintVirtual exports to browser.ts (pre-existing gap) #215 — browser.ts lint exports added (lint + lintVirtual only — lintFile is not implementable in a browser).
• options.ts second pass: value-type validation, indexed-access safety, and varsOpt type narrowing #213 — options.ts second pass: value-type validation, indexed-access safety, and varsOpt type narrowing.

Community / release hygiene

• Add CODE_OF_CONDUCT.md (Contributor Covenant 2.1) #38 — add CODE_OF_CONDUCT.md (Contributor Covenant 2.1). Carried since v0.2.0.

Release-safety gates

• ci: reject control bytes and bidi codepoints in tracked source (authoring toolchain injects live ESC) #288 — reject control bytes and bidi codepoints in tracked source. The authoring toolchain has injected a live 0x1B three times; b94ef80 stripped the most recent one from the escape-handling PR itself. node scripts/verify-no-control-bytes.mjs added to CI; scripts/hooks/pre-commit gate for local development.
• process: CI checks can be cancelled and an --admin squash-merge will not notice #289 — CI checks can be cancelled and an --admin squash-merge will not notice. node scripts/verify-pr-checks.mjs added; required before any --admin merge.

Unplanned, forced during the wave

• perf(wasm): size optimization pass — flag tuning, sort_unstable, CI pin #300 — WASM shrunk 2,024 bytes via wasm-opt flags + sort_unstable rather than raising the 850K budget.
• refactor(python)!: rename distribution to markdown-script (import markdown_script) #306 — Python package renamed to markdown-script (ADR-012). Note: mdscript on PyPI is a genuine dormant 2021 project (owner Inoft.Robinson) with a colliding top_level.txt, not a squat; zero consumers; publish = false; no PyPI step in release.yml.
• fix: recover 21 unpushed release-gate commits and share feature KBs #307 — recovered 21 unpushed release-gate commits from a stale-head squash.

Watch correctness — landed ✅ PR #323 (b34d8ac)

• mds watch silently loses edits made during startup #317 — mds watch silently lost a save made during startup; both modes now arm change detection before publishing first output.
• mds watch idle-tick self-heal never fires when irrelevant filesystem events stream continuously #319 — the self-heal idle tick could be starved indefinitely by event traffic; the deadline is now an absolute instant.
• mds watch directory mode has no content-level backstop for cross-root dependencies #321 — directory mode lost edits to cross-root @import dependencies; a failed compile no longer discards the dependency list, and the idle probe now diffs (mtime, size) across all tracked sources and dependencies.

New CI job watch-startup-race (ci.yml:395) runs the suite with the startup-race probe enabled.

✅ Did not block the tag — since resolved

• Rename Python distribution to markdown-script (import markdown_script) + register on PyPI #292 — register markdown-script on PyPI — CLOSED, satisfied. markdown-script has been live on PyPI since v0.4.2 (2026-09-03), the first Python publication (7 cp311-abi3 wheels + sdist, PEP 740 attestations, OIDC trusted publishing). The rename had already landed for v0.4.0 (pyproject.toml name = "markdown-script", ADR-012); v0.4.0 itself shipped nothing Python because release.yml had no PyPI step at the time. The wheel matrix and publishing work is Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132, closed under v0.4.2.

⚪ Deferred past v0.4.0

Everything here was out of scope for the v0.4.0 tag and remains open. Items that have since
been scoped to v0.4.3 are listed in the v0.4.3 section below and are not repeated here.

• Source maps follow-ups: Refactor oversized source-map core functions (CX-1, CX-2, CX-3) #184, Source-map architecture hardening (ARCH-2, ARCH-3) #185, Source-map performance polish (PERF-2, PERF-3, PERF-4) #186, Source-map test-coverage gaps (TEST-4, TEST-5, TEST-6) #187, Source-map cosmetic/consistency nits (TS-1, TS-2, CON-2, CON-4, CX-6, PY-2) #188, source maps: --out-dir far from source produces root-climbing relative sources (sourceRoot design) #197, source maps: static-run mapping granularity — multi-line static runs map only their first line #198, Python: refactor source-map tests toward per-surface golden files to prevent cross-surface divergence #221
• Lint internals: Refactor mds lint CLI per-file dispatch spine #173, Centralize Severity string parsing across bindings #175, Consolidate lint entry-file reads through NativeFs (single source of truth) #179, Restructure apply_fixes_incremental: decompose 135-line function, collapse impossible-state guard, deduplicate regression triple #208, lint fix-pipeline test hardening: dedup coverage and cross-rule validation #230, cosmetic consistency sweep: tone/naming/style across lint rules and docs #231, lint rules: simplify check_if_block and sortedness guard logic #235
• Escape/render follow-ups from Harden terminal-escape rendering across all MdsError variants (CWE-150) #176: refactor: constrain complexity of run_watch_file #256, refactor: unify eprint_error settle patterns in watch.rs #257, perf: eliminate double allocation in render_error_sanitized #260, refactor: rename render_error_sanitized to clarify it is the sanitization boundary #261, refactor: relocate sanitize_control_chars to dedicated module #262, docs: add normative spec section for serialized error shape #263, test: adopt pytest.raises idiom for E11 error test #264, Reject control characters in filenames at the input boundary #265
• Errors and spans: errors: remaining span-less errors — frontmatter name collisions and other sites without byte offsets #205, resolver: messages-mode @extends type_mismatch span can mis-attribute base-origin conditions (same class as PR #196 markdown fix) #207, evaluator: body_origin manual LIFO restore → RAII guard (future-proofing) #233
• CLI/UX open questions: --set duplicate key silently last-wins — warn? #200 (closed), find_project_root fallback UX in unmarked trees (.mdsroot discoverability) #201 (closed), build tooling: wasm-opt local version drift (self-provisioned 117 vs CI-pinned Binaryen 129) — add a version check #206
• Bindings and ecosystem: tech-debt: bound depythonize recursion depth in native bindings (stack-overflow hardening) #134, tech-debt: centralize MAX_MODULE_COUNT (duplicated in mds-python and mds-wasm) #135, test: cross-binding parity gaps — type_mismatch (napi) + @extends merged-FM (python) #164, Python test: mds_cli_bin fixture silently falls through on malformed MDS_CLI_BIN env var — support CARGO_TARGET_DIR/--target layouts #214, Python binding polish: optimize to_dict() and simplify files() closure chain #232, examples/python/demo.py: harden None-safety for strict mypy/pyright #234
• Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132 — Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) — shipped in v0.4.2 (2026-09-03): markdown-script is live on PyPI with 7 cp311-abi3 wheels + sdist and PEP 740 attestations (the cp314t free-threaded wheel is not in the shipped set). Name registration Rename Python distribution to markdown-script (import markdown_script) + register on PyPI #292 is closed as satisfied.
• Rust cleanups and module decomposition: Consolidate MAX_DEPTH from 4 per-file constants to one shared constant adjacent to collect_mds_files #218, Rust minor cleanups from PR #196 review: bounded-loop form, discarded infallible Result, saturating_sub, unwrap_or defensibility, error label wording #219 (every line ref stale; finalize_sub does not exist in sourcemap.rs), Tech debt: decompose oversized modules — resolver.rs (2554L) and build.rs (2020L) block safe incremental work #223, build.rs DRY: consolidate embed_sources warnings and sidecar/stdout ladder duplication #229, perf: collect_mds_files eagerly walks excluded dirs to count .mds files — fixed FS cost per run #238
• Security hardening: security: frontmatter YAML parse exposed to alias-bomb / deep-nest DoS (uncatchable at FFI) #162 (frontmatter YAML alias-bomb / deep-nest DoS)
• Write path: atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226 (hard links / ACLs / xattrs / owner-group — doc half landed in doc: add note about atomic_write_file not preserving hard links, ACLs, xattrs, owner/group #239)
• Repo hygiene: examples/ gitignore footgun: hand-authored .md/.json silently ignored by the catch-alls #290 (untouched — scripts/hooks/pre-commit in v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308 is the ci: reject control bytes and bidi codepoints in tracked source (authoring toolchain injects live ESC) #288 control-byte gate, a different thing)
• Type rename: Public TS: rename FileOptions to CompileFileOptions for intent clarity (breaking — target v0.5.0) #222 → v0.5.0, conditional on shipping a deprecated FileOptions alias
• Correctness / reliability: build: empty directory build exits 0 — silent success hazard in CI #204, output.rs path helpers fail-open on strip_prefix edge cases and non-UTF-8 paths #217, debug_assert!-only invariants silently degrade in release builds (3 sites) — PF-005 #220, build::write_output still uses truncate-then-write (non-atomic) for compiled artifacts #227
  • output.rs path helpers fail-open on strip_prefix edge cases and non-UTF-8 paths #217 — cited output.rs:177-183 stale; pattern moved to lint.rs:321-333
  • debug_assert!-only invariants silently degrade in release builds (3 sites) — PF-005 #220 — the assert lives at resolver.rs:2437 and guards a UTF-8 char-boundary precondition, not a sortedness invariant. It is also not the last remaining instance: there are 3 sites — resolver.rs:2437, resolver/inheritance.rs:77, resolver/inheritance.rs:174. The issue has been retitled accordingly.
  • build::write_output still uses truncate-then-write (non-atomic) for compiled artifacts #227 — sequence with its prerequisite: routing build::write_output through atomic_write_file trips the metadata() warning branch fix: atomic_write_file: warn on metadata failure instead of silently using 0600 #240 added at output.rs:459-472, which spuriously fires on first build when the output file does not yet exist. Fix that branch in the same change.
• Carried tech-debt: tech-debt: reduce Value cloning in evaluate_expr Var lookups #81, tech-debt: carry base-source identity through splice_skeleton for base-default block spans #114, tech-debt: minimize FileSystem trait — remove production-dead normalize base!="" branch #155, tech-debt: centralize block-opener keyword literals (A1) #156, tech-debt: mirror broken-pipe handling to stderr (R3) #157, tech-debt: write-path TOCTOU hardening — openat/O_NOFOLLOW (S1) #160, perf: Arc<str> hoist for per-file source in render_diag_human #255
  • tech-debt: minimize FileSystem trait — remove production-dead normalize base!="" branch #155 — deferred by explicit decision. It touches the path-traversal and symlink guards; a second FileSystem trait break in v0.5.0 is cheaper than a security regression before the tag.
• Release infrastructure: ci: add cargo-deny / cargo-audit supply-chain gate #136, ci(wasm): pin wasm build toolchain for deterministic size; re-tighten size budget #128, test: flaky cli_watch.rs::watch_ctrl_c_prints_stopped_watching (timing) #129, ci: add a windows-latest leg to the rust CI job (Rust suite is ubuntu-only) #147, ci: SHA-pin GitHub Actions + assert lockfile version in verify-versions.mjs #163, Release hygiene: fix config drift and close gold-standard gaps #182 — none of these were scoped to v0.4.1. The five follow-ups the v0.4.0 release run surfaced in its own pipeline (ci(release): move both musl zig wrappers to cargo-zigbuild's maintained linker-arg filter #339, ci(release): load-test the linux-x64-musl addon on Alpine before upload #340, scripts(verify-pr-checks): key the skipped-publish allowance on the release.yml check suite, not the job name #341, ci(release): release.yml's build matrix never runs on pull_request #342, ci(release): validate CARGO_REGISTRY_TOKEN against crates.io in the version-gate probe (security-08 gap) #345) are in the v0.4.3 section below.
  • ci(wasm): pin wasm build toolchain for deterministic size; re-tighten size budget #128 — half-done: toolchain pinned at ci.yml:77; budget NOT re-tightened, still -gt 850000 at ci.yml:149
  • test: flaky cli_watch.rs::watch_ctrl_c_prints_stopped_watching (timing) #129 — NOT fixed by fix(watch): eliminate silent edit loss in mds watch startup and cross-root dependencies #323: test survives at cli_watch.rs:1108, 100ms sleep at :1151 unchanged
  • ci: add a windows-latest leg to the rust CI job (Rust suite is ubuntu-only) #147 — the rust job is bare runs-on: ubuntu-latest at ci.yml:21-24, no matrix; the windows matrix at :160 belongs to the js job
  • ci: SHA-pin GitHub Actions + assert lockfile version in verify-versions.mjs #163 — 10 of 58 uses: pinned, all 8 new pins incidental to ci(wasm): pin wasm build toolchain for deterministic size; re-tighten size budget #128; 48 float
  • Release hygiene: fix config drift and close gold-standard gaps #182 — 2 of 6 done. Done: bounded crates.io index poll (release.yml:325-347) and cargo publish idempotency (:317-324, :353-359), both from PR chore: harden release machinery (5 independent fixes) #287 (cb44b56, predating v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308); the npm-side idempotency check (:464-477) landed in v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308 itself (339df37). Not done: OIDC trusted publishing (tokens still live at :315, :351, :378 — the id-token: write at :373 is npm provenance, not trusted publishing), SHA256SUMS + build-provenance attestations (:501-507 uploads nothing), Conventional Commits enforcement (claimed at CONTRIBUTING.md:162-164 and PULL_REQUEST_TEMPLATE.md:3,:16, enforced nowhere), OpenSSF Scorecard + coverage.
• Wave-1 review deferrals: refactor(lint-cli): lint.rs output-matrix ResultSink redesign #309, refactor(scripts): extract gate-common.mjs, decompose verify-pr-checks + verify-no-control-bytes #310, refactor(core): centralize FFI option-key manifest (TS/napi/wasm/Python) #311, feat(typescript): exactOptionalPropertyTypes + export surface restructure #312, chore: trim-paths, CoC segregation, release.yml tidiness, test assertions #314 — all now carry the v0.5.0 milestone. docs: post-tag runbook, security roster, spec additions (v0.4.1 amendments) #313 carries v0.4.3 and is listed in the v0.4.3 section below.
• cargo clippy --workspace -- -D warnings fails under Rust 1.93 with 53 unused_assignments errors #322 — CLOSED; premise refuted: stable is 1.98.0, 1.93 is in the past; clippy exits 0 with zero unused_assignments on a cold build; the issue self-contradicted by citing the repo's own newer 1.96.0 wasm pin
• Fixed wall-clock waits on filesystem events share the watch-startup defect class #318 — real but factually drifted: cli_build.rs site count is 1, not several (cli_build.rs:1138-1148), and it is a bounded content-predicate poll rather than a sleep-then-assert anti-pattern — the residual defect is only that it doesn't use the MDS_TEST_READY handshake; HMR harness consumer count is 4 spec files (rollup/rspack/vite/webpack *-e2e.spec.mjs), not 8; note that most call sites override the 5000ms default anyway
• cli_watch harness: unjoined stderr drain thread and latent stdout deadlock in spawn_watch_ready #320 — real but factually drifted: line refs predate fix(watch): eliminate silent edit loss in mds watch startup and cross-root dependencies #323; tap moved to crates/mds-cli/tests/common/mod.rs; bytes() at :63-65 is still a non-blocking clone and the drain thread's JoinHandle is discarded at spawn (:93) so no caller can join it; real analogues of the old refs are cli_watch.rs:582-585 and :3463-3465; fix(watch): eliminate silent edit loss in mds watch startup and cross-root dependencies #323 widened exposure to 21 stderr_tap.bytes() call sites; readiness now travels over a temp file named by MDS_TEST_READY (common/mod.rs:136-165) — the hazard remains reachable because startup compile_and_write is at watch.rs:1158 and emit_ready_marker() at :1326

Stale-open resolved:

Issue	Status	Evidence
#199 — stale .map sidecar on --inline	landed in 85a4c05 (PR #183)	build.rs:1326-1347 "Stale sidecar reconciliation (AC-FUNC-10)" calling verify_then_delete_map; test sm13_inline_build_removes_stale_sidecar at cli_source_map.rs:556-583 asserting !map_path.exists()

Closed as duplicate — tracked by the survivor:

Closed	Survivor
#115	#114
#159	#136
#174	#235
#258	#157

#178 and #210 are likewise closed as duplicates; their analysis now lives in the surviving issues.

---

v0.4.1 — Release-Infrastructure Follow-ups ✅ (crates.io + npm 2026-09-03)

Shipped to crates.io and npm on 2026-09-03. The PyPI publish failed: pypa/gh-action-pypi-publish
was pinned to the SHA of an annotated tag object, which has no corresponding GHCR image, so the
publish step could not resolve its container. The GitHub Release was backfilled on 2026-09-04 with
--latest=false. v0.4.2 is the recovery release. The v0.4.1 milestone is closed and carries
no issues: every follow-up originally scoped to this section moved to v0.4.3 and is listed there.

---

v0.4.2 — First PyPI publication ✅ SHIPPED 2026-09-03

The recovery release for v0.4.1's failed PyPI step, and the first publication of markdown-script
to PyPI: 8 distributions (7 cp311-abi3 wheels + 1 sdist) with PEP 740 attestations via OIDC
trusted publishing. The v0.4.2 milestone is closed.

• Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132 — Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t)

---

v0.4.3 — Pipeline hardening + correctness batch 🚧

Milestone v0.4.3 is open with 23 issues (0 closed). Execution order is
housekeeping → pipeline hardening → correctness batch → release, one step per session.

Pipeline

• ci: publish-python job is unreachable from branch dry run (PF-039) #350 — ci: publish-python job is unreachable from branch dry run (PF-039)
• ci(release): release.yml's build matrix never runs on pull_request #342 — ci(release): release.yml's build matrix never runs on pull_request
• ci(release): validate CARGO_REGISTRY_TOKEN against crates.io in the version-gate probe (security-08 gap) #345 — ci(release): validate CARGO_REGISTRY_TOKEN against crates.io in the version-gate probe (security-08 gap)
• ci: latent shared-cache-key collisions in build-napi Linux legs and build-python macOS pair #352 — ci: latent shared-cache-key collisions in build-napi Linux legs and build-python macOS pair
• ci: upstream maturin-action bug — host-build-script purge checks debugBuildDir instead of releaseBuildDir #351 — ci: upstream maturin-action bug — host-build-script purge checks debugBuildDir instead of releaseBuildDir
• ci(release): move both musl zig wrappers to cargo-zigbuild's maintained linker-arg filter #339 — ci(release): move both musl zig wrappers to cargo-zigbuild's maintained linker-arg filter
• ci(release): load-test the linux-x64-musl addon on Alpine before upload #340 — ci(release): load-test the linux-x64-musl addon on Alpine before upload
• scripts(verify-pr-checks): key the skipped-publish allowance on the release.yml check suite, not the job name #341 — scripts(verify-pr-checks): key the skipped-publish allowance on the release.yml check suite, not the job name

Correctness

• --vars JSON file duplicate keys silently last-win (same class as #200, different mechanism) #326 — --vars JSON file duplicate keys silently last-win (same class as --set duplicate key silently last-wins — warn? #200, different mechanism)
• security: frontmatter YAML parse exposed to alias-bomb / deep-nest DoS (uncatchable at FFI) #162 — security: frontmatter YAML parse exposed to alias-bomb / deep-nest DoS (uncatchable at FFI)
• build::write_output still uses truncate-then-write (non-atomic) for compiled artifacts #227 — build::write_output still uses truncate-then-write (non-atomic) for compiled artifacts
• atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226 — atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group
• build: empty directory build exits 0 — silent success hazard in CI #204 — build: empty directory build exits 0 — silent success hazard in CI
• debug_assert!-only invariants silently degrade in release builds (3 sites) — PF-005 #220 — debug_assert!-only invariants silently degrade in release builds (3 sites) — PF-005
• output.rs path helpers fail-open on strip_prefix edge cases and non-UTF-8 paths #217 — output.rs path helpers fail-open on strip_prefix edge cases and non-UTF-8 paths
• Fixed wall-clock waits on filesystem events share the watch-startup defect class #318 — Fixed wall-clock waits on filesystem events share the watch-startup defect class
• cli_watch harness: unjoined stderr drain thread and latent stdout deadlock in spawn_watch_ready #320 — cli_watch harness: unjoined stderr drain thread and latent stdout deadlock in spawn_watch_ready
• test: flaky cli_watch.rs::watch_ctrl_c_prints_stopped_watching (timing) #129 — test: flaky cli_watch.rs::watch_ctrl_c_prints_stopped_watching (timing)

Docs

• chore(deps): relax the three dogfood-remediation devDep pins after soak (v0.4.1) #336 — chore(deps): relax the three dogfood-remediation devDep pins after soak (v0.4.1)
• spec §4.6 Imports "Rules:" omits symlink rejection — spec/implementation drift on a security control #327 — spec §4.6 Imports "Rules:" omits symlink rejection — spec/implementation drift on a security control
• docs: post-tag runbook, security roster, spec additions (v0.4.1 amendments) #313 — docs: post-tag runbook, security roster, spec additions (v0.4.1 amendments)
• Stale rustdoc in lib.rs: "empty in S1 — rules arrive in S2", and "9 lint rules" (there are 10) #329 — Stale rustdoc in lib.rs: "empty in S1 — rules arrive in S2", and "9 lint rules" (there are 10)
• Question: should spec §7.8 document fmt.sort_frontmatter_keys, a deliberately inert config field? #328 — Question: should spec §7.8 document fmt.sort_frontmatter_keys, a deliberately inert config field?

---

v0.5.0 — Advanced Features

Enable sharing and reuse across projects and teams.

• feat: URL-based imports (remote modules) #63 — URL-based imports (remote modules)
• feat: MDS package registry / prompt library ecosystem #64 — Package registry / prompt library ecosystem
• feat: MDS Runtime — on-read compilation via virtual filesystem #82 — MDS Runtime (on-read compilation via virtual filesystem)
• Public TS: rename FileOptions to CompileFileOptions for intent clarity (breaking — target v0.5.0) #222 — Public TS: rename FileOptions → CompileFileOptions (with deprecated alias)

The headline features are listed above. The v0.5.0 milestone (22 open / 3 closed) additionally
carries the tech debt and review deferrals catalogued under "Deferred past v0.4.0" — notably #182,
#222 and the Wave-1 deferrals #309–#312 and #314. (#292 was closed as satisfied by v0.4.2.)

---

v1.0.0 — Editor Experience (Deferred)

Full editor integration. Intentionally last — language features and production readiness come before distribution overhead. These items require significant DevOps, testing, and maintenance investment beyond the code itself.

• feat: VS Code extension (TextMate injection grammar) #65 — VS Code extension (TextMate injection grammar)
• feat: Tree-sitter grammar (Neovim, Helix, Zed) #66 — Tree-sitter grammar (Neovim, Helix, Zed)
• feat: LSP server for MDS #67 — LSP server

---

Completed Milestones

v0.4.0 (2026-09-02) ✅

• Python bindings (PyO3), mds fmt, mds lint, source maps for compiled output
• Breaking: {x} → {{x}} double-brace interpolation, with a lint --fix migration path
• Terminal-escape hardening across all MdsError variants (CWE-150); LintDiagnostic made #[non_exhaustive]
• Two dogfood remediation waves plus the mds watch correctness fixes (mds watch silently loses edits made during startup #317, mds watch idle-tick self-heal never fires when irrelevant filesystem events stream continuously #319, mds watch directory mode has no content-level backstop for cross-root dependencies #321)
• Release-safety gates: control-byte/bidi source scan, pre-merge check verifier, musl linkage assertion
• Published to crates.io, npm (with SLSA provenance), and GitHub Releases

v0.3.0 (2026-06-28) ✅

• mds watch, template inheritance (@extends / @block), HMR across all four bundler plugins
• Intrinsic output format (breaking): template content decides Markdown vs JSON message array
• Full 11-item tech-debt sweep

v0.2.0 (2026-06-06) ✅

• 18 built-in functions, default args, logical operators
• Expression support in @for and @if directives
• Frontmatter imports
• wasm-opt re-enabled (Binaryen v129, -Oz)
• Published to crates.io, npm (with SLSA provenance), and GitHub Releases

v0.1.0 (2026-05-31) ✅

• Core compiler (lexer, parser, resolver, validator, evaluator)
• CLI: build, check, init
• JS/TS ecosystem: WASM bindings, napi-rs, universal package, Vite/Rollup/Webpack plugins
• Automated release pipeline (workflow dispatch)
• 591+ tests, full CI/CD
• Published to crates.io, npm, and GitHub Releases

Notes

• Editor experience (v1.0.0) is intentionally deferred. Language enrichment and production readiness take priority — we want to ship features users can use before investing in distribution and tooling overhead.
• The v0.4.0 pre-tag set was deliberately biased toward things that become expensive after the tag: wire formats, exported type names, and deprecation windows. Pure-quality tech debt was listed but never treated as a blocker.
• Release path is tag-push, and it is the path v0.4.0 shipped on: node scripts/bump-version.mjs X.Y.Z → land on main via CI-gated PR → git tag -a vX.Y.Z && git push origin vX.Y.Z. The workflow_dispatch -f version= path was deleted in chore: harden release machinery (5 independent fixes) #287; bare gh workflow run release.yml is now the dry-run. A staged run that fails mid-publish is recovered with gh run rerun --failed, never by re-tagging.

[dean0x]

v0.2.0 Released — 2026-06-06

All language enrichment features shipped:

• mds-core + mds-cli → crates.io
• 8 npm packages → npmjs.com (with SLSA provenance)
• GitHub Release v0.2.0

Features: 18 built-in functions, default args, logical operators, expression directives, frontmatter imports, wasm-opt re-enabled.

Remaining on milestone: #38 (CODE_OF_CONDUCT.md), #71 and #72 (tech debt — moving to v0.3.0).

[dean0x]

Progress Update: v0.4.0 Fix Batch

PR #161 (fix!: v0.4.0 bug batch — fences, whitespace, type safety, @extends FM) was squash-merged to main at commit 3ce9f1d on 2026-07-09.

Closed: #149, #150, #151, #152, #153, #154 — all marked COMPLETED.

Status: Fix batch is on main under [Unreleased] at version 0.3.0 with no version bump yet. v0.4.0 bump is a deliberate, separate post-merge step gated on full milestone closure.

Deferred follow-ups remain open: #162 (YAML parse DoS), #163 (SHA-pin Actions), #164 (parity gaps).

[dean0x]

Roadmap update — v0.4.0 code complete

The v0.4.0 section was last accurate at main = 113f472. Two PRs landed since then, and v0.4.0 is now code-complete.

PR #308 (339df37) — Wave 1 pre-tag set: closed 12 planned issues (#38, #180, #202, #203, #209, #211, #213, #215, #216, #224, #288, #289) plus three unplanned issues forced during the wave (#300, #306, #307). The Closes discipline held on all 15 — no repeat of the #117 stale-open failure.

PR #323 (b34d8ac) — Watch correctness: closed #317, #319, #321 and added the watch-startup-race CI job. All 3 auto-closed.

Milestone v0.4.0 is now empty: 0 open / 18 closed.

---

Corrections this update carries

Wave 1 scope: 13 pre-tag issues were listed; 12 closed in PR #308. The 13th (#292) is half-done (rename landed, PyPI registration remains) and does not block the tag — moved to the "Not blocking" section.

#199 — genuine stale-open found: build: stale .map sidecar on --inline was fixed in 85a4c05 (PR #183) and never closed. That is the one failure of the Closes discipline. Closing now.

Partially-done issues overstating what remains:

• ci(wasm): pin wasm build toolchain for deterministic size; re-tighten size budget #128: toolchain pinned; WASM budget guard NOT re-tightened (still -gt 850000)
• ci: SHA-pin GitHub Actions + assert lockfile version in verify-versions.mjs #163: 10 of 58 uses: pinned (not 2 of 53 — count grew with new PRs); 48 float
• Release hygiene: fix config drift and close gold-standard gaps #182: 2 of 6 items done, both predating v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308

#129 NOT fixed by #323: test survives at cli_watch.rs:1108, 100ms sleep at :1151 unchanged.

#322 premise refuted: the issue predicted a break "when stable reaches 1.93" but 1.93 is already in the past — current stable is 1.98.0. Clippy exits 0 with zero unused_assignments on a cold build. Closing.

#318 and #320 factually drifted: cli_build.rs site count is 1 (not several); HMR harness consumer count is 4 spec files (not 8); line refs in #320 predate #323. Both remain open but their bodies need correction.

Six wave-1 review issues (#309–#314) carry target milestones in their bodies but have no milestone or labels set.

---

Before tagging

1. Fix CHANGELOG LintConfig::from_rules entry (CHANGELOG.md:1074-1082) — documents a deprecated function that was actually removed in 339df37; move from ### Deprecated to ### Removed, drop migration text.
2. Clean the working tree (uncommitted .gitignore edit +!.devflow/conventions.md).
3. node scripts/bump-version.mjs 0.4.0 → land on main via CI-gated PR → node scripts/verify-pr-checks.mjs <pr> (PF-017) → merge with exact printed command.
4. git tag -a v0.4.0 -m v0.4.0 && git push origin v0.4.0

[dean0x]

Three contradictory entries have been corrected and a checkbox convention has been added at the top of the document.

Root cause. Issues #226 and #182 were listed twice each: once under "Fix / hardening waves — landed ✅" (with a checked box), and once under "Deferred past v0.4.0" (correctly noting open work). The two entries disagreed on state.

What each PR actually did:

• atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226 / PR doc: add note about atomic_write_file not preserving hard links, ACLs, xattrs, owner/group #239 — landed the atomic_write_file limitation note in output.rs and RELEASING.md. The implementation half (preserving ACLs, xattrs, owner/group) never landed. Issue atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226 remains open.
• Release hygiene: fix config drift and close gold-standard gaps #182 / PR chore(docs): remove dead Discussions link and stale version table (#182) #291 — removed a dead Discussions link and a stale supported-versions table that Release hygiene: fix config drift and close gold-standard gaps #182's own body had already marked "Config drift — RESOLVED, no longer in scope." None of the six gold-standard gaps in Release hygiene: fix config drift and close gold-standard gaps #182's acceptance criteria were touched. Issue Release hygiene: fix config drift and close gold-standard gaps #182 remains open.

Edit 4 (inverse case): #38 (Add CODE_OF_CONDUCT.md) was unchecked under v0.2.0 despite being closed — it landed in Wave 1 (PR #308). That box is now checked.

Standing rule added. A blockquote near the top of the document now states: a checked box means the referenced issue is closed; partial progress uses a prose bullet with no checkbox, naming what landed and what remains. This is the convention that the (partial) / (doc half) qualifiers should have enforced but did not, because readers scan checkboxes and section headings before qualifier text.

Full scan: all 76 issue refs appearing in checked bullets were verified against gh issue list --state all --limit 400. Zero other contradictions found.

[dean0x]

v0.4.0 shipped 2026-09-02: tag v0.4.0 at 6673dc3, release run https://github.com/dean0x/mdscript/actions/runs/33569514359 (attempt 2 after a crates.io token rotation), GitHub Release https://github.com/dean0x/mdscript/releases/tag/v0.4.0. Published: mds-core and mds-cli 0.4.0 on crates.io; the 8 @MDscript npm packages and 7 native platform packages at 0.4.0 with provenance. Release-prep fixes landed in #338 (aarch64-musl link flag, linux-x64-musl now genuinely musl-linked with a readelf gate, setup-zig pin, verifier allowance) and #344 (CI-history gate reads the CI run instead of branch protection). Follow-ups: #339, #340, #341, #342, #345 (v0.4.1). PyPI publishing remains deferred (#132/#292).

[dean0x]

v0.4.1 and v0.4.2 — Release Summary

v0.4.1 (tag 83bc57d, 2026-09-03): shipped to crates.io (mds-core 0.4.1, mds-cli 0.4.1) and npm (all 15 @mdscript/* packages at 0.4.1). PyPI publication failed — the pypa/gh-action-pypi-publish action was pinned to an annotated-tag-object SHA for which no GHCR container image exists (manifest unknown). No GitHub Release was created for v0.4.1.

v0.4.2 (tag d15fa46, 2026-09-03, run 33787292742): fully shipped.

• crates.io: mds-core 0.4.2, mds-cli 0.4.2
• npm: all 15 @mdscript/* packages at 0.4.2, with SLSA provenance attestations
• PyPI: markdown-script 0.4.2 — the first-ever PyPI publication for this project. 8 distributions (cp311-abi3 wheels for macOS x86_64/arm64, manylinux x86_64/aarch64, musllinux x86_64/aarch64, and source + Windows x86_64) with PEP 740 attestations.
• GitHub Release: https://github.com/dean0x/mdscript/releases/tag/v0.4.2 (marked Latest)

Note: pip install markdown-script requires Python 3.11+ (cp311-abi3 wheel ABI).

Issue #132 (Python bindings: cross-platform wheel matrix + PyPI publishing) is closed and complete. It is now on the v0.4.2 milestone.

Milestone State

Milestone	State	Notes
v0.4.1	closed	crates.io + npm only; PyPI failed; no GitHub Release
v0.4.2	closed	Full release including first PyPI publication (#132)
v0.4.3	open	11 carry-over follow-ups + 3 new issues: #350, #351, #352

The three new v0.4.3 issues address: the publish-python dry-run gap (PF-039, #350), an upstream bug in PyO3/maturin-action's host-build-script purge logic (#351), and latent shared-cache-key collisions in build-napi and build-python macOS CI legs (#352).

[dean0x]

Roadmap re-scope (2026-09-05)

• v0.4.1 and v0.4.2 are shipped; v0.4.2 (2026-09-03) was the first PyPI publication of markdown-script and closed Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132. The body above now reflects both.
• v0.4.3 re-scoped from 14 to 23 issues. The correctness batch (security: frontmatter YAML parse exposed to alias-bomb / deep-nest DoS (uncatchable at FFI) #162, build::write_output still uses truncate-then-write (non-atomic) for compiled artifacts #227, atomic_write_file: rename-based write does not preserve platform ACLs, xattrs, or owner/group #226, build: empty directory build exits 0 — silent success hazard in CI #204, debug_assert!-only invariants silently degrade in release builds (3 sites) — PF-005 #220, output.rs path helpers fail-open on strip_prefix edge cases and non-UTF-8 paths #217, Fixed wall-clock waits on filesystem events share the watch-startup defect class #318, cli_watch harness: unjoined stderr drain thread and latent stdout deadlock in spawn_watch_ready #320, test: flaky cli_watch.rs::watch_ctrl_c_prints_stopped_watching (timing) #129) joins the pipeline items (ci: publish-python job is unreachable from branch dry run (PF-039) #350, ci(release): release.yml's build matrix never runs on pull_request #342, ci(release): validate CARGO_REGISTRY_TOKEN against crates.io in the version-gate probe (security-08 gap) #345, ci: latent shared-cache-key collisions in build-napi Linux legs and build-python macOS pair #352, ci: upstream maturin-action bug — host-build-script purge checks debugBuildDir instead of releaseBuildDir #351, ci(release): move both musl zig wrappers to cargo-zigbuild's maintained linker-arg filter #339, ci(release): load-test the linux-x64-musl addon on Alpine before upload #340, scripts(verify-pr-checks): key the skipped-publish allowance on the release.yml check suite, not the job name #341), --vars JSON file duplicate keys silently last-win (same class as #200, different mechanism) #326, and the docs items (chore(deps): relax the three dogfood-remediation devDep pins after soak (v0.4.1) #336, spec §4.6 Imports "Rules:" omits symlink rejection — spec/implementation drift on a security control #327, docs: post-tag runbook, security roster, spec additions (v0.4.1 amendments) #313, Stale rustdoc in lib.rs: "empty in S1 — rules arrive in S2", and "9 lint rules" (there are 10) #329, Question: should spec §7.8 document fmt.sort_frontmatter_keys, a deliberately inert config field? #328).
• Housekeeping today: v0.5.0 removal tracker: delete mds::fix::apply_fixes and migrate ADR-004 coverage #304 moved to v0.5.0 (removal counterpart of the shipped Deprecate apply_fixes from public mds-core API and schedule removal — 0 callers since apply_fixes_incremental shipped #209 deprecation); Rename Python distribution to markdown-script (import markdown_script) + register on PyPI #292 closed (PyPI live); chore(deps): bump fast-uri from 3.1.4 to 3.1.5 in the npm_and_yarn group across 1 directory #254 closed (superseded by chore(deps-dev): bump fast-uri from 3.1.5 to 3.1.6 in /packages/webpack-loader in the npm_and_yarn group across 1 directory #346); Dependabot config gains a 30-day cooldown and a napi group.
• Execution order: housekeeping (Dependabot config → dependency sweep → GitHub Actions majors) → pipeline hardening (ci(release): release.yml's build matrix never runs on pull_request #342/ci: publish-python job is unreachable from branch dry run (PF-039) #350, then ci(release): validate CARGO_REGISTRY_TOKEN against crates.io in the version-gate probe (security-08 gap) #345/ci: latent shared-cache-key collisions in build-napi Linux legs and build-python macOS pair #352/scripts(verify-pr-checks): key the skipped-publish allowance on the release.yml check suite, not the job name #341, then ci(release): move both musl zig wrappers to cargo-zigbuild's maintained linker-arg filter #339/ci(release): load-test the linux-x64-musl addon on Alpine before upload #340) → correctness batch → docs decisions → cut v0.4.3. One step per session; this issue gets an update at each phase boundary.

[dean0x]

Phase A (housekeeping) complete.

• A1: PR chore(deps): add 30-day Dependabot cooldown and napi group #353 → 294b5a5 (Dependabot 30-day cooldown + napi group).
• A2: PR chore(deps): cargo dependency sweep (napi 3.12.2, pyo3 0.29.2, clap 4.6.6, wasm-bindgen 0.2.126, +5) #361 → aa00266 (cargo sweep); PR chore(deps): npm dependency sweep — relax phantom floor pins, @napi-rs/cli 3.8.6, vite 8.2.2 #363 → 5570e35 (npm sweep; closed chore(deps): relax the three dogfood-remediation devDep pins after soak (v0.4.1) #336). 16 Dependabot PRs closed. WASM 839,456 B measured, 850K guard unchanged.
• A3: PR chore(ci): bump checkout v7, setup-node v7, setup-python v7; normalize maturin-action pin (PF-040) #365 → 33e4adc (27 first-party action sites to v7: checkout, setup-node, setup-python; PyO3/maturin-action pin normalized to its commit, PF-040; release.yml dry-run 34047806587 green). chore(ci): bump actions/checkout from 6 to 7 #111 chore(ci): bump actions/setup-node from 6 to 7 #189 chore(ci): bump actions/setup-python from 5 to 7 #241 chore(ci): bump PyO3/maturin-action from 3e2bdf6ba6453a61e649744019b8a2d906c7eb38 to e83996d129638aa358a18fbd1dfb82f0b0fb5d3b #356 closed. chore(deps): bump typescript from 6.0.3 to 7.0.2 #169 → issue TypeScript 7 migration: the CJS dual build uses moduleResolution=node10, removed in TS 7 #364 (v0.5.0) + Dependabot typescript semver-major ignore.

Queue: 4 Dependabot PRs (#334 #333 #316 #284), cooldown-eligible 2026-09-09..13. Next: B1 (#342 + #350).