Skip to content

v0.16.0 scope (release)

This document is the v0.16.0 release scope for Strixonomy (VS Code extension) and Strixonomy (Rust engine).

Source of truth for “what’s available today” remains SHIPPED.md. This file defines what we intend to ship in v0.16.0.

Theme

Close the remaining “desktop shell” parity gaps: preferences, layout persistence, and a more Protégé-grade imports workflow.

Primary roadmap anchor: ROADMAP.md → v0.16 — Workspace layouts + preferences + imports polish.

Must ship (P0)

  • Plugin-contributed Preferences pages (wired)
  • Manifests can declare [[ui.preferences_pages]] and those pages are discoverable + openable from the extension.

  • Provide a first-party “Preferences” surface with category navigation and search.

  • Plugin context actions (wired)

  • Manifests can declare [[ui.context_actions]] and the extension can surface them in at least one high-signal location (entity context).

  • Context actions execute via the existing plugin command registry and respect plugin permissions.

  • Imports polish

  • Improve Manage Imports UX around the common workflows: add/remove import, reload imports, inspect closure, and show clear diagnostics when imports fail.
  • Provide a single “imports health” view surfaced from the command palette.

Should ship (P1)

  • Layout persistence (minimal but real)
  • Restore key Strixonomy panels across sessions using VS Code’s supported persistence hooks (panel serializers) where possible.
  • Provide “Reset Strixonomy layout” command to return to a known good default.

Nice to have (P2)

  • Workspace perspectives

  • Named layouts (e.g. Modeling / Reasoning) built on top of persistence (save/restore).

  • Imports dependency graph

  • Visual graph view of import relationships (requires more UI + data work than P0/P1).

Non-goals (v0.16)

  • Full Protégé menu/toolbar/dialog parity (planned for v0.17).
  • A full “preferences sync” story across machines/teams (later platform milestone).