luminary-memory 0.3.3__tar.gz → 0.3.4__tar.gz

luminary_memory-0.3.4/.mailmap

@@ -0,0 +1 @@
+alertxsto <alertxsto@users.noreply.github.com> OpenAI Codex <noreply@openai.com>

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## [Unreleased]
+
+## [0.3.4] - 2026-11-14
+
+Coordinated Python and native-plugin release from one source revision.
+This replaces the mismatched npm `0.3.3` builds without overwriting them.
+
+### Fixed
+
+- Isolate the inspector's default-store test from the operator's home on
+  Windows by setting `USERPROFILE` as well as `HOME`.
+- Native core memory is now a separate, query-independent DB-backed baseline
+  loaded through the bridge's new `core` action, which takes no query. Query
+  recall stays pure evidence: it removes rows already present in the loaded
+  baseline and returns `abstain` with `matches_already_in_core` when only core
+  rows matched, instead of reporting them as a successful query result. The
+  OpenCode, pi, and omp adapters refresh their own marked request-local baseline
+  each admitted user run, so explicit remember/forget/retraction becomes visible
+  without a session restart and repeated turns do not append duplicate
+  transcript entries. Core and recall keep separate row and character budgets,
+  rows are serialized once without adapters slicing or double-encoding them, and
+  empty or failed recall injects no model-bound context or status payload.
+  Baseline loading remains disabled by `LUMINARY_CORE_TOP_N=0`.
+- Long-lived stores now bound their append-only ledgers. `run_lifecycle()`
+  keeps the newest scoped rows for episodes (`LUMINARY_EPISODE_MAX_ROWS`,
+  default 10,000), audit events (`LUMINARY_EVENT_MAX_ROWS`, default 50,000),
+  and evidence (`LUMINARY_EVIDENCE_MAX_ROWS`, default 50,000); `0` disables a
+  ledger's pruning. Current-session continuity and recent audit remain intact.
+
 ## [0.3.3] - 2026-11-10
 
 Interactive memory inspection, explicit owner controls and safer native recall.
@@ -16,6 +45,12 @@ companion; the interactive UI roadmap is incomplete.
 
 ### Added
 
+- Published the Python bridge and all three native npm packages at `0.3.3`.
+  The npm packages were published later from `develop`, not the `v0.3.3`
+  tag, and their built entry points differ from the downloadable release
+  tarballs. Matching version numbers do not establish compatibility or
+  identical provenance. Use the tagged GitHub tarballs with Python `0.3.3`
+  until a coordinated replacement release is available.
 - Optional operator config file (`~/.luminary/luminary.env`) shared by native
   integrations and the CLI. Env-style `LUMINARY_*` settings load before
   `Settings` is constructed; process environment wins, `LUMINARY_CONFIG_FILE`

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: luminary-memory
-Version: 0.3.3
+Version: 0.3.4
 Summary: A lightweight, self-hosted memory layer for AI agents
 Project-URL: Homepage, https://github.com/alertxsto/luminary-memory
 Project-URL: Repository, https://github.com/alertxsto/luminary-memory
@@ -118,8 +118,8 @@ at [`opencode/SKILL.md`](opencode/SKILL.md); install it under
 
 The `0.3.3` source includes native interactive inspectors for the verified
 surfaces: OpenCode CLI/Desktop, pi and omp, Hermes Desktop/dashboard and an
-explicitly launched loopback companion. The `0.3.2` registry packages do not
-include the inspector; see the installation guide for current availability.
+explicitly launched loopback companion. The `0.3.3` registry packages include
+the inspector; see the installation guide for current availability.
 Two native targets remain blocked on upstream
 contracts and are recorded in the roadmap: OpenCode Web GUI contribution
 discovery and Hermes terminal/TUI authority plus scope lifecycle. See
@@ -146,8 +146,10 @@ The three installable tarballs are written to `artifacts/plugins/`. Set
 Choose the native package **or** the copied hook, never both.
 
 Registry names are `luminary-memory-pi`, `luminary-memory-opencode`, and
-`luminary-memory-omp`. All three npm packages and the Python bridge are
-published at `0.3.2`; npm `latest` points to that version.
+`luminary-memory-omp`. Use version-matched Python and plugin artifacts from
+the same tagged release. The npm `0.3.3` builds were published from a later
+`develop` revision and differ from the `v0.3.3` GitHub tarballs; use those
+tagged tarballs with Python `0.3.3`, not the npm builds.
 The pi manifest includes `pi-package` for eligibility in the
 [official package catalog](https://pi.dev/packages). OpenCode's existing
 Ecosystem PR targets legacy V1 docs, not a verified V2 listing; no V2 website
@@ -244,6 +246,9 @@ Every setting has a `LUMINARY_*` env var or a `Settings` object.
 | `dedup_jaccard_threshold` | `LUMINARY_DEDUP_JACCARD_THRESHOLD` | `0.85` |
 | `token_budget` | `LUMINARY_TOKEN_BUDGET` | `4096` |
 | `max_memories` | `LUMINARY_MAX_MEMORIES` | `1000` |
+| `episode_max_rows` | `LUMINARY_EPISODE_MAX_ROWS` | `10000` |
+| `event_max_rows` | `LUMINARY_EVENT_MAX_ROWS` | `50000` |
+| `evidence_max_rows` | `LUMINARY_EVIDENCE_MAX_ROWS` | `50000` |
 | `ttl_default_seconds` | `LUMINARY_TTL_DEFAULT_SECONDS` | `null` |
 | `prune_min_importance` | `LUMINARY_PRUNE_MIN_IMPORTANCE` | `0.2` |
 | `consolidate_jaccard_threshold` | `LUMINARY_CONSOLIDATE_JACCARD_THRESHOLD` | `0.9` |

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/README.md

@@ -83,8 +83,8 @@ at [`opencode/SKILL.md`](opencode/SKILL.md); install it under
 
 The `0.3.3` source includes native interactive inspectors for the verified
 surfaces: OpenCode CLI/Desktop, pi and omp, Hermes Desktop/dashboard and an
-explicitly launched loopback companion. The `0.3.2` registry packages do not
-include the inspector; see the installation guide for current availability.
+explicitly launched loopback companion. The `0.3.3` registry packages include
+the inspector; see the installation guide for current availability.
 Two native targets remain blocked on upstream
 contracts and are recorded in the roadmap: OpenCode Web GUI contribution
 discovery and Hermes terminal/TUI authority plus scope lifecycle. See
@@ -111,8 +111,10 @@ The three installable tarballs are written to `artifacts/plugins/`. Set
 Choose the native package **or** the copied hook, never both.
 
 Registry names are `luminary-memory-pi`, `luminary-memory-opencode`, and
-`luminary-memory-omp`. All three npm packages and the Python bridge are
-published at `0.3.2`; npm `latest` points to that version.
+`luminary-memory-omp`. Use version-matched Python and plugin artifacts from
+the same tagged release. The npm `0.3.3` builds were published from a later
+`develop` revision and differ from the `v0.3.3` GitHub tarballs; use those
+tagged tarballs with Python `0.3.3`, not the npm builds.
 The pi manifest includes `pi-package` for eligibility in the
 [official package catalog](https://pi.dev/packages). OpenCode's existing
 Ecosystem PR targets legacy V1 docs, not a verified V2 listing; no V2 website
@@ -209,6 +211,9 @@ Every setting has a `LUMINARY_*` env var or a `Settings` object.
 | `dedup_jaccard_threshold` | `LUMINARY_DEDUP_JACCARD_THRESHOLD` | `0.85` |
 | `token_budget` | `LUMINARY_TOKEN_BUDGET` | `4096` |
 | `max_memories` | `LUMINARY_MAX_MEMORIES` | `1000` |
+| `episode_max_rows` | `LUMINARY_EPISODE_MAX_ROWS` | `10000` |
+| `event_max_rows` | `LUMINARY_EVENT_MAX_ROWS` | `50000` |
+| `evidence_max_rows` | `LUMINARY_EVIDENCE_MAX_ROWS` | `50000` |
 | `ttl_default_seconds` | `LUMINARY_TTL_DEFAULT_SECONDS` | `null` |
 | `prune_min_importance` | `LUMINARY_PRUNE_MIN_IMPORTANCE` | `0.2` |
 | `consolidate_jaccard_threshold` | `LUMINARY_CONSOLIDATE_JACCARD_THRESHOLD` | `0.9` |

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/docs/agent-integrations.md

@@ -8,9 +8,9 @@ continues to use its public `MemoryProvider` lifecycle.
 | Adapter | Contract | Interaction surface |
 | --- | --- | --- |
 | Hermes | Public `MemoryProvider`, existing installer | Provider tools/status in supported Hermes clients; read-only scoped Telegram activity hook |
-| OpenCode V2 | `@opencode/cli` and `@opencode/plugin` 2.1.4, `Plugin.define` server API | Native tools/progress/results in connected clients; automatic recall and curated retention |
-| pi | Extension API verified against `@earendil-works/pi-coding-agent` 1.4.0 | `/luminary`, model tool, TUI dialogs/status, serializable session messages for RPC consumers |
-| omp | Extension API verified against v18.12.6; installed **18.18.5** acceptance re-verified | `/luminary`, model tool, TUI dialogs/status, serializable session messages for RPC consumers |
+| OpenCode V2 | `@opencode/cli` and `@opencode/plugin` 2.1.4, `Plugin.define` server API | Native tools/progress/results in connected clients; core baseline, automatic recall, and curated retention |
+| pi | Extension API verified against `@earendil-works/pi-coding-agent` 1.4.0 | `/luminary`, model tool, TUI dialogs/status, core baseline and automatic recall, serializable session messages for RPC consumers |
+| omp | Extension API verified against v18.12.6; installed **18.18.5** acceptance re-verified | `/luminary`, model tool, TUI dialogs/status, core baseline and automatic recall, serializable session messages for RPC consumers |
 
 OpenCode V2 uses the plural `plugins` config, a default `Plugin.define` export,
 and Promise domain APIs. The older Luminary npm `0.3.1` adapter targets V1;
@@ -25,13 +25,15 @@ and omp. That means ownership by this project, not endorsement or listing
 approval by the harness maintainers. All three compile the canonical adapter
 source under `src/luminary_memory/integrations/assets/`; no second memory engine
 or separate adapter fork is maintained.
-Python and all three native npm packages are published at `0.3.2`, with npm
-`latest` pointing to that version. The OpenCode adapter targets V2; the older
-npm `0.3.1` adapter is V1-only. Install the Python bridge into the environment
+Python and all three native npm packages list `0.3.3`, but the later npm
+builds differ from the tagged GitHub tarballs. Use those tagged tarballs
+with Python `0.3.3` until a coordinated replacement is published.
+The OpenCode adapter targets V2; the older npm `0.3.1` adapter is V1-only.
+Install the Python bridge into the environment
 the host will use:
 
 ```bash
-python -m pip install --upgrade "luminary-memory==0.3.2"
+python -m pip install --upgrade "luminary-memory==0.3.3"
 export LUMINARY_PYTHON=/absolute/venv/bin/python
 ```
 
@@ -63,7 +65,7 @@ path. No package install hook silently installs Python dependencies.
 | --- | --- | --- |
 | pi | `pi install /absolute/repo/plugins/pi` | `pi install npm:luminary-memory-pi` |
 | omp | `omp plugin link /absolute/repo/plugins/omp` | `omp plugin install luminary-memory-omp` |
-| OpenCode V2 | `{"plugins":["/absolute/repo/plugins/opencode/dist"]}`; configured local paths must be directories | `opencode plugin add luminary-memory-opencode@0.3.2`, or `{"plugins":["luminary-memory-opencode@0.3.2"]}` |
+| OpenCode V2 | `{"plugins":["/absolute/repo/plugins/opencode/dist"]}`; configured local paths must be directories | `opencode plugin add luminary-memory-opencode@0.3.3`, or `{"plugins":["luminary-memory-opencode@0.3.3"]}` |
 
 Local pi/omp packages load in place, so keep the installed directory. An
 extracted tarball works independently of this repository. See the host READMEs
@@ -110,12 +112,21 @@ The first publication requires maintainer npm authorization. Use
 the next coordinated release; do not overwrite an already-published Python tag.
 See [contributor release instructions](../CONTRIBUTING.md).
 
-Publication verified on 2026-10-25: Python and all three npm packages are
-available at `0.3.2`:
+Publication verified on 2026-11-14: Python and all three npm packages are
+available at `0.3.3`:
 [pi](https://www.npmjs.com/package/luminary-memory-pi),
 [OpenCode](https://www.npmjs.com/package/luminary-memory-opencode), and
 [omp](https://www.npmjs.com/package/luminary-memory-omp).
-All npm `latest` tags and SHA-512 checksums match the validated release assets.
+All npm `latest` tags point to `0.3.3`. Verified SHA-1 shasums:
+pi `a5c613417ef20c4e178e53a5e56e5b9e4e0c121d`,
+OpenCode `ee8ffe5a4089b5441dde52af9a90d4f0ce37fe9b`,
+omp `82d18ba70ebba95d3566c1f394561000a76d34c5`.
+
+These npm shasums do not match the `v0.3.3` GitHub release tarballs. The npm
+entry points match later `develop` builds, which use the new `core` bridge
+action. Do not treat npm and PyPI `0.3.3` as one validated release. Existing
+published versions and tags are immutable; recovery uses a new coordinated
+version built and gated by the tag workflow.
 Installing all three from npm succeeded. The real V2 CLI also installed the
 OpenCode package and an actual native session stored a fact through the
 published PyPI wheel. That wheel's CLI installer and remember/recall/forget
@@ -141,7 +152,7 @@ proof of a live website listing.
 ## Interactive inspectors
 
 The `0.3.3` source includes the inspector in the Python and native npm
-packages. The published `0.3.2` packages do not include it. Installing the
+packages. The published `0.3.3` packages include it. Installing the
 inspector does not enable saving, start a server on import, or call an AI model.
 Exact tested native hosts and the two remaining blocked surfaces are recorded
 in the [roadmap matrix](ROADMAP.md#target-support-matrix).
@@ -241,7 +252,7 @@ This remains an alternative to native package installation. Install the
 published Python bridge, then copy only the adapter for the host you use:
 
 ```bash
-python -m pip install --upgrade "luminary-memory==0.3.2"
+python -m pip install --upgrade "luminary-memory==0.3.3"
 luminary-memory hook install opencode
 luminary-memory hook install pi
 luminary-memory hook install omp
@@ -370,16 +381,61 @@ or to a project's `.opencode/skills/luminary-memory/SKILL.md`. OpenCode
 discovers both locations automatically; no `opencode.json` entry is required.
 The skill is documentation only and does not change plugin behavior.
 
-## Automatic recall and retention
-
-Before a normal user run, adapters recall strictly relevant, evidence-bearing
-memory. Core-tagged rows must pass the same retrieval gate; unrelated core
-rows do not override abstention. This differs from Hermes's separate pinned-core
-surface. Historical data is a request-local, non-system reference before the
-live user message, not a persistent transcript entry. Empty recall injects
-nothing. Whole JSON records are serialized once within the bridge's 8000-character
-budget; adapters do not slice or double-encode that reference. Aborted/error/
-tool-only responses are not automatically retained. Compaction is not a write.
+## Core baseline
+
+Core memory is a separate, database-backed baseline, not part of query recall.
+Confirmed core-tagged rows load independently of the current query before the
+live user message. `core` is a bridge action with no query or text field: it
+takes the usual agent, workspace, and session binding and returns status `ok`
+with the currently valid core rows and one labeled `<luminary-core-memory>`
+context block. Empty core is `ok` with `memories: []` and `context: ""`; it is
+not an error, does not call query recall, and does not mutate access or ranking
+state.
+
+Core selection binds the exact adapter scope without global rows and keeps only
+active, currently valid rows. Rows follow their stable core-tag insertion order;
+`LUMINARY_CORE_TOP_N` (default 12, capped at 12; `0` disables baseline loading)
+limits how many rows are used and `LUMINARY_CORE_BUDGET` (default 8000)
+bounds the total content characters across the selected rows, not the rendered
+block including JSON, IDs, tags, or labels. A row that does not fit whole is
+skipped, never truncated. Adapters fetch core afresh at the start of each
+admitted user run, so an explicit remember, forget, or retraction is visible
+without restarting the host. The block is request-local, non-system reference
+data: adapters replace their own marked baseline instead of appending duplicate
+transcript entries. Its label says confirmed durable identity, preferences, and
+rules are subordinate default context; current system instructions, verified
+runtime state, and an explicit current user correction take precedence without
+silently editing stored memory. A failed core request injects no fabricated
+baseline.
+
+pi and omp prepend the core block and then a non-empty successful recall
+reference as request-only custom messages in their `context` hook; OpenCode
+unshifts the matching request-local parts before the live user message in its
+`context` hook. All three filter out their own previously injected baseline and
+recall entries so repeated turns do not grow the visible conversation. Hosts
+may resend baseline when their model API requires it, equivalent to resending
+`AGENTS.md`; the adapter does not create a duplicate transcript entry.
+
+## Query recall
+
+Before a normal user run, adapters recall only query-relevant,
+evidence-bearing memory. Recall is pure: a returned row already represented in
+the loaded core baseline by ID or normalized content is removed, so it never
+appears twice. If only core rows matched, recall returns `abstain` with
+`reason: matches_already_in_core`, empty `memories`, and empty `context`; core
+never turns abstention into success. An engine `ok` result whose rows are all
+invalid, already in core, or otherwise not deliverable becomes `abstain` with
+`reason: no_deliverable_candidate` (or `matches_already_in_core` when only core
+matched), with empty `memories` and `context`. Other results keep the engine's
+status and reason. Recall uses its own row cap and 8000-character whole-row
+serialization budget; the core budget is separate and neither expands the other.
+
+The recall result is a request-local, non-system reference before the live user
+message, not a persistent transcript entry. Empty, abstained, or failed recall
+injects nothing: pi/omp add no custom message and OpenCode adds no recall part.
+Historical data is untrusted; adapters attach the bridge's context string as-is
+without slicing or double JSON encoding. Aborted/error/tool-only responses are
+not automatically retained. Compaction is not a write.
 
 Automatic durable capture is disabled unless configured:
 
@@ -410,19 +466,29 @@ Run `python -m luminary_memory.integrations bridge` (or
 `luminary-memory hook bridge`) with **one UTF-8 JSON object on stdin**, then
 close stdin. Never interpolate user text into a shell command:
 
+Query recall:
+
 ```json
 {"agent":"another-supported-host","workspace":"/absolute/project","session_id":"native-session-42","action":"recall","query":"deploy target"}
 ```
 
+Baseline load (no query):
+
+```json
+{"agent":"another-supported-host","workspace":"/absolute/project","session_id":"native-session-42","action":"core"}
+```
+
 The stable harness identifier accepts `[a-z][a-z0-9._-]{0,63}`; it is an ownership
-key, not a dynamically loaded plugin name. Actions: `recall` (`query`), `remember`
-(`text`, `evidence_quote`, optional `tags`), `forget` (`memory_id`), `activity`, and `turn` (`user`,
-`assistant`, optional lineage `tags`). Every action requires absolute workspace,
-agent ID, and native session ID. Maximum request: 128 KiB; each text field:
-32,768 characters. A response is a UTF-8 JSON object containing `ok`, `status`,
-`reason`, `message`, `context`, `memories`, `stored`, and `deleted`; errors exit
-nonzero. Keep stdout reserved for that response and treat recalled data as
-untrusted. Native adapters bound process lifetime/output and use no shell.
+key, not a dynamically loaded plugin name. Actions: `core` (no query or text),
+`recall` (`query`), `remember` (`text`, `evidence_quote`, optional `tags`),
+`forget` (`memory_id`), `activity`, and `turn` (`user`, `assistant`, optional
+lineage `tags`). Every action requires absolute workspace, agent ID, and native
+session ID. Maximum request: 128 KiB; each text field: 32,768 characters. A
+response is a UTF-8 JSON object containing `ok`, `status`, `reason`, `message`,
+`context`, `memories`, `stored`, and `deleted`; errors exit nonzero. `core`
+returns status `ok` even when it has no valid rows, in which case `memories` and
+`context` are empty. Keep stdout reserved for that response and treat recalled
+data as untrusted. Native adapters bound process lifetime/output and use no shell.
 
 For remember, the **trusted adapter**, never model arguments, supplies a fresh
 `LUMINARY_BRIDGE_SOURCE` environment value to that one child process:

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/package-lock.json

@@ -6544,7 +6544,7 @@
     },
     "plugins/omp": {
       "name": "luminary-memory-omp",
-      "version": "0.3.3",
+      "version": "0.3.4",
       "license": "Apache-2.0",
       "engines": {
         "bun": ">=1.3.14",
@@ -6565,7 +6565,7 @@
     },
     "plugins/opencode": {
       "name": "luminary-memory-opencode",
-      "version": "0.3.3",
+      "version": "0.3.4",
       "license": "Apache-2.0",
       "dependencies": {
         "zod": "4.6.7"
@@ -6600,7 +6600,7 @@
     },
     "plugins/pi": {
       "name": "luminary-memory-pi",
-      "version": "0.3.3",
+      "version": "0.3.4",
       "license": "Apache-2.0",
       "engines": {
         "node": ">=22.19.0"

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/omp/README.md

@@ -9,16 +9,14 @@ embedded Bun runtime to load extensions.
 
 ## Registry installation
 
-The registry commands below install `0.3.2`, which has no inspector. For the
-`0.3.3` inspector, use the matching Python bridge and native package built from
-this checkout or obtained from the GitHub release when available.
+The registry commands below install `0.3.3`, which includes the inspector.
 
 Install the published Python bridge from PyPI, then install the omp package:
 
 ```sh
-python -m pip install --upgrade "luminary-memory==0.3.2"
+python -m pip install --upgrade "luminary-memory==0.3.3"
 export LUMINARY_PYTHON=/absolute/path/to/venv/bin/python
-omp plugin install luminary-memory-omp@0.3.2
+omp plugin install luminary-memory-omp@0.3.3
 ```
 
 No npm install script installs Python for you. Set `LUMINARY_PYTHON` to the

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/omp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luminary-memory-omp",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Luminary-maintained scoped memory extension for oh-my-pi, backed by the Luminary Python bridge",
   "type": "module",
   "main": "./dist/index.js",

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/opencode/README.md

@@ -6,35 +6,33 @@ and **`@opencode/plugin` 2.2.0**. This is an official Luminary package,
 
 **Development scope:** the `0.3.3` source includes this inspector
 for OpenCode CLI and Desktop on `@opencode/cli` and `@opencode/plugin`
-**2.2.0**. The published `0.3.2` bridge contains no inspector and was verified
-on OpenCode 2.1.4; `0.3.1` targets the separate V1 API. Native Web GUI
+**2.2.0**. The published `0.3.3` bridge includes the inspector; `0.3.2` was
+verified on OpenCode 2.1.4, and `0.3.1` targets the separate V1 API. Native Web GUI
 contribution discovery remains
 blocked upstream. See the [target matrix](https://github.com/alertxsto/luminary-memory/blob/develop/docs/ROADMAP.md#target-support-matrix)
 for exact scope, lifecycle and release limitations.
 
 ## Install
 
-The registry commands below install `0.3.2`, which has no inspector. For the
-`0.3.3` inspector, use the matching Python bridge and native package built from
-this checkout or obtained from the GitHub release when available.
+The registry commands below install `0.3.3`, which includes the inspector.
 
 Install the published Python bridge from PyPI:
 
 ```sh
-python -m pip install --upgrade "luminary-memory==0.3.2"
+python -m pip install --upgrade "luminary-memory==0.3.3"
 export LUMINARY_PYTHON=/absolute/path/to/venv/bin/python
 ```
 
 Install the V2 npm package through OpenCode:
 
 ```sh
-opencode plugin add luminary-memory-opencode@0.3.2
+opencode plugin add luminary-memory-opencode@0.3.3
 ```
 
 Alternatively, add it to your existing `opencode.json` or `opencode.jsonc`:
 
 ```json
-{"plugins": ["luminary-memory-opencode@0.3.2"]}
+{"plugins": ["luminary-memory-opencode@0.3.3"]}
 ```
 
 V2 uses **`plugins`**, not V1's singular `plugin`. The host provides the SDK and
@@ -150,7 +148,7 @@ Compatible clients consume the server's native tools/results. This package does
 not add a universal client toolbar or a standalone desktop app. Before enabling
 it, remove only the old copied Luminary adapter and its explicit config entry;
 do not run both installation forms. To remove the package, use
-`opencode plugin remove luminary-memory-opencode@0.3.2` or remove its config
+`opencode plugin remove luminary-memory-opencode@0.3.3` or remove its config
 entry. Reload/restart the server as needed. Stored memory is not deleted.
 
 ## Compatibility evidence
@@ -176,7 +174,7 @@ review. This is not a verified V2 catalog or a live website listing.
 The obsolete local listing patch is no longer shipped.
 
 [Source PR #17](https://github.com/alertxsto/luminary-memory/pull/17) has merged.
-Python and all three native npm packages are published at `0.3.2`.
+Python and all three native npm packages are published at `0.3.3`.
 
 [Configuration and ownership](https://github.com/alertxsto/luminary-memory/blob/main/docs/agent-integrations.md)
 · [OpenCode V2 plugin contract](https://opencode.ai/v2/docs/plugins/)

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/opencode/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luminary-memory-opencode",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Luminary-maintained scoped memory plugin for OpenCode V2",
   "type": "module",
   "main": "./dist/index.js",

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/pi/README.md

@@ -9,16 +9,14 @@ versions accepted by the root manifest).
 
 ## Registry installation
 
-The registry commands below install `0.3.2`, which has no inspector. For the
-`0.3.3` inspector, use the matching Python bridge and native package built from
-this checkout or obtained from the GitHub release when available.
+The registry commands below install `0.3.3`, which includes the inspector.
 
 Install the published Python bridge from PyPI, then install the pi package:
 
 ```sh
-python -m pip install --upgrade "luminary-memory==0.3.2"
+python -m pip install --upgrade "luminary-memory==0.3.3"
 export LUMINARY_PYTHON=/absolute/path/to/venv/bin/python
-pi install npm:luminary-memory-pi@0.3.2
+pi install npm:luminary-memory-pi@0.3.3
 ```
 
 No npm install script installs Python for you. Set `LUMINARY_PYTHON` to the

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/plugins/pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luminary-memory-pi",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "description": "Luminary-maintained scoped memory extension for pi, backed by the Luminary Python bridge",
   "type": "module",
   "main": "./dist/index.js",

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "luminary-memory"
-version = "0.3.3"
+version = "0.3.4"
 description = "A lightweight, self-hosted memory layer for AI agents"
 readme = "README.md"
 license = { text = "Apache-2.0" }

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/src/luminary_memory/__init__.py

@@ -1,4 +1,4 @@
 from luminary_memory.api import MemoryClient
 
-__version__ = "0.3.3"
+__version__ = "0.3.4"
 __all__ = ["MemoryClient", "__version__"]

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/src/luminary_memory/backends/base.py

@@ -120,6 +120,33 @@ class MemoryBackend(ABC):
         """Return insertion/duplicate acknowledgement, or None without a ledger."""
         return
 
+    def prune_episodes(
+        self,
+        max_rows: int,
+        scope: dict | None = None,
+        include_global: bool = True,
+    ) -> int:
+        """Delete oldest scoped episodes beyond *max_rows*; 0 disables."""
+        return 0
+
+    def prune_events(
+        self,
+        max_rows: int,
+        scope: dict | None = None,
+        include_global: bool = True,
+    ) -> int:
+        """Delete oldest scoped audit events beyond *max_rows*; 0 disables."""
+        return 0
+
+    def prune_evidence(
+        self,
+        max_rows: int,
+        scope: dict | None = None,
+        include_global: bool = True,
+    ) -> int:
+        """Delete oldest scoped evidence rows beyond *max_rows*; 0 disables."""
+        return 0
+
     def recent_episodes(
         self,
         limit: int = 10,

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/src/luminary_memory/backends/inspector.py

@@ -180,6 +180,73 @@ class InspectorSQL:
                    *(scope[field] for field in fields)))
         self._commit()
 
+    def _prune_ledger(self, table: str, max_rows: int, scope, include_global: bool) -> int:
+        """Delete oldest scoped rows beyond a hard row cap.
+
+        The cap is deterministic and keeps the newest rows, so current-session
+        continuity and recent audit remain available. 0 disables pruning.
+        """
+        from luminary_memory.scope import scope_sql
+
+        cap = max(0, int(max_rows))
+        if cap == 0:
+            return 0
+        where, params = scope_sql(
+            scope, alias="e", include_global=include_global, active_only=False
+        )
+        total = int(self._sql(
+            f"SELECT COUNT(*) FROM {table} e WHERE {where}", tuple(params)
+        ).fetchone()[0])
+        excess = total - cap
+        if excess <= 0:
+            return 0
+        order = "e.created_at ASC, e.id ASC"
+        if table == "episodes" and not hasattr(self, "_psycopg"):
+            order = "e.created_at ASC, e.rowid ASC"
+        self._sql(
+            f"DELETE FROM {table} WHERE id IN "
+            f"(SELECT e.id FROM {table} e WHERE {where} ORDER BY {order} LIMIT ?)",
+            (*params, excess),
+        )
+        self._commit()
+        return excess
+
+    def prune_episodes(self, max_rows: int, scope=None, include_global: bool = True) -> int:
+        return self._prune_ledger("episodes", max_rows, scope, include_global)
+
+    def prune_events(self, max_rows: int, scope=None, include_global: bool = True) -> int:
+        return self._prune_ledger("memory_events", max_rows, scope, include_global)
+
+    def prune_evidence(self, max_rows: int, scope=None, include_global: bool = True) -> int:
+        """Prune evidence by its owning memory's scope; evidence has no scope columns."""
+        from luminary_memory.scope import scope_sql
+
+        cap = max(0, int(max_rows))
+        if cap == 0:
+            return 0
+        memory_where, params = scope_sql(
+            scope, alias="m", include_global=include_global, active_only=False
+        )
+        where = f"e.memory_id IN (SELECT m.id FROM memories m WHERE {memory_where})"
+        if scope is None and include_global:
+            # Orphaned evidence has no owner left to scope it; only an
+            # unscoped/global lifecycle pass may reclaim it.
+            where = f"(e.memory_id IS NULL OR {where})"
+        total = int(self._sql(
+            f"SELECT COUNT(*) FROM memory_evidence e WHERE {where}", tuple(params)
+        ).fetchone()[0])
+        excess = total - cap
+        if excess <= 0:
+            return 0
+        self._sql(
+            "DELETE FROM memory_evidence WHERE id IN "
+            f"(SELECT e.id FROM memory_evidence e WHERE {where} "
+            "ORDER BY e.created_at ASC, e.id ASC LIMIT ?)",
+            (*params, excess),
+        )
+        self._commit()
+        return excess
+
     def inspector_get(self, key, default=None):
         row = self._sql("SELECT value FROM inspector_metadata WHERE key = ?", (key,)).fetchone()
         return json.loads(row[0]) if row else default

{luminary_memory-0.3.3 → luminary_memory-0.3.4}/src/luminary_memory/config.py

@@ -229,6 +229,10 @@ class Settings:
     )
     token_budget: int = field(default_factory=lambda: _env_int("LUMINARY_TOKEN_BUDGET", 4096))
     max_memories: int | None = field(default_factory=lambda: _env_int("LUMINARY_MAX_MEMORIES", 1000))
+    # Append-only ledger retention. 0 disables pruning for that ledger.
+    episode_max_rows: int = field(default_factory=lambda: _env_int("LUMINARY_EPISODE_MAX_ROWS", 10000))
+    event_max_rows: int = field(default_factory=lambda: _env_int("LUMINARY_EVENT_MAX_ROWS", 50000))
+    evidence_max_rows: int = field(default_factory=lambda: _env_int("LUMINARY_EVIDENCE_MAX_ROWS", 50000))
     # Safety policy.  Legacy direct clients keep permissive recall unless
     # enabled, while Hermes/CLI accuracy paths opt into strict abstention.
     strict_recall: bool = field(default_factory=lambda: _env_bool("LUMINARY_STRICT_RECALL", False))
@@ -300,6 +304,9 @@ class Settings:
             "recall_min_score": self.recall_min_score,
             "token_budget": self.token_budget,
             "max_memories": self.max_memories,
+            "episode_max_rows": self.episode_max_rows,
+            "event_max_rows": self.event_max_rows,
+            "evidence_max_rows": self.evidence_max_rows,
             "strict_recall": self.strict_recall,
             "scope_include_global": self.scope_include_global,
             "abstention_min_confidence": self.abstention_min_confidence,