nk-bind-executor go-live: the case of record is net-kingdom security-cases/nk-bind-executor-approval.yaml

The type's example stays an example; accepted cases live in security-cases/ (as nk-synthetic-journey).
The broker takes the case by path and hash, so only the runbook path changes.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 523928@bnt-lap001
Assistant-Session: 6c737afb-9c14-4152-9f02-477214b9c350

docs/credential-lane-designs/nk-bind-executor-go-live.md

@@ -40,7 +40,7 @@ delivered to KeyCape by ESO, and read natively by the executor through CCR-2026-
 
 - **G1, before step 5 (mint).** The founder accepts case `nk-bind-executor-approval` (owner and
   founder), and net-kingdom commits
-  `security-case-types/oidc-service-client/examples/nk-bind-executor-approval.yaml` with
+  `security-cases/nk-bind-executor-approval.yaml` with
   `status: materialized` and `acceptance: {at, record, by: [{role: owner}, {role: founder}]}`. The
   broker refuses anything else (`case_not_materialized`, `case_source_validation_failed`); a synthetic
   copy with exactly that shape passed the broker's case check on 2026-11-04.
@@ -144,7 +144,7 @@ CCR-2026-0043), not the platform-admin envelope.
 cd /home/worsch/railiance-platform
 export BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200
 unset BAO_TOKEN VAULT_TOKEN
-CASE=/home/worsch/net-kingdom/security-case-types/oidc-service-client/examples/nk-bind-executor-approval.yaml
+CASE=/home/worsch/net-kingdom/security-cases/nk-bind-executor-approval.yaml
 grep -q '^  status: materialized$' "$CASE" && echo case-materialized
 REF="nk-bind-executor-approval@sha256:$(sha256sum "$CASE" | cut -d' ' -f1)"
 bao login -no-print -method=oidc -path=netkingdom role=credential-broker-keycape-client-secret-generate