Merge branch 'pratik/otel-phase9-metric-gap-fill' into pratik/otel-phase10-workload-validation

Three doc conflicts, all inside Phase 10's own sections. Resolved by keeping
phase-9's corrections and re-applying phase-10's ownership of those sections on
top, rather than taking either side wholesale:

06 §6.8.3 — Status now says Phase 10 is implemented on THIS branch (phase-9's
copy said "not merged into this branch", true there, false here). The stale
"71 checks" enumeration and "Current Status" list are replaced by phase-9's
dynamic-count description plus a Known Gaps list that states the real reason
the rpc.process hierarchy is unassertable: rpc.process is HTTP-only, so a
WebSocket-only workload never produces it. Phase-9's CI Deliverable subsection
is carried through; exit criteria keep phase-10's tick state with phase-9's
corrected wording.

06 §6.8.3 Architecture — the automatic merge had resurrected phase-10's stale
2-node cluster prose and diagram over phase-9's 5-node correction. Reconciled
to phase-10's topology (native xrpld processes vs the containerised backend,
which is accurate) with phase-9's node count: 5 validators, and the collector
labelled OTLP + filelog rather than StatsD, which the config has never had.
Dropped the "all 26 metrics required" label in favour of the manifest.

06 §6.8.3 Key Implementation Details — two claims corrected against the code.
The StatsD m_dirty gauge fix describes a member that exists nowhere in the
repo, and the harness sets [insight] server=otel anyway, so gauges export
through an observable-gauge callback. The tx.receive attribute keys are bare
suppressed and tx_status, not dotted, and tx_status is set only on the
reject/known-bad/dropped paths, so it is absent on a successful receive.

09 §5c — kept phase-10's four-column table shape, with phase-9's corrected
counts: 40 of 41 emitted spans, 67 required attributes, 14 of 15 dashboards.

Phase10_taskList — dynamic inventory totals, the real RPC span trees, and exit
criteria ticked where the code on this branch closes them. Per-RPC timings are
recorded as not gated: regression-metrics.json defines only spans and job_queue.

Verified every hunk of the phase-10 diff falls inside a Phase-10-owned section
(06 §6.8.3, 09 §5c, Phase10_taskList, and the runbook's appended Phase 10
sections); no phase-9-owned text is modified from this branch.

.github/workflows/on-pr.yml

@@ -77,6 +77,16 @@ jobs:
             .github/workflows/reusable-check-rename.yml
             .github/workflows/on-pr.yml
 
+            # The non-code layers the OTel naming check validates: the docs that
+            # publish attribute tables (Rule E) and the telemetry stack config —
+            # collector, Tempo, dashboards (Rules B, C, D). Without these paths a
+            # docs-only or dashboard-only pull request sets `go=false`, so the
+            # very layers those rules exist to police would never be checked.
+            # As with `README.md` below, matching one of these also switches on
+            # the rest of the workflow; there is a single `go` gate.
+            docs/**
+            docker/telemetry/**
+
             # Keep the paths below in sync with those in `on-trigger.yml`.
             .github/actions/build-deps/**
             .github/actions/generate-version/**

.github/workflows/reusable-check-otel-naming.yml

@@ -21,6 +21,13 @@ jobs:
     steps:
       - name: Checkout repository
         uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+      - name: Test the OTel naming checker
+        # The checker's own unit tests, run before the check itself so a broken
+        # rule is reported as a broken rule rather than as a naming violation
+        # (or, worse, as a rule that silently stops flagging anything).
+        # stdlib `unittest` only: the repo installs no third-party test runner
+        # for CI, and the checker itself is deliberately dependency-free.
+        run: python -m unittest discover -s .github/scripts/otel-naming -p 'test_*.py' --verbose
       - name: Check OTel naming
         # The script is stdlib-only and reads only files already in the tree;
         # it enforces each rule only when the layer it needs is present, so it