Repository navigation
v0.3.4 — Coordinated native memory release
Query-independent core memory, bounded lifecycle ledgers, and a coordinated Python/native-plugin release source.
Core baseline and query recall
- OpenCode, pi, and omp refresh a DB-backed core baseline for each admitted user run, separately from query recall.
- Core and recall have separate budgets. Recall excludes rows already loaded into the baseline and abstains when no additional evidence remains.
- Remember, forget, and retraction become visible without restarting the session; repeated turns do not accumulate duplicate injected entries.
LUMINARY_CORE_TOP_N=0disables baseline loading.
Bounded ledger retention
- Lifecycle maintenance retains the newest rows per exact scope: 10,000 episodes, 50,000 audit events, and 50,000 evidence rows by default.
- Configure
LUMINARY_EPISODE_MAX_ROWS,LUMINARY_EVENT_MAX_ROWS, andLUMINARY_EVIDENCE_MAX_ROWS;0disables pruning for that ledger. Older history beyond a cap is deleted during maintenance.
Release consistency and verification
- Python and the three native plugin packages use version
0.3.4from the same tagged source. The tag workflow builds and validates the native tarballs once, then uses those artifacts for GitHub assets and npm publication. - This forward release replaces the inconsistent npm
0.3.3builds without overwriting published versions or moving the old tag. - The inspector default-store regression test now isolates both
HOMEand WindowsUSERPROFILEfrom the operator's home.
Known limitations
- Native OpenCode Web GUI discovery and Hermes classic CLI/TUI visual inspection remain unsupported; the optional browser companion is not a native replacement.
- Local Node 22 dependency installation warns that
@opentui/core@0.7.0declares Node 26.4.0 or Bun 1.3.14. Build, OpenCode type checks, UI/plugin tests, and the real-model gate passed locally; this does not establish support for every host/runtime.
Installation and artifact verification
Python 0.3.4 is published on PyPI. npm latest is 0.3.4 for pi, OpenCode, and omp.
All three npm tarballs are byte-identical to the GitHub assets attached here, and every packaged dist resource matches its copy in the PyPI wheel. Registry digests were checked for the wheel, sdist, and npm tarballs. npm publication used GitHub Actions trusted publishing with signed provenance; no local npm login or passkey was needed for the release.