Changelog - 2026-10-17

VULCAN 0.2.0-3: one bad file never takes a check down

Type: Bug Fix, Enhancement

In one line. BANA's gate found two places where one bad file stopped everything; both now report the file and carry on.

doctor reports a skill it cannot read. A SKILL.md whose frontmatter is not valid YAML (for example argument-hint: [a] [b]) is a finding with its line, SKILL.md: the frontmatter is not valid YAML at line 4, instead of a crash. The other checks still run.
One broken export never empties atlas's symbols. An export whose .d.ts is missing, or cannot be read as a module, is skipped with one warning naming the package, subpath and path. Every other export still answers symbol.
changes says what it needs. With no changelog directory, or none with dated entries, it names the layout: YYYY-MM-DD-<slug>.md files with packages: [<npm name>, ...] frontmatter.
Fence warnings point at the line. atlas names the document and the line an unclosed code fence opened on, and reads fences the CommonMark way (a 4-backtick block may hold a 3-backtick one).
search takes a source. Ask one source among several; an unknown name lists the known ones.
An unknown symbol answers. symbol returns matches: [] with the closest known names instead of an error.
sync takes back a dead shipped skill link after a downgrade or a retired skill; doctor flags one.
skill-evals --max-budget-usd caps every model call (a VULCAN-repo tool).

A client that branched on symbol's "unknown symbol" error. It now gets a result with matches: [] and closest.
Everyone else. No action needed: upgrade, then vulcan sync.