Skip to content

Changelog - 2026-10-18 ​

VULCAN 0.2.0-7: atlas help and tools, a doctor that checks the scaffold, init for workspaces ​

Type: Enhancement, Bug Fix

In one line. Six defects a clean-directory dry run of a new IGNIS + ARDOR + VULCAN monorepo found on 0.2.0-6.

What changed ​

  • atlas prints its usage. vulcan x atlas --help, -h and help print the usage on stdout and exit 0. They used to fall through to the MCP server, which waited on stdin and exited 0 in silence.
  • vulcan x atlas tools lists the tools. It prints the five tools, one line each, without an MCP client, and exits 2 with nothing to serve outside a project.
  • init skips root lint configs in a workspaces project. When package.json declares workspaces, init writes no root .configs/{oxlint,eslint,oxfmt} and says skipped: each app keeps its own. A single-package project gets the same three files as before.
  • The .mcp.json hint fits every project. It no longer waits for docs/wiki/content: atlas serves a knowledge bundle alone. The hint and the guides pass --root ..
  • doctor has a scaffold check. A workspaces project whose config lists no packages fails (the legacy atlas.packages map counts), and so does a knowledge index that still holds the vulcan:scaffold line init writes. Delete that line once the index describes the project.
  • A built-in renderer links only a concept that exists. The "see also" line of makefile-targets, source-map and binding-keys appears once its concept exists (process/build-system.md, overview/monorepo-layout.md, conventions/binding-key-namespaces.md), so a new project passes okf check --strict. Where the concept exists the page is unchanged. okf gen with nothing configured now names okf.renderers and the built-in renderers.
  • The adopting guide covers a fresh clone. Run install as its own CI step (make parses the -include of vulcan.mk before install creates it), and run vulcan sync before vulcan doctor (the adapters are gitignored).

Who is affected ​

  • A project that ran init on 0.2.0-6 or earlier. Its index has no marker, so doctor is unchanged for a single-package project. A workspaces project with no packages in its config now fails [scaffold]: list them in release order.
  • A project that ran init on 0.2.0-7. doctor fails [scaffold] until the index loses its marker line.
  • Everyone else. No action needed: upgrade, then vulcan sync.