FLEX-WP-0035-T05: informed-decision lifecycle v2 declares application.access

- application.access allows only with purpose=readback and the authoring
  human bar; no workload path, no audience or client-scoped claims
- v1 operations unchanged; pin.json moves to v2; live pin stays v1 until T04
- examples/application-readback: readback catalogue with informed-decision's
  key-cape client binding; integration test over the shipped files

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 609675@bnt-lap001
Assistant-Session: 4987a36e-eb38-4b10-803c-15a29cd78212

docs/application-access-readback.md

@@ -90,9 +90,15 @@ their own pins run, plus a merged registry snapshot.
   every consumer pin, which is exactly the widening constraint 2 forbids. It
   also makes per-page latency the sum of N pins.
 
-Code needed: `serve` today takes one `--policy`. The readback pin needs a
-multi-package mode keyed by `resource.system`, restricted to
-`application.access`.
+`serve-readback` implements this multi-package mode, keyed by
+`resource.system` and restricted to `application.access`. The pin's own
+catalogue registry is `examples/application-readback/registry_snapshot.json`.
+It lists participants and their `client_binding`, and its README names each
+participant's package and registry.
+
+First participant: `informed-decision`, through `informed-decision.lifecycle`
+v2 (`FLEX-WP-0035-T05`). Its `application.access` rule reuses the authoring
+`human` bar, requires `purpose == "readback"`, and has no workload path.
 
 ## 5. Request and response