[MartinForReal]

Cuts 0.6.0. Minor rather than patch: the settings tab is a different shape, and Warn about missing fields adds a stored field with a migration.

What's in it

• The settings tab asks 18 questions instead of 29 (Consolidate the settings tab: 29 rows to 18, and three dead fields #17, PR Ask 18 settings questions instead of 29 #18) — five merges, two of which fixed real defects: Live check on save / open never gated "open", and Generate index.md on startup did nothing with auto-generation off.
• Index gaps can be reported instead of written ([Feature] Flag index gaps instead of generating them, for hand-authored vaults #15, PR Report index gaps instead of writing them (#15) #16) — plus the report pane grouping findings by folder and listing the open note's own.
• Release assets survive a pre-existing release (PR Don't lose the release assets when the release already exists #19).

Version bump

npm version minor --no-git-tag-version → package.json, manifest.json, versions.json (0.6.0 → minAppVersion 1.7.2), package-lock.json. main.js rebuilt and committed.

The default Actor for generated.by becomes okf-enforcer/0.6, tracking the minor line as it has since 0.3.0. Only new vaults see it — a saved defaultActor is kept as written. Verified in the built artifact: 4 occurrences of okf-enforcer/0.6, 0 of okf-enforcer/0.5.

Changelog tidy

The unreleased section had grown two ### Changed headings — one from the report-pane work, one from the settings consolidation, each correct on its own branch and duplicated once both landed. Folded into one section, with the categories in Keep a Changelog's order (Added, Changed, Removed, Internal).

Done by splicing line ranges rather than retyping, and checked by line multiset: the only content lines that left the file are the ## [Unreleased] heading (renamed to ## [0.6.0] - 2026-08-05) and the duplicate ### Changed. Nothing else moved out.

Verification

• npx tsc --noEmit --skipLibCheck clean.
• npm run build clean; main.js committed alongside the sources.
• manifest.json, package.json both read 0.6.0; versions.json gained "0.6.0": "1.7.2".

Once merged, tagging the merge commit 0.6.0 triggers the release workflow.

🤖 Generated with Claude Code