@korrlabs/mnemospi 4.2.0 → 4.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -312,3 +312,27 @@ Apache-2.0 — see [LICENSE](LICENSE) and [NOTICE](NOTICE). Source: [github.com/
312
312
 
313
313
  Contributions are welcome — [CONTRIBUTING.md](CONTRIBUTING.md) has the development setup, the branch
314
314
  and commit conventions, and the quality gate a change must pass.
315
+
316
+ ---
317
+
318
+ ## 🛠 CI / Релизы — кластерный конвейер `release-pipeline`
319
+
320
+ Этот проект подключён к общему кластерному конвейеру релизов
321
+ ([Korrnals/release-pipeline](https://github.com/Korrnals/release-pipeline),
322
+ K3s `abyss-ai-agent`, namespace `release-pipeline`). GitHub Actions не
323
+ используется (биллинг аккаунта заблокирован) — конвейер и есть штатный путь
324
+ релизов. Релизный артефакт подписывается трёхслойно: SHA256 → SBOM → cosign → GPG.
325
+
326
+ **Релиз новой версии:**
327
+ 1. `VERSION` → релизный коммит (конвенция репо) → тег `vX.Y.Z` → push.
328
+ 2. Обновить версию проекта в `projects[]` файла `~/.cache/release-pipeline-values.yaml` и применить:
329
+ ```bash
330
+ helm upgrade --install release-pipeline \
331
+ ~/LABs/Projects/Project-Umbra/release-pipeline/chart/release-pipeline \
332
+ --kube-context abyss-ai-agent -n release-pipeline \
333
+ -f ~/.cache/release-pipeline-values.yaml
334
+ ```
335
+ 3. Наблюдение: `kubectl --context abyss-ai-agent -n release-pipeline get jobs`,
336
+ логи: `kubectl ... logs -f job/release-<proj>-<ver>`.
337
+
338
+ Подробности (типы проектов, kaniko-контейнеры, teardown): README конвейера.
@@ -28,6 +28,10 @@ rewrite lifecycle.
28
28
  - **Tool output compression (hooks.post_tool_call)** — a tool returned a
29
29
  huge output you want substituted by a zero-loss CCR marker, with
30
30
  provenance stamped for strict marker validation.
31
+ - **Re-assembly (mid-session)** — only when memory changed materially (a
32
+ new decision, a rewritten context block that must surface). The
33
+ assembled block is prefix-stable by design; gratuitous re-assembly
34
+ rewrites the prefix and discards the cache the session was building.
31
35
 
32
36
  ## STEPS
33
37
 
@@ -92,6 +96,22 @@ rewrite lifecycle.
92
96
  project/agent/session/supersedes/content), so re-delivery cannot
93
97
  duplicate writes.
94
98
 
99
+ 6. **Keep assembly cache-friendly** (provider-agnostic cache discipline):
100
+
101
+ - Assemble the context once per session, or on material memory
102
+ change; mid-session re-assembly is reserved for significant
103
+ changes only.
104
+ - The assembled mnemos text is per-call conversation content (tail),
105
+ NOT a standing prefix — never inject mnemos blocks into the system
106
+ prompt.
107
+ - Do not change the MCP tool set or tool schemas mid-session; a tool
108
+ change invalidates the provider's cache for the entire session.
109
+ - Prefer append-over-rewrite on compaction: append the new summary
110
+ after the stable prefix rather than rewriting the prefix.
111
+ - Align system prompts once, at assembly time
112
+ (`mnemos_align_prefix`); dynamic values (timestamps, counters,
113
+ volatile state) go to the tail, never the prefix.
114
+
95
115
  ## DISCIPLINE
96
116
 
97
117
  - **Never assemble context by hand.** The pipeline stages (context filter,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@korrlabs/mnemospi",
3
- "version": "4.2.0",
3
+ "version": "4.3.0",
4
4
  "description": "Mnemos memory & knowledge server — Pi extension. Spawns `mnemos mcp-server` over stdio and exposes every mnemos_* tool as a native Pi tool, plus the mnemos skill pack.",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",