Improve agent-memory evidence and benchmark integrity

.claude-plugin/skill-assets.sha256

@@ -3,4 +3,4 @@ e2e08499a70d8d62ef22797cda0bb07d46cd1c6a79e5e18c1103b6c3c755b6d5  .claude-plugin
 4bc8979b9ffeb97190960e551dbf4ddc6f7aeeb7b86894fd2298a59ff0001efa  skills/engraphis-memory/SKILL.md
 055655db84af07561d002f0c69744313d8413c39f3e873f941f0fa0b1e76dc66  skills/engraphis-memory/references/CONVENTIONS.md
 62019760766ff472a76a0f81437898f39e3c1fe2631732b7b7733e50c1ad837f  skills/engraphis-memory/references/SCOPING.md
-33874c7c7a1c0911b0e73c7d22addc9828963d5436cb315fe7c6c5587c6b911d  skills/engraphis-memory/references/TOOLS.md
+9e5f1c8e91ca5697e828ab9e468504b8e1aa28e34f61307c9fcd850969126be9  skills/engraphis-memory/references/TOOLS.md

.github/codeql/codeql-config.yml

@@ -7,6 +7,6 @@
 #
 # Changing to SHA-256 would invalidate all existing local vectors and break
 # the documented compatibility invariant in regression tests. The release SARIF
-# gate waives only the two exact call sites; the CodeQL query remains enabled.
+# gate waives only three exact call sites; the CodeQL query remains enabled.
 
 name: "Engraphis CodeQL config"

.github/workflows/ci.yml

@@ -52,6 +52,8 @@ jobs:
         run: python -m eval.grounded
       - name: Code-agent arm gate
         run: python -m eval.code_arm
+      - name: Evidence contract boundary gate
+        run: python -m eval.evidence_contracts
 
   typecheck:
     name: core + backends typecheck (Python 3.11)
@@ -125,6 +127,8 @@ jobs:
         run: python -m eval.reinforcement
       - name: Adversarial memory prompt-boundary gate
         run: python -m eval.adversarial_memory_security
+      - name: Evidence contract boundary gate
+        run: python -m eval.evidence_contracts
       - name: Build and smoke installed core artifacts
         shell: bash
         run: |

.github/workflows/codeql.yml

@@ -10,6 +10,7 @@ on:
 
 permissions:
   contents: read
+  packages: read
   security-events: write
 
 jobs:
@@ -33,10 +34,23 @@ jobs:
           languages: ${{ matrix.language }}
           build-mode: none
           config-file: ./.github/codeql/codeql-config.yml
+          packs: ${{ matrix.language == 'python' && 'codeql/python-queries:AlertSuppression.ql' || 'codeql/javascript-queries:AlertSuppression.ql' }}
       - name: Analyze
         id: analyze
         uses: github/codeql-action/analyze@b96794f015dfd88f77b49b1c93e0fa7110f94c63 # v4
         with:
           output: codeql-results
+          upload: never
+          category: ".github/workflows/codeql.yml:analyze/language:${{ matrix.language }}"
       - name: Require clean CodeQL results
         run: python scripts/check_codeql_sarif.py "${{ steps.analyze.outputs.sarif-output }}"
+      - name: Filter approved non-security digest results
+        run: >-
+          python scripts/check_codeql_sarif.py --filter-approved
+          "${{ steps.analyze.outputs.sarif-output }}" codeql-results-filtered
+      - name: Upload CodeQL results
+        uses: github/codeql-action/upload-sarif@b96794f015dfd88f77b49b1c93e0fa7110f94c63 # v4
+        with:
+          sarif_file: codeql-results-filtered
+          category: ".github/workflows/codeql.yml:analyze/language:${{ matrix.language }}"
+          wait-for-processing: true

CHANGELOG.md

@@ -5,6 +5,10 @@ All notable changes to Engraphis are documented here. Format loosely follows
 
 ## [Unreleased]
 
+- Receipt-chain structural corruption remains fail-closed at the Store boundary without
+  bricking a completed service operation: affected responses now carry a content-free
+  `receipt_warning`, and graph/import workers preserve their completed state.
+
 ## [1.7.4] - 2026-09-13
 
 - Writable SQLite files now default to WAL plus FULL synchronization, with an explicit

Dockerfile

@@ -18,7 +18,9 @@ ENV PYTHONUNBUFFERED=1 \
     # Customer-side cloud session and entitlement display cache. Keep it on /data rather
     # than the container's ephemeral home so reconnects do not lose rotated credentials.
     # License issuance, trial state, leases, and revocations remain private services.
-    ENGRAPHIS_STATE_DIR=/data/.engraphis
+    ENGRAPHIS_STATE_DIR=/data/.engraphis \
+    # Dashboard-managed non-secret settings must survive a Railway redeploy with the volume.
+    ENGRAPHIS_ENV_FILE=/data/.engraphis/config.env
 
 WORKDIR /app
 
@@ -33,6 +35,8 @@ RUN apt-get update \
 COPY pyproject.toml README.md LICENSE NOTICE ./
 COPY engraphis ./engraphis
 COPY scripts ./scripts
+# The declared distribution license assets are part of the package build metadata.
+COPY deploy ./deploy
 
 # Railway runs CPU workloads.  Install the CPU-only PyTorch wheel before the embedding
 # stack so pip cannot select PyPI's multi-gigabyte CUDA dependency chain.  The public

README.md

@@ -44,7 +44,7 @@ by default, or accept an explicit workspace plus optional `from_ts`, `to_ts`, an
 `release_version` filters.
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/Coding-Dev-Tools/engraphis/main/docs/images/context-efficiency.svg" alt="Dark chart of local measurements and deterministic fixtures, including a local LoCoMo diagnostic marked with an asterisk. Cross-session handoff satisfaction rises from 3 of 15 queries with the last memories to 15 of 15 with proactive ranking or a consolidated summary. Intent-layered graph routing rises from 0 of 3 to 3 of 3 correct top-1 targets, and two-hop graph recall rises from 0 of 3 with one-hop expansion to 3 of 3 with Personalized PageRank. Consolidation-aware ranking selects the expected digest in 2 of 2 summary cases instead of 0 of 2 for the baseline. Structure-aware chunks reduce context from 740.3 to 214.3 tokens and the smallest evidence-holding memory from 162.2 to 42.4 tokens. A compact JSON-shape proxy uses 10,982 rather than 23,810 tokens. Grounded recall makes 11 of 11 correct decisions and packed context averages 85.38 tokens under a 1,500-token cap." width="100%">
+  <img src="https://raw.githubusercontent.com/Coding-Dev-Tools/engraphis/main/docs/images/context-efficiency.svg" alt="Dark chart of registered deterministic fixtures. Structure-aware chunks reduce retrieved context from 740.3 to 214.3 tokens and the smallest evidence-holding memory from 162.2 to 42.4 tokens. A compact JSON-shape proxy uses 11,138 rather than 24,590 tokens. Retrieved-candidate quality is labeled separately from packed-context quality, both measured in the selected report with packed-quality fields. Actual MCP transport and provider billing are not measured." width="100%">
   <br>
   <sup>Less repeated history means more room for the task, tools, and useful evidence.</sup>
 </p>
@@ -73,17 +73,27 @@ its counting boundary explicit.
 |---|---|---|---|
 | Retrieved top-5 memory content, averaged per question | Whole documents: **740.3** tokens → structure-aware chunks: **214.3** tokens | **526.0 fewer tokens per question** (**71.1% lower**, about **3.5× smaller**) | Recall@5 **1.000** in both modes across 6 documents and 18 questions |
 | Smallest returned memory that contains the reference evidence | Whole documents: **162.2** tokens → chunks: **42.4** tokens | **119.8 fewer tokens to evidence** (**73.9% lower**, about **3.8× smaller**) | The same 18 questions had a returned evidence-holding memory in both modes |
-| Full versus compact recall payload proxy across one 26-question pass within a 260-timed-recall CodeMem run | Full proxy: **23,810** `engraphis.regex.v1` tokens → compact proxy: **10,982** tokens | **12,828 proxy tokens avoided** (**53.88% lower**) | 26 payload samples; 260 timed recalls; Recall@5, hit@5, and answer-token recall all **1.000** |
+| Full versus compact recall payload proxy across one 26-question pass within a 260-timed-recall CodeMem run | Full proxy: **24,590** `engraphis.regex.v1` tokens → compact proxy: **11,138** tokens | **13,452 proxy tokens avoided** (**54.71% lower**) | 26 payload samples; 260 timed recalls; Recall@5, hit@5, and answer-token recall all **1.000** |
 | Packed prompt-context usage in the same 26-question CodeMem sample pass | Hard budget: **1,500** tokens; observed mean: **85.38**; observed maximum: **108** | A hard cap prevents a recall from exceeding its configured context budget | This is usage accounting, not a before/after savings comparison |
 
-These values are evidence IDs `offline-chunking` and `offline-performance` in
-[`offline-fixtures-v9.json`](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/benchmark-evidence/offline-fixtures-v9.json),
-SHA-256
-`455fc9d32a236e582a49aaaf9b84f30cae2573dc6ed982f4dd7dd845afcaf24c`.
+The performance report keeps its legacy `quality` fields for all candidate chunks returned before
+context packing and adds `packed_quality` for evidence admitted to the reader context. The checked-in
+v19 artifact includes both quality views, with Recall@5, hit@5 and answer-token evidence coverage
+of 1.000 for the 26-question fixture in each view. Both views measure retrieved evidence;
+neither is an end-to-end question-answer score. Coding outcomes, external datasets, and staged
+operational capacity remain separate pending evaluation tracks until their artifacts are selected.
+
+These values are evidence IDs `offline-chunking` and `offline-performance` in
+[`offline-fixtures-v70.json`](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/benchmark-evidence/offline-fixtures-v70.json),
+SHA-256
+`a8a96cb4d096ee72131d60307cc95b95f5b09716e813d9ee07090578dc1439c3`.
 [`BENCHMARKS.md`](https://github.com/Coding-Dev-Tools/engraphis/blob/main/BENCHMARKS.md#public-numeric-evidence-registry)
-records the matching suite digest, exact commands, and per-command config digests. External,
-model-dependent, consolidation, productivity, and latency results remain unpublished until the
-same evidence exists for them.
+records the matching suite digest, exact commands, and per-command config digests. The offline
+fixture registry intentionally excludes external, model-dependent, consolidation, productivity,
+and latency results. Completed retrieval-only diagnostics are published separately in the
+[benchmark expansion results](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/BENCHMARK_EXPANSION_RESULTS.md) with redacted immutable
+artifacts; no generated-answer, official leaderboard, hosted-latency, or paid result is claimed
+here.
 
 The compact payload shape avoids duplicating full memory bodies when the packed context and source
 list are enough. The evaluator tokenizes JSON-shaped full and compact payload proxies built from
@@ -546,11 +556,27 @@ For an agent prompt, prefer `engraphis_recall_context`: it returns one hard-budg
 `source_tokens`, `saved_tokens`, `savings_ratio`, `packed_count`, `omitted_count`, and
 `token_counter`), and optional diagnostics. Accounting is exact for the named counter; inject the
 reader's tokenizer when reader-model token parity is required. `engraphis_recall` remains the compatible full-recall
-surface; use `response_mode="compact"` when the packed context is enough and full memory bodies
-would duplicate it. For advanced query-planning configuration, see the
-[architecture guide](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/ARCHITECTURE_V3.md#query-planning).
-
-For bi-temporal reads, `valid_at` selects what was true at a Unix timestamp and `known_at` selects
+surface; use `response_mode="compact"` when the packed context is enough and full memory bodies
+would duplicate it. For advanced query-planning configuration, see the
+[architecture guide](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/ARCHITECTURE_V3.md#query-planning).
+
+Benchmark-driven alternatives are opt-in: `packing_mode="coverage"` keeps complete evidence
+units from more source memories, while `retrieval_recipe="conversation"` and
+`retrieval_recipe="long_session"` select the measured depth/budget starting points. The
+historical `legacy`/`default` settings remain unchanged. For a value that must survive a file
+edit or tool call exactly, Smart and Classic `engraphis_remember` and the Python/service write
+APIs accept source-bound `exact_value` plus its `exact_value_type`. MCP remember requires a
+unique occurrence; Python/service writes can select a repeated occurrence with `exact_value_span`.
+Packed binding metadata requires the complete memory source, preserving conditions in any
+language. Boundary whitespace outside the bound value may be trimmed. Coverage withholds a
+bound group that cannot fit; legacy keeps its selected text but omits the incomplete binding.
+Corrections and content revisions clear the old binding when content changes;
+pass `exact_value` to explicitly bind the replacement, with `exact_value_span=[start,end]`
+for a repeated occurrence, or `clear_exact_value=true` to remove a binding. Unchanged content
+and title-only revisions preserve valid bindings. History preserves the original record.
+MCP response trimming removes binding metadata whenever its supporting context is omitted.
+
+For bi-temporal reads, `valid_at` selects what was true at a Unix timestamp and `known_at` selects
 what Engraphis had learned then. `as_of` remains a compatibility alias for `valid_at`; supplying
 both is allowed only when they match.
 
@@ -762,7 +788,7 @@ file. It never searches the working directory for `.env`, and explicit process v
 |---------|---------|-------------|
 | `ENGRAPHIS_ENV_FILE` | `~/.engraphis/config.env` | Optional trusted config leaf selected before trusted values load. Its bounded dependency-free parser performs no interpolation. An explicit value must be an absolute path to an owner-private regular file; arbitrary working-directory `.env` files are ignored. |
 | `ENGRAPHIS_DB_PATH` | Source: `<repo>/engraphis.db`; installed: platform user-data directory | SQLite database file. Installed defaults are `%LOCALAPPDATA%\engraphis\engraphis.db` (Windows), `~/Library/Application Support/engraphis/engraphis.db` (macOS), and `$XDG_DATA_HOME/engraphis/engraphis.db` or `~/.local/share/engraphis/engraphis.db` (Linux). The environment variable overrides every default; a relative value is resolved from the trusted `~/.engraphis/config.env` directory so launch CWD cannot select a different workspace database. |
-| `ENGRAPHIS_SQLITE_DURABILITY` | `durable` | Writable file databases use WAL and FULL commit synchronization. Explicit `balanced` selects NORMAL, which can lose recent acknowledged writes after OS/power failure. Effective settings appear in diagnostics; see [SQLite durability](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/SQLITE_DURABILITY.md). |
+| `ENGRAPHIS_SQLITE_DURABILITY` | `durable` | Writable file databases use WAL and FULL commit synchronization. Explicit `balanced` selects NORMAL, which can lose recent acknowledged writes after OS/power failure. Effective settings appear in diagnostics; see [SQLite durability](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/SQLITE_DURABILITY.md). |
 | `ENGRAPHIS_HOST` | `127.0.0.1` | Server bind address |
 | `ENGRAPHIS_PORT` | `8700` | Dashboard port. A platform-injected `$PORT` (Railway/Fly/Heroku) takes precedence over this value for the dashboard bind; Compose pins both to `ENGRAPHIS_COMPOSE_PORT` so the mapping stays in sync |
 | `ENGRAPHIS_SERVICE_MODE` | `customer` | The public package supports only `customer`; hosted vendor, relay, compute, and worker roles are not distributed here |

deploy/railway-template.json

@@ -15,6 +15,11 @@
     }
   },
   "variables": {
+    "ENGRAPHIS_HOST": {
+      "value": "0.0.0.0",
+      "prompt": "Bind the public Railway service on all IPv4 interfaces so the platform PORT and health probe are reachable.",
+      "required": true
+    },
     "ENGRAPHIS_SERVICE_MODE": {
       "value": "customer",
       "required": true
@@ -27,6 +32,10 @@
       "value": "/data/.engraphis",
       "required": true
     },
+    "ENGRAPHIS_ENV_FILE": {
+      "value": "/data/.engraphis/config.env",
+      "required": true
+    },
     "ENGRAPHIS_API_TOKEN": {
       "value": "${{ secret(48) }}",
       "secret": true,