WARDEN-IN-0003: record post-rename verification (routing resolves under both names)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 101414@bnt-lap001 Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6
This commit is contained in:
parent
bbc97c5a4e
commit
e6ef060f7e
1 changed files with 11 additions and 2 deletions
|
|
@ -144,8 +144,17 @@ notes: 'REVIEWED 2026-09-21; one change made, one deliberately not made.
|
|||
Related and unresolved: WARDEN-WP-0039-T03 already waits on the credential proxy''s
|
||||
admitted policy binding, which is the same resource.system field seen from the
|
||||
delegated-read side. The rename must not be allowed to answer that question by
|
||||
accident.'
|
||||
accident.
|
||||
|
||||
|
||||
RENAME LANDED 2026-09-30 (flex-auth msg 2026-09-30; access-engine head b943d9a).
|
||||
Verified after the landing: warden route find resolves flex-auth-policy-check under
|
||||
both "access-engine" and "flex-auth" keywords; no catalog edit was required. The
|
||||
open question above is answered by FLEX-DEC-2026-013 (runtime names, including the
|
||||
policy resource.system string, stay flex-auth), so owner_repo/subsystem stay
|
||||
flex-auth until the runtime name changes. If flex-auth intends otherwise it must
|
||||
say so explicitly. Intake stays open for the owner to close.'
|
||||
created: '2026-09-21T00:00:00Z'
|
||||
updated: '2026-09-21T00:00:00Z'
|
||||
updated: '2026-09-30T00:00:00Z'
|
||||
state_hub_intake_id: "01a0c153-98e1-7705-bf82-a58c85df980f"
|
||||
```
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue