VULCAN

Appearance

Changelog - 2026-10-17 ​

VULCAN 0.2.0-1: the minors from the 0.2.0-0 review ​

Type: Bug Fix, Enhancement

In one line. Every minor finding of the 0.2.0-0 final review is fixed: errors say what is wrong and where, generated files settle in one run, and atlas sources recover on their own.

What changed ​

  • Contents anchors match GitHub. _ is kept, repeated headings get -1, -2, a link heading uses its text. Run vulcan x okf gen once: long files with such headings get new anchors.
  • okf reports instead of aborting. A broken region names its file and says "malformed", one bad changelog or one empty coverage axis is a problem in the list, and an invalid VULCAN_CONFIG gets a plain message. A gen that changes nothing says gen: up to date.
  • sync --prune removes only VULCAN's own old commands, the exact forms earlier releases shipped. A hook you customised stays. A hand-edited shipped hook no longer leaves two guards after an upgrade.
  • The fail-closed hook says what is missing: node_modules/@venizia/vulcan, or bun on PATH. Its bun install escape allows bare flags only.
  • The release tag sits on the commit it published, and a retry skips a tag that is already there.
  • atlas sources recover. A failed npm symbol fetch is retried in the background, a release tag pushed later is seen, a broken cache directory is cloned again, and the offline fallback keeps to the ref you asked for. version finds packages installed under another package.
  • Smaller fixes. vulcan x --help, would create under --dry-run, D9 for packages outside packages/, a symlinked .claude/skills is never written through, validated package names, CRLF frontmatter, and truthful no-history messages.

Who is affected ​

  • Projects with long knowledge files. Run vulcan x okf gen after upgrading, then commit the new anchors.
  • Everyone else. No action needed: bun x --no-install vulcan upgrade, then vulcan sync.