Keep corpus configuration current and clarify gateway cost dashboards

Fence registry and config loads by operator intent so late responses cannot
restore a deleted corpus or replace the active configuration. Show UTC calendar
cost ranges and native model/lane totals without converting missing evidence
to free work or implying exporter delivery from an absent error count.

@codex review

Author: DMontgomery40

docs/exec-plans/active/graphrag-continuation-2026-09-04.md

@@ -831,3 +831,41 @@ shared-code scope: 70 files, 1,006 symbols and 95 affected flows. The CLI still
 caps its displayed names with a larger limit, while reporting that its counts and
 risk cover all changes; exact staged paths were checked separately. A fresh PR
 review and full CI run follow.
+
+The amended PR90 head `9c3bb56b` passed full CI with 2,922 tests and 68
+environment-gated skips in 860.85 seconds. GitHub Codex review reported no major
+issues on that exact head. PR90 merged as `2a3555a7` on September 5 at 08:42 UTC;
+post-merge CI and production activation remain pending.
+
+### Separate operator follow-ups
+
+The Cost & Capacity dashboard follow-up uses UTC midnight for Today and retains
+explicit selected-range and seven-day meanings. Native model/lane counters use
+reset-aware queries and normalize absent lane labels to unattributed. The pinned
+collector experiment confirmed that an asynchronous OTLP export failure does not
+necessarily emit a callback-failure counter sample. Scoped terminal-error logs
+therefore remain separate evidence. Their zero is guarded by the presence of logs
+from the same gateway service; absent or foreign-only logs remain unavailable.
+Five real Loki cases, the real Prometheus reset/midnight matrix and nine dashboard
+tests pass. Sol approved the final presence correction. No production dashboard
+change has been made yet.
+
+Shared config loads now pin corpus/global scope and reject older selection epochs,
+including A to B to A. The private Graph browser suite passed 14 cases after a
+test-observer correction: Vite's actual timestamped module URL must be reused to
+inspect the rendered app's store. Frontend lint, 21 unit tests and build passed in
+that Graph overlay. Sol then found a further upstream recurrence: an older corpus
+registry response can resurrect a deleted corpus after a newer forced refresh.
+The new held-response regression reproduced that recurrence against the prior
+store. Registry publication now fences success, failure, loading, URL/storage
+canonicalization and events by request generation. All 16 Graph browser cases
+pass, including old and new concurrent registry loads. All nine accounting UI
+cases also pass with these shared-store changes. Final frontend lint, 23 unit
+tests, build, nine dashboard tests with the real Prometheus query engine, Ruff,
+banned-pattern and generated-type checks pass. Sol approved the final registry
+correction; E5 and this config correction are frozen for their own publication.
+
+The cloud-embedding transport continuation has begun as a separate source slice.
+It will route existing OpenAI embedding calls through the native gateway with
+explicit identities while preserving local embedding paths and dense contracts.
+It is excluded from the pending PR90 deployment and NASA rebuild.