WolfMarkDown v1.0.0

[WolfMarkTools]

Introducing WolfMarkDown v1.0.0

WolfMarkDown v1.0.0 is the publishing workflow for agent Markdown, not a patch on v0.2.2.

The agent still decides structure. Deterministic tooling still proves the file is safe to keep. What v1.0.0 adds is written evidence: a receipt, a source-to-candidate preview, integrity coverage, and publish paths that restore or refuse instead of leaving a half-written .md.

A PASS is Markdown-quality evidence. It is not factual correctness, completeness, or approval to publish.

Highlights

• Receipts. Verify records hashes, tool versions, checks, structured issues, remediations, and the quality boundary. A PASS is durable evidence, not only an exit code.
• Preview before keep. Source-to-candidate preview inventories observable structure, recognised protected tokens, and whether the candidate is formatting-only or content-changed.
• Honest integrity. Coverage warnings name shapes the extractor does not protect, including two-part versions such as 18.17, month-name dates such as May 2027, and isolated integers.
• Batch Verify. Directories, multiple files, and standard input are supported.
• Long-document scaffold. The agent gets an inventory of headings, fences, lists, tables, and recognised tokens before it decides structure. Scaffold does not rewrite the document.
• Safer writes. Format and publish use atomic replace, refuse symlink destinations, and will not overwrite a file that changed during verification. Failed Clean restores the original. Failed Compose does not publish.

Compose, Clean, Verify, Doctor, and Setup remain the public operations.

Install and update

Requires Node.js 20 or newer.

npx skills add WolfMarkTools/WolfMarkDown --skill wolfmarkdown

npx skills update wolfmarkdown

Reload the host after install or update. A repository checkout still updates with git pull, npm ci --prefix wolfmarkdown, and node wolfmarkdown/scripts/install.mjs.

Behaviour to know

• Clean and Compose now keep preview and receipt evidence as part of keep-or-publish. Bare Verify remains available for check-only use.
• The skill activates for Markdown, .md, export/save, or WolfMarkDown itself. Generic “clean up this research” or “format this documentation” does not start Clean or Compose.
• Standalone Verify without --integrity-from does not prove protected tokens were preserved.
• CI runs the test suite, skill validation, and the public example on Node 20, 22, and 24.

What's Changed

Compared with v0.2.2, v1.0.0 is better where it used to stop at “the command exited zero”:

• v0.2.2 proved a file and moved on. v1.0.0 writes a receipt you can keep: hashes, versions, checks, issues, remediations, and the quality boundary.
• v0.2.2 integrity could pass while leaving unprotected shapes silent. v1.0.0 warns when two-part versions, month-name dates, or isolated integers were never in the extractor.
• v0.2.2 Verify was one file at a time. v1.0.0 verifies directories, multiple files, and standard input, with a source-to-candidate preview before you keep the result.
• v0.2.2 left long-document structure to the agent’s memory. v1.0.0 adds a scaffold inventory so headings, fences, lists, and tables are mapped before repair.
• v0.2.2 publish was less strict about collisions and in-flight edits. v1.0.0 uses atomic replace, refuses symlink destinations, will not clobber a file that changed during verification, restores on failed Clean, and does not publish failed Compose.
• v0.2.2 README assumed you already knew how to install. v1.0.0 makes install and update obvious for both the skills CLI and a checkout.
• v0.2.2 could activate on generic research or docs cleanup. v1.0.0 starts Clean or Compose only when the request is Markdown, a .md file, export/save, or WolfMarkDown itself.

Ship WolfMarkDown v1.0.0: #11

Full Changelog: v0.2.2...v1.0.0

---

This discussion was created from the release WolfMarkDown v1.0.0.