up

docs/modules/zastava/operations/runtime.md

@@ -123,12 +123,18 @@ It aligns with `Sprint 12 – Runtime Guardrails` and assumes components consume
   - Extract Prometheus rules into offline monitoring cluster (`/etc/prometheus/rules.d`).
   - Import Grafana dashboard via `grafana-cli --config ...`.
 
-## 6. Observability assets
-
+## 6. Observability assets
+
 - Prometheus alert rules: `docs/modules/zastava/operations/runtime-prometheus-rules.yaml`.
 - Grafana dashboard JSON: `docs/modules/zastava/operations/runtime-grafana-dashboard.json`.
-- Add both to the monitoring repo (`ops/monitoring/zastava`) and reference them in
-  the Offline Kit manifest.
+- Add both to the monitoring repo (`ops/monitoring/zastava`) and reference them in
+  the Offline Kit manifest.
+
+### 6.1 Surface manifest troubleshooting
+- Metrics: `zastava_surface_manifest_failures_total{reason=not_found|fetch_error}` increments when Observer cannot resolve cached `cas://` pointers or digests; correlate with Scanner cache health.
+- Evidence: Observer appends `runtime.surface.manifest{resolved|not_found|fetch_error}` plus `runtime.surface.manifestUri`/`manifestDigest` and up to five artifact metadata keys per manifest; view via drift diagnostics or runtime posture evidence.
+- Checklist: ensure `Surface:Manifest:RootDirectory` points to the Scanner cache mount, tenant matches `ZASTAVA_SURFACE_TENANT`, and `cas://` URIs from drift/entrytrace events exist on disk (`<root>/manifests/<hh>/<tt>/<digest>.json`).
+- Offline: if missing, sync the manifests directory from Offline Kit bundle into the Observer node cache and rerun the drift check. Avoid network fetches.
 
 ## 7. Build-id correlation & symbol retrieval