v0.35.1

Patch Changes

• Internal refactor (no user-facing change): the native application menu now
  renders its actionable command leaves from the same shared command registry the
  Cmd+K palette uses, so each command's identity — label, accelerator, keyboard
  shortcut, availability, and menu placement — is declared once in
  @inkeep/open-knowledge-core instead of being hand-maintained in two lists.
  Command availability is a pure, declarative evaluator both surfaces call; the
  menu's structural scaffolding (roles, separators, submenus, the dynamic
  Recent-project list, and the platform branches) stays declarative. The
  "Check for updates" and "Settings" platform placements are now data-driven,
  and a ratchet fails the build if a command is ever hand-placed twice in the same
  platform's menu bar. Menu items, order, labels, accelerators, and enabled/checked
  states are unchanged on every platform.

• When OpenKnowledge invites you to report a crash it just detected, and a crash dump for that crash is on disk, the dump is now included in the report by default. The crash dump is a memory snapshot from the moment of the crash, and the single most useful artifact for finding the cause, so it now rides along unless you uncheck it. Previously it was off by default, so crash reports usually arrived without the very dump that triggered them.

  The crash-dump option now appears only when a dump actually exists for the crash, so a crash invite with nothing to include (for example a session that ended without a clean quit but left no native dump) no longer shows a dead checkbox.

  Nothing about the consent flow changes: the crash dump is still a labeled checkbox you can turn off, the note still says it can contain document content and can't be redacted, and nothing is sent until you review the exact bundle. This only affects reports triggered by a detected crash; regular bug reports are unchanged and never include a crash dump.

• The desktop app no longer invites you to file a bug report after your machine reboots (kernel panic, forced restart, or power loss) while OpenKnowledge was running. It now recognizes when the previous session ended because the machine went down — not because the app crashed — and skips the prompt in that case, logging the event instead. Genuine app crashes still prompt exactly as before, and a crash that produced a crash dump still prompts, even across a reboot.