Repository navigation
chore: align API manager-compatible owner archives (#644) - #653
Merged
Merged
Conversation
This was referenced Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Align API's existing application with exact manager-compatible public owner archives and bounded durable Deployment publication. The previously failing genuine installed API/Keycloak/database/edge/browser gate now passes locally with its original assertions and deadlines.
Work authority
92331d397e8c813de8b834ac54b134adba450ba0.31fc9d2099519f62b8ffe12ae9ee483fe071ab92.Contributor mode:
Plan
Owner selection documentation precedes exact-selection red and archive adoption. The .12 continuation uses documentation dd0d267/26cf349d3a, intended .126-versus-.122 selection failure aad0611 and adoption 31fc9d2. Earlier .10/.11 failed application evidence and exact archives remain immutable; the current description reports final .12 behavior.
Changes and commits
Dependency-only API .12 selects SDK .42, Deployment .126, Identity .9, Admin .12 and UI .23. Preserve all runtime source, seven platform operations, routes, Keycloak, mobile-first presentation, AGPL and API #620 approved-committer blob b1a687db754ee2fac141919e6c63052d12bf2812. No cross-checkout imports, authority changes, seed-runtime completion or productive Work/model execution.
Exact owner producers / archive SHA-256:
Ten files; no baseline/exception additions or deadline/assertion changes. Exact selection caught Bun retaining installed .122 after the file archive changed. A forced script-disabled install with a fresh cache regenerated the correct .126 lock SRI; installed metadata, producer/archive identities and genuine runtime were rechecked before committing adoption.
Verification
Previous .11 staging consumed 146.631 seconds before activation and failed; .10 also recorded exchange/drain failure. No failed observation is rewritten as success, no unexplained gate is retried, and temporary generated diagnostics were restored byte-for-byte. The unapproved permanent diagnostics process proposal remains separate.
Risk and rollback
Installation timing and exact closure compatibility require the original genuine gate on both current-head hosted runs. All owner and API gates now qualify this bounded slice. Revert owner archives/pins/lock and API identity together; preserve old artifacts, original checkouts, #620 and legacy services. API #645 internal seed reconciliation remains separate and held. No production publication or cutover; all issues including platform#678 stay open.
Completion summary
All local owner tiers and public archive proof pass, including the previously failing genuine installed root. Owner integration, both complete current-head API hosted runs and final review pass. This existing-root compatibility slice is qualified. This does not complete Task 3D or live Agent capacity.
Submission checklist