fix(review 005 Unit 3): resource_id_path wire round-trip + bootstrap-list doc alignment (G-04, G-05)

- resource_id_path rides both halves of the spec wire round-trip:
  spec_to_json_pub serializes it (optional string key), rebuild_spec_for
  parses it. Additive optional field - absent stays absent. Previously
  an announced (or from_call-imported) op declaring ownership-scoped
  resource extraction silently rebuilt with resource_id: None, so ACL
  checks ran without the resource ID.
- Gates: spec_round_trips_resource_id_path (serialize -> parse ->
  field intact) + spec_without_resource_id_path_stays_absent (additive
  field breaks no consumer).
- ADR-022 amendment: bootstrap-op set gains services/list-peers with a
  dated G-05 note (the installer has registered it since the amendment
  landed; the doc lagged the code). Set remains closed at four.

Verification: cargo test 589 / --all-features 606, clippy
(all-targets, all-features, wasm32) clean, fmt clean, doc clean.

Refs docs/reviews/005-...md (G-04, G-05; all findings closed).

docs/architecture/decisions/022-call-protocol-client-and-adapter-contract.md

@@ -385,6 +385,11 @@ channel 0. The set is closed:
 - `services/list` — discovery (the op `from_call` dials on every
   import; each side is expected to serve it)
 - `services/schema` — per-op schema disclosure
+- `services/list-peers` — peer-keyed discovery (the op that makes
+  peer-announced ops discoverable; `from_call`-import discovery
+  relies on it). Added to this list 2026-09-04 (review 005 G-05) —
+  `install_bootstrap_discovery` has installed it since the amendment
+  landed; the set was declared closed and the doc lagged the code.
 - `op/register` — peer op announcement (below)
 
 These are the ops a peer may assume are reachable (subject to each