Preserve graph cache isolation, renderer lifecycle and scoped queries

BENCHMARKS.md

@@ -94,14 +94,14 @@ interpretation and do not count as additional benchmark-quality gains.
 ### Public numeric evidence registry
 
 Every exact public aggregate retained below comes from the checked-in, public-safe
-[`offline-fixtures-v114.json`](docs/benchmark-evidence/offline-fixtures-v114.json) artifact. Its
+[`offline-fixtures-v115.json`](docs/benchmark-evidence/offline-fixtures-v115.json) artifact. Its
 SHA-256 is
-`40188db31e07680e1c886ecec8ed523c6237858f0d5c63ef3159251c63538970`, also recorded in the
+`4d2cd6be29324597f0b201f8c0bd753173be69d24a274dff570c95c0db6ae629`, also recorded in the
 adjacent `.sha256` file. The artifact contains no raw questions, answers, prompts, customer data,
 or per-record content fingerprints.
 
 The fixture-suite digest is
-`6347175b1e4b3760e23afe2dcb7722d48557f987c45c7fcbd4f115e1e7720b54`. The artifact defines
+`ddf3b70d426441a364ef02967f98454435ca045c3840e1c4b81ba05ab7f139bb`. The artifact defines
 the digest algorithm and records the SHA-256 of every suite and dataset file. Each evidence ID
 also binds its exact command through `sha256(UTF-8 exact command)`:
 
@@ -123,10 +123,10 @@ Historical LoCoMo, graph, handoff, consolidation, and security figures remain pr
 source artifacts but are omitted from the current chart until each has a matching immutable,
 public-safe artifact. The chart labels coding outcomes, external datasets, and operational
 capacity as pending evaluation tracks rather than implying scores. Regenerate it with
-`python scripts/render_benchmark_report.py --report docs/benchmark-evidence/offline-fixtures-v114.json --output docs/images/context-efficiency.svg` after selecting the report to publish.
+`python scripts/render_benchmark_report.py --report docs/benchmark-evidence/offline-fixtures-v115.json --output docs/images/context-efficiency.svg` after selecting the report to publish.
 
 The companion examples are also generated from that artifact with
-`python -m scripts.render_benchmark_examples --report docs/benchmark-evidence/offline-fixtures-v114.json --output docs/images/evidence-backed-agent-examples.svg`.
+`python -m scripts.render_benchmark_examples --report docs/benchmark-evidence/offline-fixtures-v115.json --output docs/images/evidence-backed-agent-examples.svg`.
 The historical-to-executable mapping is in
 [`docs/BENCHMARK_CHANGE_COVERAGE.md`](docs/BENCHMARK_CHANGE_COVERAGE.md).
 

CHANGELOG.md

@@ -7,6 +7,12 @@ All notable changes to Engraphis are documented here. Format loosely follows
 
 - Provide a valid offline decision example in Smart MCP action discovery.
 - Reject coerced numeric/string remote consent before Classic MCP can select a Jev backend.
+- Retain global entities referenced by workspace edges during secure erasure,
+  while preserving exact-workspace incidence checks for workspace-owned entities.
+- Preserve graph cache isolation, pause intent through WebGL context loss, and
+  theme-correct exported backgrounds.
+- Scope graph incidence queries to candidate entities and retain shared legacy
+  entities during secure erasure.
 - Require the credential-bound control origin before selecting managed Jev.
 - Bound chunked response trailers while retaining strict deadline completion checks.
 - Keep relocation policy behind domain storage operations and 500-memory moves
@@ -28,7 +34,9 @@ All notable changes to Engraphis are documented here. Format loosely follows
 - Recognize complete chunked refresh responses at the watchdog boundary without
   accepting a missing or truncated trailer terminator.
 - Rebuild FastMCP settings eagerly to avoid a forward-reference warning on newer SDKs.
-- Refreshed the public offline fixtures and source bindings in immutable v110 evidence.
+- Preserve CSS gradient tiles, screen blending and reduced-motion opacity in graph PNGs,
+  including fractional display scaling; synchronize graph cache metadata across threads.
+- Refreshed the public offline fixtures and source bindings in immutable v111 evidence.
 
 - Added saved project-to-workspace routing and connection instructions so agents can use the
   user's selected workspace. Routine MCP calls inherit an omitted workspace from an authorized

README.md

@@ -84,9 +84,9 @@ neither is an end-to-end question-answer score. Coding outcomes, external datase
 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-v114.json`](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/benchmark-evidence/offline-fixtures-v114.json),
+[`offline-fixtures-v115.json`](https://github.com/Coding-Dev-Tools/engraphis/blob/main/docs/benchmark-evidence/offline-fixtures-v115.json),
 SHA-256
-`40188db31e07680e1c886ecec8ed523c6237858f0d5c63ef3159251c63538970`.
+`4d2cd6be29324597f0b201f8c0bd753173be69d24a274dff570c95c0db6ae629`.
 [`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. The offline
 fixture registry intentionally excludes external, model-dependent, consolidation, productivity,