Skip to content

WolfMarkDown v1.0.2

Choose a tag to compare

View all tags
@WolfMarkTools WolfMarkTools released this 10 Oct 12:24
v1.0.2
0ae1af9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Overview

WolfMarkDown v1.0.2 focuses on correctness, safety, reliability, and stronger verification. Integrity comparison now understands what it protects, publishing is safe when multiple agents operate concurrently, and every operation leaves structured evidence behind.

Highlights

  • Stronger preservation of technical content: code spans, URLs, currency, paths, environment assignments, and image descriptions fail verification when changed or removed, while ordinary prose edits raise review warnings instead of failures.
  • Improved detection of altered values and identifiers, including same-class value swaps, occurrence shifts, and accurate occurrence counts in receipts.
  • More reliable publishing when multiple agents operate concurrently: per-destination locks, stale-lock recovery, conflict refusal instead of silent overwrites, and temporary candidates published only after verification passes.
  • Accurate verification receipts and clearer error reporting: truthful hashes, stage-specific read errors, per-file error receipts, skipped-path reporting, and failure evidence for batches with no eligible files.
  • Improved skill installation and diagnostics: Node.js pre-checks, classified npm failure messages, link-only setup, and a Doctor exit code that follows runtime health with --strict audits.

Compatibility

  • Node.js 22 or newer is required.
  • Existing installations should update dependencies (npm ci --prefix wolfmarkdown) and re-run setup.
  • Doctor's exit code is now 0 when the runtime is healthy, even if discovery links are missing; use node wolfmarkdown/scripts/doctor.mjs --strict for a full installation audit.
  • node wolfmarkdown/scripts/install.mjs --skip-deps manages discovery links without running npm ci.

Installation and updating

Agent Skills CLI (recommended):

npx skills add WolfMarkTools/WolfMarkDown --skill wolfmarkdown

Update an existing Skills CLI installation:

npx skills update wolfmarkdown

Repository checkout:

git clone https://github.com/WolfMarkTools/WolfMarkDown.git
cd WolfMarkDown
npm ci --prefix wolfmarkdown
node wolfmarkdown/scripts/install.mjs

Update a checkout with git pull, then repeat npm ci --prefix wolfmarkdown and node wolfmarkdown/scripts/install.mjs.

Verification

  • 204 automated tests pass on Node.js 22 and 24.
  • Agent-skill metadata validation passes.
  • The public Mobile App Migration example verifies PASS against its source snapshot.

Known limitations

  • Integrity checks cover recognised token classes only: some values (two-part versions, month-name dates, isolated integers) are outside the extractor and reported as coverage warnings.
  • A PASS is Markdown-quality evidence — well-formed, verified output — not factual correctness, completeness, policy compliance, or authorisation to publish.
  • npm audit reports one low-severity KaTeX advisory chain via markdownlint; WolfMarkDown never renders math to HTML, so the documented rendering conditions do not apply. Tracked upstream rather than forcing a breaking downgrade.

Changelog

Assets 2
Loading