Close forge observability task

SCOPE.md

@@ -165,6 +165,8 @@ lessons into reusable S5 app release patterns.
   with `railiance-platform`, especially for shared CNPG databases consumed by
   S5 apps. Forge artifact restore and secret-custody evidence is defined in
   `/home/worsch/railiance-forge/docs/backup-restore-secret-handoff.md`.
+- Forge release-readiness evidence that S5 app runbooks may cite is defined in
+  `/home/worsch/railiance-forge/docs/observability-operating-evidence.md`.
 
 ---
 

workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md

@@ -307,7 +307,7 @@ without owning registry credentials or package backup procedures.
 
 ```task
 id: RAILIANCE-WP-0006-T08
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "ce2ebe48-052a-4e3e-86aa-441274940078"
 ```
@@ -327,6 +327,16 @@ Define at least:
 Done when forge availability and artifact health can be inspected without
 manually reconstructing the system.
 
+Completed 2026-06-05: the detailed observability and operating evidence
+contract now lives in
+`/home/worsch/railiance-forge/docs/observability-operating-evidence.md`. It
+defines read-only health checks for web/API, Git SSH, OCI registry, Python
+package registry, Actions/runner, database, logs, and package storage; manual
+storage thresholds and intervention rules; release-readiness evidence that S5
+app deployments can cite; and the future split between forge-owned signal
+definitions, platform-owned durable metrics/log storage, enablement templates,
+and a possible future observability repo.
+
 ---
 
 ## T09 - Add Railiance Fabric declarations for forge capabilities