A vault with no bundle is left alone. With nothing configured, a root index.md carrying a LOKF header makes the whole vault the bundle and a top-level knowledge_bundle/ makes that the bundle, as before; a vault with neither now has no bundle - nothing scanned, no root-header warning, status bar LOKF: no bundle, commands explain instead of acting - rather than being read as one whole-vault bundle. The workshop is never mistaken for the exhibition.
Insert the bundle’s semantic header (was Insert semantic header template into root index.md): in a vault with no bundle it now creates knowledge_bundle/ and puts the header in its index.md instead of decorating the vault root.
README trimmed: the For the curious section is now docs/for-the-curious.md.
Added
Treat the vault root as the bundle (Scope, off by default): the break-glass switch that restores the old whole-vault reading for a vault whose root index.md carries no LOKF header.
Fixed
npm run lint and tsc failed on scripts/smoke-test.ts’s js-yaml import and on .github/scripts/changelog-release.mjs (outside ESLint’s project); both now pass.
