feat(portfolio): fold in RAILIANCE-WP-0016 apps-pg evidence

First delegated evidence from RESOURCE-WP-0003-T04 to land. railiance-platform
delivered apps-pg capacity, utilization, consumers, and the apps-pg-dbbytes-v1
allocation driver, and correctly delivered no EUR.

- data/resources/apps-pg.json: real capacity; allocation unattributed -> shared
  under apps-pg-dbbytes-v1; second consumer vergabe-teilnahme registered
- data/control-cycle/apps-pg-2026-09-base.json: first operational control-cycle
  record in the repository
- examples/control-cycle/apps-pg-*.json retired; the invented fixture collided
  with the real record's identifier
- data/portfolio-coverage-2026-08-14.json: gap marked delivered with three
  residual unknowns still open

The real evidence exposed a design gap in the T05 schema: v0.1 required a number
for every cost field, so recording genuine usage without a booked cost meant
inventing one. Schema 0.2 permits null costs, null unattributed_eur, a technical
unattributed_share, and null measurements. Null is unknown, never zero; an
unknown component makes the total null rather than the sum of the known parts;
and the comparator classifies unknown amounts as data_quality instead of
computing a variance. Existing 0.1 records are not rewritten.

apps-pg is now measured (idle at 5.8% of volume) and attributed, and remains
unpriced: delivered technical evidence does not create a booked cost.

86 tests pass.

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

docs/portfolio-operating-cadence.md

@@ -47,6 +47,19 @@ reason, rather than being silently omitted from the ratios.
 | **Pre-renewal review** | At least 60 days before the earliest `renews_on` or `cancel_by` | Contract evidence, utilization, open cases | Human financial authority | A `renewal` case, decided while cancellation is still possible |
 | **Event-driven** | Sustained variance beyond threshold, an incident exposing a failure domain, or a workload request | The triggering evidence | Owning repository | A case of the matching type per `docs/optimization-cases.md` |
 
+## Delivered evidence stays visible
+
+A delegated gap that is answered does not vanish from the report. It moves from
+`coverage.unresolved_gaps` to `coverage.delivered_gaps`, keeping the interface
+that answered it and the **residual unknowns** it did not, and each residual
+still generates a next action. Partial delivery must not read as full coverage.
+
+`RAILIANCE-WP-0016` is the first example: railiance-platform delivered apps-pg
+capacity, utilization, consumers, and the `apps-pg-dbbytes-v1` allocation
+driver, and deliberately delivered no EUR. Three residuals remain open — the
+booked host share, the labour estimate, and the absent recovery objectives — so
+apps-pg is now measurable and attributed while still counting as unpriced.
+
 ## Reading the current report
 
 As of 2026-08-14 an operator asking the four questions this cadence exists to
@@ -55,12 +68,15 @@ answer gets these answers, and the honest ones are the useful ones:
 - **Material spend?** Unknown, and explicitly so. Only the proposed backup
   storage carries price evidence. Every other resource is waiting on
   `RAIL-HO-WP-0008` and `FIN-WP-0004`.
-- **Idle or saturated capacity?** `railiance01` and the `reef-railiance` k3s
-  cluster are idle on every measured metric — 14 percent CPU, 37 percent memory.
-  Nothing is saturated. Five resources cannot be measured at all.
-- **Forecast error?** Not yet computable. The control-cycle mechanism is proven
-  on paired examples, but no operational actual observation exists, so there is
-  no variance to report and none is fabricated.
+- **Idle or saturated capacity?** `railiance01`, the `reef-railiance` k3s
+  cluster, and `apps-pg` are idle on every measured metric — 14 percent CPU,
+  37 percent memory, and 5.8 percent of the apps-pg volume. Nothing is
+  saturated. Four resources cannot be measured at all.
+- **Forecast error?** Not yet computable. The first operational forecast record
+  exists for apps-pg, but its period is 2026-09 and no actual has been observed
+  against it, so there is no variance to report and none is fabricated. Its
+  infrastructure cost is `null`, so even when the actual lands, cost variance
+  will read `unknown` until a booked fact arrives.
 - **Approaching commitments?** None visible — and that is itself the finding:
   six active resources have no renewal or cancellation date recorded, so the
   cancellation window cannot be respected for any of them.