memorix 1.7.3 → 1.8.1

package/docs/1.2.4-PERSISTENT-MEMORY-DELIVERY.md

@@ -26,7 +26,7 @@ database, a transcript archive, or another default MCP tool.
 | Start a new, unrelated task | A bounded task Workset. No automatic prior-session text. |
 | Continue or take over prior work | The same Workset plus a bounded prior-work projection. |
 | MCP is available | Use the existing `memorix_project_context` tool with the real task. |
-| MCP is unavailable | Make one CLI call: `memorix resume "<task>" --brief-json` for continuation or `memorix context "<task>" --brief-json` for a new task. `--json` remains the detailed diagnostic form. |
+| MCP is unavailable | Make one CLI fallback call: `memorix resume "<task>" --fallback --brief-json` for continuation or `memorix context "<task>" --fallback --brief-json` for a new task. The fallback budget rejects repeated probes; `--json` remains the detailed diagnostic form. |
 | Claude Code hook is installed | An explicit continuation prompt receives the same bounded prior-work Workset through the official `UserPromptSubmit` context channel, unless `memory.inject = "silent"`. |
 | Read-only assessment | The brief may be read, but Memorix does not persist a new observation unless the user explicitly asks to save one. |
 | Need a deliberate session handoff | Keep using the explicit session/handoff surfaces; this projection does not replace them. |

package/docs/1.8.0-RELEASE-CANDIDATE-SPEC.md

@@ -0,0 +1,75 @@
+# Memorix 1.8.0 Release Candidate Specification
+
+Status: accepted implementation contract for Memorix 1.8.0.
+
+## Acceptance Checklist
+
+- [x] Keep one canonical release document and update the documentation map.
+- [x] Expose MCP protocol diagnostics without changing existing defaults.
+- [x] Preserve legacy stateful Streamable HTTP and stdio clients.
+- [x] Return bounded evidence cards from persisted project graph state.
+- [x] Provide a deterministic memory feedback reducer, SQLite event persistence,
+  auditable MCP/CLI adapters, and a unified retrieval/retention projection.
+- [x] Keep the default MCP profile compact and preserve the full profile contract.
+- [x] Provide dashboard evidence/provenance views without replacing the existing UI.
+- [x] Preserve explicit project/session handles across restart and client shapes.
+- [x] Verify CLI fallback, Windows child-process hiding, HTTP old/new smoke, build, and package contents.
+
+## Compatibility Contract
+
+The MCP 2026-07-28 protocol is the external stateless request contract.
+Memorix also accepts the legacy stateful Streamable HTTP contract with
+`Mcp-Session-Id`. Stateless requests carry an explicit `Mcp-Project-Handle`
+that is persisted in SQLite and survives service restart; the handle, rather
+than a transport session id, owns project routing. The pinned SDK's accepted
+wire version is normalized internally at the HTTP boundary, while responses
+continue to advertise current protocol metadata. Unsupported Tasks/polling is
+reported by capability diagnostics rather than simulated.
+
+Antigravity is the primary setup target. Gemini CLI remains a compatibility and
+migration path. GitHub issue #204 (WorkBuddy) is intentionally not merged or
+used as release evidence.
+
+## Evidence Architecture
+
+Consumers are both humans and agents. Markdown remains the human source of
+truth; SQLite graph records and bounded evidence cards are the agent index.
+Retrieval is hybrid/graph-assisted, but never a full graph dump. Supported
+relations are persisted through the existing graph store and may reference
+files, symbols, calls/imports, tests, scripts, commits, dependencies,
+failures, memory, and source. Non-TypeScript/JavaScript projects use the
+existing graceful fallback and report coverage honestly.
+
+## Memory Feedback Contract
+
+The lifecycle is capture -> qualify -> recall -> use -> feedback ->
+strengthen/weaken -> archive/forget. Feedback is auditable and deterministic.
+Supported signals are user correction, verification success/failure, code
+change, use/non-use, and conflict with current code. Positive feedback raises
+retrieval weight; negative or conflicting feedback lowers it and can make a
+record eligible for archive. Recovery is explicit and auditable.
+
+The 1.8.0 release ships the reducer, durable state/event tables, MCP and CLI
+surfaces, revoke events, and tests for these rules. A legacy record without a
+feedback event keeps its historical retrieval/retention score; the first
+explicit feedback event opts it into the feedback projection.
+
+## Evidence and Operator Surface
+
+Every observation write creates or refreshes a project-scoped evidence card with
+source kind, source reference, locator, captured hash, files, and freshness.
+Changed paths can mark cards stale without deleting their source memory. The
+`memorix_evidence` MCP tool, `memorix evidence` CLI command, and Dashboard
+Evidence page expose the same persisted cards and audit events.
+
+When MCP discovery is unavailable, `memorix context --fallback` uses a durable
+one-shot budget keyed by project and task. Repeated help/search/status probing
+is rejected for that task window.
+
+## Explicit Non-goals for 1.8.0
+
+- No fake MCP Tasks/polling implementation when the pinned SDK does not expose
+  a durable server-side task contract.
+- No remote memory hub, proxying of model traffic, or upstream installer.
+- No claim that the bundled Lite parser is a semantic CodeGraph.
+- No marketing landing page in place of an operator evidence console.

package/docs/API_REFERENCE.md

@@ -103,7 +103,7 @@ memorix context "continue auth bug"
 memorix resume "continue auth bug"
 memorix checkpoint list
 memorix checkpoint context --task "continue auth bug"
-memorix context --task "prepare 1.1.7 release"
+  memorix context --task "prepare 1.8.0 release"
 memorix explain
 memorix codegraph context-pack --task "continue auth bug"
 ```
@@ -123,6 +123,42 @@ SessionStart hooks keep the default minimal hint lightweight. When memory behavi
 
 The intended loop for agents is: get the project brief when it helps, inspect the suggested current files, use stale or unbound memory only as a lead, store durable outcomes after the work changes the project, and resolve obsolete memories.
 
+### Evidence Cards and Feedback
+
+Evidence Cards are the persisted provenance index for project memory. They do
+not replace the observation, source file, commit, or test they point to. Every
+observation write creates or refreshes a card with `sourceRef`, `locator`,
+`capturedHash`, project ownership, files, verification state, and freshness.
+
+CLI:
+
+```bash
+memorix evidence list --json
+memorix evidence get --id 42 --json
+memorix evidence stale --paths src/server.ts,tests/server.test.ts --json
+memorix feedback record --id 42 --signal verification-success --source test:run-1 --json
+memorix feedback audit --id 42 --json
+```
+
+MCP uses `memorix_evidence` for `list`, `get`, `sync`, `stale`, and `events`,
+and `memorix_feedback` for `record`, `show`, and `audit`. Feedback events are
+append-only; `revoke` points at the event being undone, so the audit history is
+preserved. A memory without explicit feedback keeps the legacy relevance and
+retention score. The first feedback event opts that candidate into the
+feedback projection.
+
+### HTTP MCP Compatibility
+
+Legacy clients use stateful Streamable HTTP with `Mcp-Session-Id`. Current
+stateless clients send `Mcp-Protocol-Version: 2026-07-28` and receive a durable
+`Mcp-Project-Handle`. Send that handle on subsequent requests; it is persisted
+in SQLite and remains valid across service restart until its TTL expires.
+`/protocol-diagnostics` reports the current/legacy contract and explicitly
+reports Tasks and polling as unsupported when the pinned SDK cannot provide a
+durable implementation. When MCP discovery is unavailable, use one bounded
+`memorix context --fallback` request for a task; repeated fallback probing is
+rejected by the local budget.
+
 The built-in Lite provider indexes common code files with lightweight file, symbol, and import facts. It is a structural fallback, not a language-server-quality graph. When a project already has a healthy local CodeGraph index, `[codegraph].external_context = "auto"` may add a validated, bounded semantic outline to the Workset. Memorix never initializes, syncs, or exports that external index, and never stores its raw source output. `memorix codegraph status --json`, `memorix doctor --json`, and Project Context JSON identify the actual provider quality.
 
 ### Knowledge Workspace and Workflows
@@ -828,6 +864,8 @@ Important inputs:
 
 When using HTTP mode, the main dashboard is usually served from the same port as `serve-http`.
 
+The Dashboard's Coordination Status page is read-only. It reads the selected project's agents, tasks, locks, handoffs, messages, and poll state from the persistent SQLite `TeamStore`; it does not expose team/task write endpoints or replace task execution and orchestration tools. A coordination read failure is returned as an explicit degraded/error response rather than an empty healthy snapshot.
+
 ---
 
 ## 12. Optional Graph Compatibility Tools

package/docs/ARCHITECTURE.md

@@ -498,7 +498,9 @@ It provides an operational view for:
 - sessions
 - retention state
 - preview-first cleanup, consolidation, intelligent deduplication, and retention archival
-- read-only orchestration coordination state in the standalone dashboard and live state in HTTP service mode
+- read-only Coordination Status derived from the project-scoped SQLite `TeamStore`; the page is a projection, not a task execution surface
+
+`TeamStore` is the real persistent coordination layer for agents, tasks, messages, locks, handoffs, and poll state. Dashboard coordination reads use that same SQLite state and return an explicit degraded/error status when it cannot be read; they must not substitute a normal-looking empty snapshot.
 
 Dashboard maintenance is not a separate business-logic implementation. CLI, MCP, background jobs, and Dashboard routes share the same cleanup, consolidation, deduplication, and retention functions. Mutation routes issue a project-bound signed preview token and reject execution when the candidate set changed after preview.
 

package/docs/DASHBOARD.md

@@ -2,6 +2,11 @@
 
 The Memorix Dashboard is the local control surface for inspecting project memory and running explicit maintenance. It is available through the shared background service or as a standalone local process.
 
+The 1.8.0 Evidence page is the operator view of the same source-backed cards
+used by MCP and CLI. It shows each card's source reference, locator, captured
+hash, freshness, verification state, and audit-event count. It is project
+scoped and does not replace the underlying observation or code source.
+
 ## Start
 
 ```bash
@@ -14,6 +19,12 @@ memorix dashboard
 
 Both modes read the same project-scoped stores. The project switcher changes the active project filter; it does not merge projects or grant access to personal memories.
 
+## Coordination Status
+
+The Coordination Status page is a read-only projection of the selected project's persistent coordination state. `TeamStore` is the canonical SQLite layer for agents, tasks, messages, locks, handoffs, and poll state; the Dashboard does not keep a second in-memory coordination registry.
+
+The page reports agents, task status, file locks, and handoffs for the selected project. It exposes no team or task write endpoints and is not a task execution or full orchestration platform. If the SQLite read fails, the API returns an explicit degraded/error status and the page shows that the status is unavailable instead of presenting an empty result as healthy.
+
 ## Maintenance Workbench
 
 The Observations page exposes three explicit maintenance actions:
@@ -52,3 +63,8 @@ POST /api/maintenance/retention/execute
 ```
 
 Use the CLI for scripts and remote terminals. Use MCP for agent-driven maintenance. The Dashboard is the reviewable local operator surface; all three call the same maintenance logic.
+
+The control-plane API also exposes `GET /api/evidence?project=<id>` for the
+bounded Evidence Console payload. The page is responsive at desktop, tablet,
+and narrow mobile widths; long paths wrap instead of widening the viewport,
+and maintenance dialogs remain viewport-centered.

package/docs/DEVELOPMENT.md

@@ -13,8 +13,8 @@ Memorix is a TypeScript project built around:
 
 ## Current Development Baseline
 
-The current release work targets the **1.7 line** while package metadata may
-still show the last published version until the release commit is cut.
+The current release work targets the **1.8.1 release line** and package metadata
+is kept at `1.8.1` for this release commit.
 
 Contributors should assume the following areas are part of the current release line:
 
@@ -29,6 +29,7 @@ Contributors should assume the following areas are part of the current release l
 - the existing layered retrieval, retention, attribution, and compact output model
 - source-backed long-term memory with candidate, qualification, approval, archival, supersession, and explicit portable user scope
 - preview-first project maintenance shared across Dashboard, CLI, and MCP
+- persisted Evidence Cards, feedback audit events, and stateless MCP project handles
 - the reproducible large-store gate for SDK, HTTP MCP, hooks, persistence, and
   cold-start retrieval budgets
 

package/docs/INTEGRATIONS.md

@@ -61,7 +61,7 @@ Generated guidance also has scope:
 | Pi | `memorix setup --agent pi --global` | Pi package | User Pi package with extension and official skills, registered through `pi install <path> --approve` | Run without `--global` only when you want a project-local Pi package. Pi currently does not need a separate Memorix MCP config lane. |
 | Windsurf | `memorix setup --agent windsurf --global` | Windsurf MCP/rules/hooks config | stdio MCP config, `.windsurf/rules/memorix.md`, hook config | Uses Windsurf's current config surfaces. |
 | Kiro | `memorix setup --agent kiro --global` | Kiro MCP/steering/hooks config | MCP config, `.kiro/steering/memorix.md`, `.kiro/hooks/*.kiro.hook` | Uses Kiro steering and hook files. |
-| Antigravity | `memorix setup --agent antigravity --global` | Antigravity plugin | Plugin under `~/.gemini/config/plugins/memorix` or `.agents/plugins/memorix`, with `plugin.json`, `mcp_config.json`, `hooks.json`, rules, and skills | Uses Antigravity's official plugin layout. Dedicated MCP configs live at `~/.gemini/config/mcp_config.json` or `.agents/mcp_config.json`; legacy Gemini settings are read only for compatibility. |
+| Antigravity | `memorix setup --agent antigravity --global` | **Primary supported target** | Plugin under `~/.gemini/config/plugins/memorix` or `.agents/plugins/memorix`, with `plugin.json`, `mcp_config.json`, `hooks.json`, rules, and skills | Uses Antigravity's official plugin layout. Dedicated MCP configs live at `~/.gemini/config/mcp_config.json` or `.agents/mcp_config.json`; legacy Gemini settings are read only for compatibility. |
 | Trae | `memorix setup --agent trae --global` | Trae MCP/rules config | MCP config and `.trae/rules/project_rules.md` | Current support is MCP plus project rules. |
 | DeepSeek Harness | `memorix setup --agent dsh --global` | DeepSeek Harness MCP patch | Memorix `@deepseek-ai/dsh-mcp-client` row in `$DSH_HOME/cordis.patch.yml` (default `~/.dsh/cordis.patch.yml`), guidance in the harness `AGENTS.md`, and official skills under `$DSH_HOME/skills` | Tools appear as `mcp__memorix__*`. No hooks surface. Project-local setup writes project `AGENTS.md` guidance and `.dsh/skills`; the MCP row always lives in the harness-level patch file. |
 | memcode | `memorix` or `memcode` | Bundled terminal agent | Built-in Memorix memory access | memcode uses the same project memory pool; it is not a separate memory silo. |

package/docs/README.md

@@ -33,10 +33,11 @@ The public docs are organized by user intent:
 | CLI commands and MCP tools | [API_REFERENCE.md](API_REFERENCE.md) |
 | Memory Autopilot, Code State, and context packs | [API_REFERENCE.md § Memory Autopilot, Code State, and Context Packs](API_REFERENCE.md#memory-autopilot-code-state-and-context-packs), [1.2 Code State](1.2.0-CODE-STATE.md), and [1.2 Workset Retrieval](1.2.0-WORKSET-RETRIEVAL.md) |
 | Reviewed episodic, semantic, and procedural long-term memory | [1.3 Memory Architecture](1.3-MEMORY-ARCHITECTURE.md) |
-| Browse memory and run preview-first local maintenance | [Dashboard](DASHBOARD.md) |
+| Browse memory, maintenance, and read-only Coordination Status | [Dashboard](DASHBOARD.md) |
 | Reviewable knowledge pages and workflow inheritance | [API_REFERENCE.md § Knowledge Workspace and Workflows](API_REFERENCE.md#knowledge-workspace-and-workflows), [1.2 Knowledge Workspace](1.2.0-KNOWLEDGE-WORKSPACE.md), and [1.2 Workflow Inheritance](1.2.0-WORKFLOW-INHERITANCE.md) |
 | Git-derived engineering memory | [GIT_MEMORY.md](GIT_MEMORY.md) |
 | Memory formation and quality pipeline | [MEMORY_FORMATION_PIPELINE.md](MEMORY_FORMATION_PIPELINE.md) |
+| Evidence cards and memory feedback | [1.8.0 Release Specification](1.8.0-RELEASE-CANDIDATE-SPEC.md) and [API_REFERENCE.md](API_REFERENCE.md) |
 | Performance and resource profile | [PERFORMANCE.md](PERFORMANCE.md) |
 | Orchestrated subagent tasks, messages, locks, handoffs | [API_REFERENCE.md § Orchestration Coordination](API_REFERENCE.md#9-orchestration-coordination-tools) |
 | Subagent orchestration | [API_REFERENCE.md](API_REFERENCE.md) and `memorix orchestrate --help` |
@@ -92,6 +93,7 @@ The public docs are organized by user intent:
 | 1.2 honest Lite and optional semantic CodeGraph provider contract | [1.2 Provider Quality](1.2.0-PROVIDER-QUALITY.md) |
 | 1.3 long-term memory model, source boundary, and lifecycle | [1.3 Memory Architecture](1.3-MEMORY-ARCHITECTURE.md) |
 | Active context-control work | [1.2.2 Memory Control Plane](1.2.2-MEMORY-CONTROL-PLANE.md) |
+| 1.8 context-control acceptance contract | [1.8.0 Release Specification](1.8.0-RELEASE-CANDIDATE-SPEC.md) |
 | Historical cloud sync and multi-agent research | [CLOUD_SYNC_AND_MULTI_AGENT_RESEARCH.md](CLOUD_SYNC_AND_MULTI_AGENT_RESEARCH.md) |
 | Known issues and old roadmap notes | [KNOWN_ISSUES_AND_ROADMAP.md](KNOWN_ISSUES_AND_ROADMAP.md) |
 
@@ -119,16 +121,27 @@ Historical/deep-reference documents may describe older designs. If they conflict
 
 ## Current Product Line
 
-The released product is on the **1.7 line**. The current baseline has:
+The current product line is **1.8.1**. The authoritative acceptance contract is
+[1.8.0 Release Specification](1.8.0-RELEASE-CANDIDATE-SPEC.md).
+The current baseline has:
 
 - `memorix setup --agent <agent> --global` is the default agent integration command
 - `memorix serve` is the manual stdio MCP server for external agents
 - `memorix background start` runs the shared HTTP MCP service and dashboard
 - Dashboard maintenance is preview-first, project-scoped, and uses the same
   cleanup and deduplication planners as CLI and MCP
+- Dashboard Coordination Status is read-only and projects the persistent SQLite
+  `TeamStore` truth; its task section is `Task Status` and failed reads are
+  explicit `error`/`degraded` states
 - context and CodeGraph commands return bounded task receipts before detailed diagnostics
 - HTTP MCP sessions have a bounded, explicit lifecycle and fail with a reinitialize hint after expiry
 - `memorix integrate --agent <agent>` and `memorix hooks install --agent <agent>` remain manual/fallback generation commands
 - `memorix` / `memcode` open memcode, the bundled terminal agent that uses the same Memorix memory pool
 - `~/.memorix/config.toml` and project `memorix.toml` are the user-facing configuration model
 - legacy `memorix.yml`, `.env`, and `config.json` files are still read for compatibility, but new setups should use TOML
+
+For MCP compatibility, 1.8 preserves legacy stateful Streamable HTTP and
+supports 2026-07-28 stateless requests with durable project handles. Tasks and
+polling are reported as unsupported when the pinned SDK cannot provide a real
+durable implementation. Antigravity is the primary setup target; Gemini CLI is
+the compatibility path. See the release specification for the exact contract.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "memorix",
   "mcpName": "io.github.AVIDS2/memorix",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "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/antigravity/memorix/rules/memorix.md

@@ -3,7 +3,7 @@
 Use Memorix when prior workspace context, decisions, fixes, or handoff state would materially help the current task and Memorix tools are available.
 
 - Call `memorix_project_context` with the user's actual task for continuation, fresh handoff, or unfamiliar coding work so Memorix can choose a task-lensed brief.
-- If the MCP tool is not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text.
+- If the MCP tool is not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text.
 - Use `memorix_context_pack` when you need structured refs and freshness for code-bound memories.
 - Use `memorix_graph_context` for explicit memory graph questions.
 - Use `memorix_search` for focused lookup.

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

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "memorix",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "description": "Shared workspace memory for Claude Code and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/claude/memorix/SKILL.md

@@ -32,7 +32,7 @@ is not a failure by itself. Claude Code supports MCP tool search, and the
 Memorix Claude plugin asks Claude to eagerly load its small core tool set. In
 headless/print-mode, if Memorix tools are not in the first visible tool list,
 search/select `memorix_project_context` before using shell fallback. Run
-`memorix context --task "<task>"` only after MCP is unavailable, disabled, or
+`memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or
 not discoverable, and pass the user's real task text.
 
 Do not store secrets, credentials, raw private transcripts, or trivial one-off actions. Treat memory as context, not as a substitute for reading code and verifying behavior.

package/plugins/claude/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
@@ -28,7 +28,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If Claude Code print-mode shows Memorix MCP as pending and the tools are not visible yet, first use Claude Code's MCP tool search/dynamic loading to find `memorix_project_context`. Run `memorix context --task "<task>"` from the shell only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on `pending`, or hand-write tool-call syntax.
+- If Claude Code print-mode shows Memorix MCP as pending and the tools are not visible yet, first use Claude Code's MCP tool search/dynamic loading to find `memorix_project_context`. Run `memorix context --task "<task>" --fallback --brief-json` from the shell only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on `pending`, or hand-write tool-call syntax.
 
 ## Store Rules
 

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

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "description": "Local-first project memory for CodeBuddy Code and other coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/codebuddy/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
 | Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |
@@ -28,7 +28,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If Claude Code print-mode shows Memorix MCP as pending and the tools are not visible yet, first use Claude Code's MCP tool search/dynamic loading to find `memorix_project_context`. Run `memorix context --task "<task>"` from the shell only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on `pending`, or hand-write tool-call syntax.
+- If Claude Code print-mode shows Memorix MCP as pending and the tools are not visible yet, first use Claude Code's MCP tool search/dynamic loading to find `memorix_project_context`. Run `memorix context --task "<task>" --fallback --brief-json` from the shell only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on `pending`, or hand-write tool-call syntax.
 
 ## Store Rules
 

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

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

package/plugins/codex/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
@@ -29,7 +29,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
+- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
 
 ## Store Rules
 

package/plugins/copilot/memorix/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "description": "Shared local workspace memory for GitHub Copilot CLI and other AI coding agents.",
   "author": {
     "name": "AVIDS2",

package/plugins/copilot/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
@@ -29,7 +29,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
+- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
 
 ## Store Rules
 

package/plugins/cursor/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
@@ -29,7 +29,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
+- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
 
 ## Store Rules
 

package/plugins/gemini/memorix/GEMINI.md

@@ -5,7 +5,7 @@ This extension adds Memorix memory guidance for the active Gemini CLI workspace.
 Use Memorix when prior workspace context, decisions, fixes, or handoff state would materially help the current task and Memorix tools are available.
 
 - Call `memorix_project_context` with the user's actual task for continuation, fresh handoff, or unfamiliar coding work so Memorix can choose a task-lensed brief.
-- If the MCP tool is not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text.
+- If the MCP tool is not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text.
 - Use `memorix_context_pack` when you need structured refs and freshness for code-bound memories.
 - Use `memorix_graph_context` for explicit memory graph questions.
 - Use `memorix_search` for focused lookup.

package/plugins/gemini/memorix/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "mcpServers": {
     "memorix": {
       "command": "memorix",

package/plugins/omp/memorix/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix-omp-package",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "description": "Memorix shared workspace memory package for Oh-my-Pi.",
   "license": "Apache-2.0",
   "keywords": [

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

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

package/plugins/pi/memorix/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memorix-pi-package",
-  "version": "1.7.3",
+  "version": "1.8.1",
   "description": "Memorix shared workspace memory package for Pi coding agent.",
   "license": "Apache-2.0",
   "keywords": [

package/plugins/pi/memorix/skills/memorix-memory/SKILL.md

@@ -11,7 +11,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 
 | Situation | Prefer | CLI fallback |
 |---|---|---|
-| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>"` |
+| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |
 | Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |
 | Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` |
 | Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |
@@ -29,7 +29,7 @@ Use Memorix as the shared memory layer for the active workspace when Memorix too
 - Treat memory as background context. Still read the current code and verify behavior.
 - Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
 - If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
-- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>"` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
+- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
 
 ## Store Rules
 

package/server.json

@@ -7,7 +7,7 @@
     "url": "https://github.com/AVIDS2/memorix",
     "source": "github"
   },
-  "version": "1.7.3",
+  "version": "1.8.1",
   "websiteUrl": "https://github.com/AVIDS2/memorix#readme",
   "icons": [
     {
@@ -22,7 +22,7 @@
     {
       "registryType": "npm",
       "identifier": "memorix",
-      "version": "1.7.3",
+      "version": "1.8.1",
       "runtimeHint": "npx",
       "packageArguments": [
         {

package/src/cli/capability-map.ts

@@ -19,6 +19,8 @@ export const CLI_NATIVE_PARITY: Record<string, string> = Object.freeze({
   memorix_transfer: 'memorix transfer export|import',
   memorix_retention: 'memorix retention status|archive|stale',
   memorix_media: 'memorix media import|attach|list|show|generate|status',
+  memorix_evidence: 'memorix evidence list|get|sync|stale|events',
+  memorix_feedback: 'memorix feedback record|show|audit',
   memorix_dashboard: 'memorix dashboard',
   memorix_handoff: 'memorix handoff send',
   memorix_poll: 'memorix poll',

package/src/cli/commands/context.ts

@@ -11,6 +11,7 @@ import { buildBoundedContextReceipt } from '../../knowledge/context-receipt.js';
 import { WORKFLOW_AGENT_TARGETS } from '../../knowledge/workflows.js';
 import type { AgentTarget } from '../../types.js';
 import { emitError, emitResult, getCliProjectContext } from './operator-shared.js';
+import { CliFallbackBudget } from '../fallback-budget.js';
 
 function coerceRefreshMode(input?: string): AutoContextRefreshMode {
   const value = (input ?? 'auto').trim().toLowerCase();
@@ -42,6 +43,7 @@ export default defineCommand({
     agent: { type: 'string', description: 'Optional target agent for compatible workflow selection' },
     json: { type: 'boolean', description: 'Emit machine-readable JSON output' },
     briefJson: { type: 'boolean', description: 'Emit only the bounded agent brief and receipt JSON' },
+    fallback: { type: 'boolean', description: 'Mark this as the one-shot MCP-unavailable fallback for the task' },
   },
   run: async ({ args }) => {
     const asJson = !!args.json || !!args.briefJson;
@@ -51,6 +53,15 @@ export default defineCommand({
 
     try {
       const { project, dataDir, reader } = await getCliProjectContext();
+      if (args.fallback) {
+        const budget = new CliFallbackBudget();
+        await budget.init(dataDir);
+        const claim = budget.claim(project.id, task);
+        if (!claim.allowed) {
+          emitError(claim.reason ?? 'CLI fallback budget exhausted for this task.', asJson);
+          return;
+        }
+      }
       const context = await buildAutoProjectContext({
         project,
         dataDir,

package/src/cli/commands/dashboard.ts

@@ -59,7 +59,7 @@ export default defineCommand({
         const cliDir = path.dirname(fileURLToPath(import.meta.url));
         const staticDir = path.join(cliDir, '..', 'dashboard', 'static');
 
-        await startDashboard(dataDir, port, staticDir, project.id, project.name, true, undefined, project.rootPath, true);
+        await startDashboard(dataDir, port, staticDir, project.id, project.name, true, project.rootPath, true);
 
         // Keep alive
         await new Promise(() => { });