chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@zettelgeist/cli@0.4.1

Patch Changes

• #15 8853133 Thanks @morrieinmaas! - Pre-commit hook now self-disables in repos that aren't zettelgeist repos. Previously, a stale install left over from a removed config (or a partial init) would block every commit with error: not a zettelgeist repo. The installed hook block now exits 0 silently when .zettelgeist.yaml is missing. Re-run zettelgeist install-hook (or zettelgeist init) to update existing hooks.

@zettelgeist/core@0.4.1

Patch Changes

• #15 8853133 Thanks @morrieinmaas! - deriveStatus now ignores a status: draft frontmatter override when the spec has at least one counted task and every counted task is checked. The override is provably stale in that case (the board's "+" button writes it on new-card creation and nothing clears it afterwards). The card transparently moves to in-review (or done if merged) on the next render — no file mutation, no user action. Other override values (planned, in-progress, in-review, done, blocked, cancelled) and draft overrides with partial or zero progress are unchanged.

@zettelgeist/mcp-server@0.3.1

Patch Changes

• #15 8853133 Thanks @morrieinmaas! - tick_task now clears a stale status: draft frontmatter override on requirements.md as part of the same commit. This unblocks specs created from the board's "+" column button (which pins status: draft) from staying stuck in the draft column after every task is ticked. Other override values (blocked, cancelled, planned, in-progress, in-review, done) are left untouched — they may reflect explicit user intent. untick_task does not clear the override, so the draft column reset use-case still works.