Repository navigation
Conversation
On the board grouped by field:status, a task note with `status: done` vanished, even with `done` listed in kanban_statuses. The field board skipped every checked, cancelled or forwarded task before it read the field, and a task note's checked state comes from that same `status:`: the value that names its column was the value that took it off the board. The desktop app had the same filter (ZenNotes/zennotes#949). A task note whose value is one of the configured columns now stays in that column. Only configured values count: a discovered column would turn every finished task note in the vault into a column of its own. A configured `cancelled` column holds cancelled task notes the same way. Checkbox tasks keep the rule, since a status they inherit from the note's frontmatter would pull every checked subtask of an in-progress note into In progress. One test, which fails without the change.
DefaultInstructions is meant to be a verbatim copy of the desktop MCP server's instructions, so an agent behaves the same whichever binary serves the vault. It had drifted three times: it lacked the rule that Mermaid labels are plain text, the collapsible callout syntax, and the whole section on reviewing a note through comment threads, although zn mcp has had list_comments, add_comment, reply_to_comment and resolve_comment since e5550a3. Desktop 2.71.0 also adds D2 to the renderers an agent should use. The constant is regenerated from the desktop text at ZenNotes/zennotes c4a38631, one quoted line per source line as before (the same generator reproduces the old constant exactly), and zn mcp's initialize now returns that text unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The zn half of ZenNotes 2.71.0, released as v0.8.1.
field:status, a task note withstatus: donenow stays in a configureddonecolumn instead of vanishing, mirroring [Bug] Custom status Kanban hides completed task notes from the configured Done column zennotes#949 (desktop ab15a36d). Onlykanban_statusescolumns hold finished notes; checked checkbox tasks still leave the board.zn mcpgives assistants the desktop's instructions again (241abbc):DefaultInstructionsis regenerated from the desktop MCP instructions at ZenNotes/zennotes c4a38631 (D2, the Mermaid label rule, collapsible callouts, the comments section). Theinitializeresponse is byte-identical to the desktop's text (14,089 characters).Tests:
go vet ./...andgo test ./...pass locally; the new board test fails without its fix. All six GOOS/GOARCH targets build,goreleaser checkand a snapshot release pass, and the Homebrew updater tests pass. Inzn tuion a scratch vault, v0.8.0'sdonecolumn is empty while this branch shows thestatus: donenote in it.