KEY-WP-0039-T02: record Platform source-prepared owner returns

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 903097@bnt-lap001
Assistant-Session: aa320c8f-c3fa-46e7-8541-0b58e1e45d23

workplans/KEY-WP-0039-openbao-negative-probe-tokens.md

@@ -9,7 +9,7 @@ flavor: implementation
 owner: claude-code
 topic_slug: netkingdom
 created: "2026-10-10"
-updated: "2026-10-14"
+updated: "2026-10-17"
 depends_on: []
 related_repos:
   - railiance-platform
@@ -337,3 +337,15 @@ leeway/refusal/capability/no-fallback/cleanup proof. The live registration go is
 already recorded resolved; do not ask again. Attended human authentication and
 owner-held existing coding-agent custody go on the single attended checklist.
 No credentials, live registry/API changes or KEY-WP-0040 recovery work occurred.
+
+2026-10-17 Platform owner returns (source-prepared, not admitted):
+railiance-platform `docs/proposals/2026-10-17-key39-t02-owner-returns.md`
+(commit `0a9617a`). The coding client `codex-railiance-platform` has no
+admission, custody or delivery record. The existing narrow proposal
+`docs/proposals/2026-10-11-key39-coding-client-custody-proposal.json` (`9460f6f`)
+remains the one to admit, so the coding-agent case stays unrunnable until owners
+admit it. The role source (`openbao/auth/secrets-engine-jwt-role.json`) matches
+the packet's claim design. It declares no `expiration_leeway`, so the expiry
+probe must assume OpenBao's 150s default until an attended sanitized read
+confirms the live value. The node-local Bao origin is not declared in source and
+also needs that attended read. T02 stays wait.