Place telemetry on the Quality dimension as Q2 Observability

The placement question seeded as open is answered by canon rather than by a
new decision. OAS section 8 defines Q2 Observability as 'telemetry and
monitoring: metrics, logs, traces' - this repo in canon's own words.

The 2026-08-11 coherence review found Railiance had been modelling itself on
one of OAS's six required dimensions and treating everything else as unplaced.
Observability was never homeless; the dimension it belongs to was not in use.
Notes Q7 Governance as the sibling concern - the conformance loop, the other
half of the self-evidencing aspiration this repo serves.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

SCOPE.md

@@ -70,8 +70,9 @@ output.
 
 - Status: **seeded** — `INTENT.md` written 2026-08-11, no implementation yet
 - The live cluster has no monitoring namespace; this is greenfield
-- Open: stack-dimension placement is undecided (see `INTENT.md`, "Open
-  Placement Question") and belongs to `railiance-master`
+- Placement: **Quality dimension, Q2 Observability** — canon defines Q2 as
+  "telemetry and monitoring: metrics, logs, traces". Ratification sits with
+  `railiance-master`; the question is answered, not open
 
 ---