memorix 1.1.12 → 1.1.13

package/dist/index.js

@@ -21884,7 +21884,7 @@ The path should point to a directory containing a .git folder.`
   };
   const server = existingServer ?? new McpServer({
     name: "memorix",
-    version: true ? "1.1.12" : "1.0.1"
+    version: true ? "1.1.13" : "1.0.1"
   });
   const originalRegisterTool = server.registerTool.bind(server);
   server.registerTool = ((name, ...args) => {

package/dist/memcode-runtime/CHANGELOG.md

@@ -4,6 +4,15 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.1.13] - 2026-07-17
+
+### Added
+- **Codex installation proof** -- `memorix doctor agents --agent codex --scope global` now checks the local plugin bundle, Personal marketplace entry, five declared and trusted lifecycle hooks, and the installed/enabled state reported by `codex plugin list`.
+
+### Fixed
+- **Codex plugin version drift** -- Global setup now stamps the copied Codex plugin manifest with the installed Memorix version, so Codex no longer reports the old template version after an upgrade. The source template is covered by a release regression test as well.
+- **Workspace package publish trap** -- `@memorix/ai`, `@memorix/agent-core`, `@memorix/tui`, and `@memorix/memcode` are now explicitly internal workspaces. The root `memorix` package ships their bundled runtime, and the release workflow publishes only that supported public package.
+
 ## [1.1.12] - 2026-07-17
 
 ### Added

package/dist/memcode-runtime/package.json

@@ -1,6 +1,7 @@
 {
 	"name": "@memorix/memcode",
 	"version": "1.1.12",
+	"private": true,
 	"description": "Memorix-native coding agent CLI with terminal chat, project memory, hooks, and session management",
 	"type": "module",
 	"piConfig": {

package/dist/sdk.js

@@ -21799,7 +21799,7 @@ The path should point to a directory containing a .git folder.`
   };
   const server = existingServer ?? new McpServer({
     name: "memorix",
-    version: true ? "1.1.12" : "1.0.1"
+    version: true ? "1.1.13" : "1.0.1"
   });
   const originalRegisterTool = server.registerTool.bind(server);
   server.registerTool = ((name, ...args) => {

package/docs/AGENT_OPERATOR_PLAYBOOK.md

@@ -661,7 +661,7 @@ If it reports stale MCP command paths, missing `memorix` MCP entries, missing Cl
 memorix repair agents --agent <agent>
 ```
 
-Repair only rewrites Memorix-owned MCP entries and Memorix-owned guidance blocks. It should not edit unrelated user config.
+Repair only rewrites Memorix-owned MCP entries, Memorix-owned guidance blocks, and an explicitly targeted Codex Memorix plugin bundle. It does not edit unrelated user config or turn on a user-disabled Codex plugin; enable that one from `/plugins`.
 
 ### 1. Is the workspace a Git repo?
 

package/docs/DEVELOPMENT.md

@@ -300,32 +300,25 @@ is intentional after reviewing the diff, rerun with
 - dashboard
 - Git Memory
 - config diagnostics
+- `memorix setup --agent codex --global` followed by `memorix doctor agents --agent codex --scope global --json` in an isolated home, when changing the Codex integration
 
 4. inspect package contents:
 
 ```bash
 npm pack --dry-run --json
-npm pack --workspace @memorix/ai --dry-run --json
-npm pack --workspace @memorix/agent-core --dry-run --json
-npm pack --workspace @memorix/tui --dry-run --json
-npm pack --workspace @memorix/memcode --dry-run --json
 ```
 
 5. commit and push
-6. publish manually when ready, in dependency order:
+6. publish the supported public package manually when ready:
 
 ```bash
-npm publish --workspace @memorix/ai --access public
-npm publish --workspace @memorix/agent-core --access public
-npm publish --workspace @memorix/tui --access public
-npm publish --workspace @memorix/memcode --access public
 npm publish --access public
 ```
 
 Notes:
 
 - `prepublishOnly` runs build + test, but does not contact live model catalog APIs
-- `memorix` depends on `@memorix/memcode`; `@memorix/memcode` depends on `@memorix/ai`, `@memorix/agent-core`, and `@memorix/tui`, so publish workspaces before the root package
+- `@memorix/ai`, `@memorix/agent-core`, `@memorix/tui`, and `@memorix/memcode` are internal workspaces. Their code is bundled into the root `memorix` distribution and they must stay `private` unless the project deliberately establishes an owned npm scope and a separate package-support contract.
 - npm publish is usually manual, especially when 2FA is enabled
 - GitHub release automation should not be treated as a substitute for manual runtime validation
 

package/docs/INTEGRATIONS.md

@@ -49,7 +49,7 @@ Generated guidance also has scope:
 | Agent | Recommended install | Official entry | What gets installed | Notes |
 | --- | --- | --- | --- | --- |
 | Claude Code | `memorix setup --agent claude --global` | Claude Code plugin marketplace | Local `memorix-local` marketplace, plugin-bundled stdio MCP, skills, hooks, plus `CLAUDE.md` guidance | Setup attempts `claude plugin marketplace add` and `claude plugin install memorix@memorix-local`. |
-| Codex | `memorix setup --agent codex --global` | Codex Personal marketplace plugin | Local plugin under `~/.codex/plugins/memorix`, Personal marketplace entry, plugin-bundled stdio MCP, skills, hooks, plus `AGENTS.md` guidance | Setup attempts `codex plugin add memorix@personal`. The plugin uses Codex `SessionStart`, `UserPromptSubmit`, `PostToolUse`, `PreCompact`, and `Stop` hooks; review it once in `/hooks` when Codex requests trust. |
+| Codex | `memorix setup --agent codex --global` | Codex Personal marketplace plugin | Local plugin under `~/.codex/plugins/memorix`, Personal marketplace entry, plugin-bundled stdio MCP, skills, hooks, plus `AGENTS.md` guidance | Setup attempts `codex plugin add memorix@personal`. Run `memorix doctor agents --agent codex --scope global` to verify the bundle, marketplace, enabled state, and five declared/trusted hooks; start a new thread after setup. |
 | GitHub Copilot CLI | `memorix setup --agent copilot --global` | Copilot CLI plugin package | Local plugin under `~/.copilot/plugins/local/memorix` with MCP, skills, and hooks | Setup attempts `copilot plugin install <local-path>` when Copilot CLI is available. |
 | Cursor | `memorix setup --agent cursor --global` | Cursor MCP and rules config | Cursor MCP config, `.cursor/rules/memorix.mdc`, skills, and hook guidance | Reload Cursor after setup so it can pick up project config changes. |
 | Gemini CLI | `memorix setup --agent gemini-cli --global` | Gemini CLI extension | Extension under `~/.gemini/extensions/memorix` with MCP, `GEMINI.md` context, hooks, commands, and skills | Antigravity CLI has an official Gemini CLI migration path, but Gemini CLI remains an active standalone Google CLI target. |

package/docs/SETUP.md

@@ -132,7 +132,9 @@ memorix doctor agents --agent <agent>
 memorix repair agents --agent <agent>
 ```
 
-The doctor checks Memorix-owned MCP entries and guidance files for stale command paths, missing `memorix` MCP servers, missing Claude `alwaysLoad`, and outdated Memory Autopilot rules.
+The doctor checks Memorix-owned MCP entries and guidance files for stale command paths, missing `memorix` MCP servers, missing Claude `alwaysLoad`, and outdated Memory Autopilot rules. For `codex --scope global`, it also checks the local plugin bundle, Personal marketplace entry, five declared lifecycle hooks, Codex's trusted hook state, and the installed/enabled state reported by `codex plugin list`.
+
+After Codex setup, start a new thread so enabled plugins can load. Codex does not expose a command that proves hooks are already active inside the current thread. If doctor reports `codex-plugin-disabled`, open `/plugins` and turn Memorix on there; repair does not toggle a user-disabled plugin.
 
 ### Option B: manual stdio MCP
 

package/docs/dev-log/progress.txt

@@ -4,71 +4,43 @@
 > older notes when they conflict.
 
 ## Current State
-- Phase: 1.1.12 ready to publish
-- Branch: `codex/1.1.12-runtime-hygiene`
+- Phase: 1.1.13 ready to publish
+- Branch: `codex/1.1.13-release-contract`
 - Last updated: 2026-07-17
-- Goal: ship the verified Codex lifecycle hooks, repair OpenCode Windows hook
-  delivery, and preserve semantic vector recall without blocking MCP startup.
+- Goal: make Codex global setup diagnosable end to end, remove the accidental
+  workspace publish lane, restore the Star History chart, then publish a clean
+  1.1.13 before beginning 1.2 work.
 
 ## Completed Recently
-- Released `memorix@1.1.11`, tagged `v1.1.11`, with durable maintenance,
-  bounded lifecycle work, incremental Code Memory, and first-turn SQLite
-  readiness.
-- Added Codex plugin lifecycle hooks for `SessionStart`, `UserPromptSubmit`,
-  `PostToolUse`, `PreCompact`, and `Stop`, including native SessionStart
-  context injection, quiet capture events, Windows command overrides, and
-  compact-session startup coverage.
-- Confirmed issue #124's project-context timeout fix with the reporter.
-- Triaged issue #125 as an OpenCode Windows PATH resolution failure and
-  reviewed PR #126's semantic vector-recall diagnosis.
-
-## Completed In This Release Candidate
-- OpenCode's generated Windows plugin now embeds the npm `memorix.cmd` shim
-  resolved during setup. It no longer assumes OpenCode inherits the user's
-  npm path, and delivery diagnostics are opt-in through `MEMORIX_HOOK_DEBUG=1`.
-- Project setup no longer writes Claude, Codex, or Copilot plugin bundles into
-  the user home; those bundles require an explicit `--global` installation.
-- API embedding hydration restores compatible local cache entries after lexical
-  readiness. Startup never makes a remote embedding request; cache misses stay
-  in the bounded background lane, and the first successful vector upgrades a
-  cache-less lexical index in the same process. Namespace-scoped cache metadata
-  provides a recovery path when the separate dimensions cache is missing.
-- TUI health, chat, and quick-search paths now use the same lexical-ready
-  initializer, so a first TUI render or search never probes the embedding API.
-- Orama initialization is serialized across cache-only startup and normal
-  callers, preventing a late vector-schema instance from replacing a hydrated
-  lexical index. Resetting the store also invalidates any obsolete in-flight
-  initializer.
-- Cache-only API initialization now avoids parsing the large vector-cache file
-  unless local dimensions metadata proves that cached vectors can be attached.
-- Added regressions for cache hits, cache misses, invalid vectors, stale index
-  changes, delayed cache I/O, concurrent index initialization, schema upgrade
-  after a first vector, and setup scope isolation.
+- Released `memorix@1.1.12`, tagged `v1.1.12`, with native Codex lifecycle
+  hooks, Windows-safe OpenCode hook resolution, scope-isolated setup, and
+  cache-first semantic-vector hydration.
+- `memorix setup --agent codex --global` now stamps the copied plugin manifest
+  with the running Memorix version instead of leaving the template version.
+- `memorix doctor agents --agent codex --scope global` now reports four
+  independently useful facts: the local bundle and declared hook contract, the
+  Personal marketplace entry, Codex's installed/enabled plugin state, and the
+  trusted state for each Codex lifecycle hook.
+- Repair only refreshes Memorix-owned files. A disabled plugin or untrusted
+  hook remains an explicit user action in Codex's plugin/hook UI.
+- `@memorix/ai`, `@memorix/agent-core`, `@memorix/tui`, and
+  `@memorix/memcode` are explicitly internal workspaces. The public release
+  contract is the bundled root `memorix` package.
+- Restored the AVIDS2/memorix Star History chart at the bottom of both READMEs.
 
 ## Verification Snapshot
-- Focused hook/vector tests pass, including a Windows child-process smoke with
-  the npm bin directory removed from the child `PATH`.
-- Full `npm test` passes, along with `npm run lint` and `npm run build` after
-  the final initialization-race and lazy-cache regressions were added.
-- Real stdio MCP smoke with an unreachable API endpoint confirms that an empty
-  cache does not issue a startup embedding probe. A second local API smoke
-  confirms first-vector schema upgrade reaches hybrid search without restart.
-- A cross-process cache smoke deletes the dimensions cache after populating
-  vectors, then verifies offline hybrid retrieval restores from the redundant
-  namespace metadata without another API request.
-- An isolated Windows home smoke confirms project setup leaves the user Codex
-  plugin untouched and `--global` installs the native SessionStart hook.
-- `npm pack --dry-run` succeeds. A clean normal installation of the generated
-  `memorix-1.1.12.tgz` loaded the `better-sqlite3` native binding, completed
-  MCP `initialize` and `tools/list`, and exposed the expected 7-tool micro
-  profile with `memorix_project_context` present.
-
-## Known Boundary
-- Orama remains process-local. Search and stateful write/session tools still
-  wait for full runtime hydration; bootstrap-safe context tools do not.
-- CodeGraph Lite is an incremental local structural map, not a replacement for
-  an AST/language-server intelligence product.
+- Focused Codex setup, hook, doctor, and release-contract regressions pass.
+- `npm run lint`, `npm run build`, and the full serial `npm test` suite pass.
+- `npm pack --dry-run` includes the root runtime, plugin templates, hooks,
+  READMEs, and docs at `memorix@1.1.13`.
+- A clean normal npm installation of the tarball completed a real stdio MCP
+  store/search call against an isolated Git repository and exposed the expected
+  seven-tool micro profile.
+- An isolated real Codex CLI setup installed and enabled `memorix@personal`,
+  stamped the manifest at `1.1.13`, and let doctor verify the bundle,
+  marketplace, runtime state, and pending first-use hook trust separately.
+- The Star History embed uses Star History's current `/image` README endpoint.
 
 ## Next Steps
-- Commit and publish `1.1.12`, then update issue #124, issue #125, and PR #126
-  with the release evidence and credit.
+- Push/merge/tag/publish `v1.1.13`, then create the 1.2 development baseline
+  from the released main branch.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.1.12",
+  "version": "1.1.13",
   "description": "Local-first shared memory layer for AI coding agents across MCP clients, Git history, reasoning context, and project sessions.",
   "type": "module",
   "sideEffects": false,

package/plugins/codex/memorix/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.1.0",
+  "version": "1.1.13",
   "description": "Shared workspace memory for Codex and other AI coding agents.",
   "author": {
     "name": "AVIDS2",