Repository navigation
chore: qualify UI with the combined capacity SDK successor (#101) - #105
Merged
Merged
Conversation
4 tasks
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
Qualify reusable React/Cordis presentation with one exact combined SDK capacity successor. Preserve all components, mobile-first behavior, terminal providers and Keycloak identity boundaries.
Work authority
7377433d9c1bcfd1079907686bdc21b4dea83573.db013ecf81b08773dd8c4f0c4871a60980759ce6.Contributor mode:
Plan
Document exact closure → require selected/installed identity → update immutable archive/pins → complete owner checks/build/four tiers and genuine consumers. Seven files. No source imports cross owners.
Changes and commits
934d409 documents the successor; cd7508e pins the expected package identities before implementation; 45684e6 updates one exact SDK archive, lock and UI artifact identity. No presentation or identity authority is transferred.
SDK .35 source
bc6cb6610fd5ddc13639b3c3bc8b709ed930d647, SHA-25698a4474726b79c1ce1a4b96a76e636a3dafa8e20df3dc66db89331ae79b31fbf; UI .22 archive33511b90cbfcae4375f3034e3d79ea47bb495cbe05128d9aba740d661dc16b08. SDK #493–#497 are now integrated into cordis; .35 is the reviewed activity/environment/lease/pool/protocol closure. The earlier UI .21/SDK .30 artifacts remain immutable. Follow-up documentation and intended-red identity controls precede this selected/installed update.Verification
Risk and rollback
Earlier archives and historical assembled pins remain immutable. A populated Bun cache initially retained .22 despite the changed archive; the real identity gate caught it, and a fresh-cache update plus independent frozen installation verified the repaired lock. Shared process follow-up is recorded separately in platform#809. Revert this exact closure if needed. No new UI, production publication, legacy mutation, issue closure or merge.
Completion summary
All local owner/public artifact gates pass. Reconciled hosted owner gates passed; upstream source is reviewed/integrated; full Task 3D is ongoing.
Submission checklist