opencode-codex-memory 0.7.5 → 0.7.6

package/README.md

@@ -53,7 +53,7 @@ If you want the mental model — learning, remembering, forgetting — see
 
 ```json
 {
-  "plugin": ["opencode-codex-memory@0.7.5"]
+  "plugin": ["opencode-codex-memory@0.7.6"]
 }
 ```
 
@@ -73,7 +73,7 @@ V2 plugin syntax:
 
 ```jsonc
 {
-  "plugins": [{ "package": "opencode-codex-memory@0.7.5" }],
+  "plugins": [{ "package": "opencode-codex-memory@0.7.6" }],
 }
 ```
 
@@ -208,7 +208,7 @@ To set options, turn the plugin entry into a `[name, options]` pair:
 ```json
 {
   "plugin": [
-    ["opencode-codex-memory@0.7.5", { "disable_on_external_context": true, "min_rollout_idle_hours": 2 }]
+    ["opencode-codex-memory@0.7.6", { "disable_on_external_context": true, "min_rollout_idle_hours": 2 }]
   ]
 }
 ```
@@ -280,7 +280,7 @@ dedicated directory:
 ```json
 {
   "plugin": [
-    ["opencode-codex-memory@0.7.5", { "home": "/path/to/opencode-memory" }]
+    ["opencode-codex-memory@0.7.6", { "home": "/path/to/opencode-memory" }]
   ]
 }
 ```
@@ -290,7 +290,7 @@ OpenCode 2:
 ```jsonc
 {
   "plugins": [
-    { "package": "opencode-codex-memory@0.7.5", "options": { "home": "/path/to/opencode-memory" } }
+    { "package": "opencode-codex-memory@0.7.6", "options": { "home": "/path/to/opencode-memory" } }
   ]
 }
 ```
@@ -325,7 +325,7 @@ Off by default; no changes to Codex's own config are required.
 {
   "plugin": [
     [
-      "opencode-codex-memory@0.7.5",
+      "opencode-codex-memory@0.7.6",
       { "codex_interop": { "import": true, "export": true } }
     ]
   ]
@@ -382,7 +382,7 @@ from the project memories Claude already keeps on your machine. **One-way only**
 ```json
 {
   "plugin": [
-    ["opencode-codex-memory@0.7.5", { "claude_import": { "enabled": true } }]
+    ["opencode-codex-memory@0.7.6", { "claude_import": { "enabled": true } }]
   ]
 }
 ```
@@ -409,7 +409,7 @@ Claude names each project with an opaque id (a folder under
 {
   "plugin": [
     [
-      "opencode-codex-memory@0.7.5",
+      "opencode-codex-memory@0.7.6",
       {
         "claude_import": {
           "enabled": true,

package/dist/src/v2/citation-overlay.d.ts

@@ -3,5 +3,5 @@
  * the TUI renders fenced `memory-citation` blocks, so the V2 context hook
  * overlays this section onto the shared inject prompt.
  */
-export declare const V2_CITATION_INSTRUCTIONS = "Memory citation requirements:\n\n- If ANY relevant memory files were used: append exactly one fenced code\n  block with the language tag `memory-citation` as the VERY LAST content of\n  the final reply. Normal responses should include the answer first, then\n  append the block at the end. The host renders this block natively.\n- Use this exact structure for programmatic parsing:\n````\n```memory-citation\nMEMORY.md:234-236|note=build command for the api service\nrollout_summaries/2026-02-17T21-23-02-ln3m-example.md:10-12|note=weekly report format\nsessions: ses_abc123 ses_def456\n```\n````\n- Do not wrap it in `<memory-citation>` XML tags; the fenced form replaces\n  that older format.\n- Citation entry lines are for rendering:\n  - one citation entry per line\n  - format: `<file>:<line_start>-<line_end>|note=<how memory was used>`\n  - use file paths relative to the memory base path (for example, `MEMORY.md`,\n    `rollout_summaries/...`, `skills/...`)\n  - only cite files actually used under the memory base path (do not cite\n    workspace files as memory citations)\n  - if you used `MEMORY.md` and then a rollout summary/skill file, cite both\n  - list entries in order of importance (most important first)\n  - `note` should be short, single-line, and use simple characters only (avoid\n    unusual symbols, no newlines)\n- The final `sessions:` line is for us to track which past sessions you find\n  useful:\n  - one line, space-separated session ids after `sessions:`\n  - session ids look like `ses_...` and appear in rollout summary files and\n    MEMORY.md as `session_id:`\n  - include unique ids only; do not repeat ids\n  - omit the `sessions:` line if no session ids are available\n  - do not include file paths or notes on this line\n  - for every citation entry, try to find and cite the corresponding session id\n- Never include memory citations inside pull-request messages.\n- Never cite blank lines; double-check ranges.\n\n";
+export declare const V2_CITATION_INSTRUCTIONS = "Memory citation requirements:\n\n- If ANY relevant memory files were used: append exactly one fenced code\n  block with the language tag `memory-citation` as the VERY LAST content of\n  the final reply. Answer first, then a blank line, then the block. The\n  opening fence must be on its own line at column 0 \u2014 never glue it to the\n  last sentence, or markdown clients treat the block as paragraph text and\n  collapse its newlines. The host renders this block natively.\n- Use this exact structure for programmatic parsing (blank line before the\n  fence is required):\n````\nanswer text ends here.\n\n```memory-citation\nMEMORY.md:234-236|note=build command for the api service\nrollout_summaries/2026-02-17T21-23-02-ln3m-example.md:10-12|note=weekly report format\nsessions: ses_abc123 ses_def456\n```\n````\n- Do not wrap it in `<memory-citation>` XML tags; the fenced form replaces\n  that older format.\n- Citation entry lines are for rendering:\n  - one citation entry per line\n  - format: `<file>:<line_start>-<line_end>|note=<how memory was used>`\n  - use file paths relative to the memory base path (for example, `MEMORY.md`,\n    `rollout_summaries/...`, `skills/...`)\n  - only cite files actually used under the memory base path (do not cite\n    workspace files as memory citations)\n  - if you used `MEMORY.md` and then a rollout summary/skill file, cite both\n  - list entries in order of importance (most important first)\n  - `note` should be short, single-line, and use simple characters only (avoid\n    unusual symbols, no newlines)\n- The final `sessions:` line is for us to track which past sessions you find\n  useful:\n  - one line, space-separated session ids after `sessions:`\n  - session ids look like `ses_...` and appear in rollout summary files and\n    MEMORY.md as `session_id:`\n  - include unique ids only; do not repeat ids\n  - omit the `sessions:` line if no session ids are available\n  - do not include file paths or notes on this line\n  - for every citation entry, try to find and cite the corresponding session id\n- Never include memory citations inside pull-request messages.\n- Never cite blank lines; double-check ranges.\n\n";
 export declare function overlayV2CitationInstructions(prompt: string): string;

package/dist/src/v2/citation-overlay.js

@@ -7,10 +7,15 @@ export const V2_CITATION_INSTRUCTIONS = `Memory citation requirements:
 
 - If ANY relevant memory files were used: append exactly one fenced code
   block with the language tag \`memory-citation\` as the VERY LAST content of
-  the final reply. Normal responses should include the answer first, then
-  append the block at the end. The host renders this block natively.
-- Use this exact structure for programmatic parsing:
+  the final reply. Answer first, then a blank line, then the block. The
+  opening fence must be on its own line at column 0 — never glue it to the
+  last sentence, or markdown clients treat the block as paragraph text and
+  collapse its newlines. The host renders this block natively.
+- Use this exact structure for programmatic parsing (blank line before the
+  fence is required):
 \`\`\`\`
+answer text ends here.
+
 \`\`\`memory-citation
 MEMORY.md:234-236|note=build command for the api service
 rollout_summaries/2026-02-17T21-23-02-ln3m-example.md:10-12|note=weekly report format

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-codex-memory",
-  "version": "0.7.5",
+  "version": "0.7.6",
   "description": "Persistent memory plugin for opencode — ports codex's two-phase memory system (extraction → consolidation → injection → citation feedback)",
   "type": "module",
   "main": "./dist/src/index.js",