Repository navigation
fix: map genuine SDK status outputs into Admin views (#137) - #143
Merged
Merged
Conversation
# Conflicts: # CHANGELOG.md # README.md
This was referenced Oct 25, 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
Map the SDK's actual platform.status output into reusable Admin UI models; preserve API machine responses and Keycloak ownership.
Part of #137 and treeseed-ai/platform#726. Stacked continuation of #142. Every issue remains open; no Task 3C completion claim.
Work authority
Contributor mode (select one):
Plan
Genuine API/Keycloak browser refresh red → owner docs → contract-valid default-browser fixture and unit regression red → raw SDK output validation → full owner gate.
Changes and commits
Six-file increment after #142. AdminViews consumes PlatformOperations.status.parseOutput directly, including historical generic and format-3 statuses. Reject invented envelopes and malformed results. The authority fixture now returns SDK-valid raw status; escaping uses allowed installation text rather than an invalid service ID. Rebuild private Admin .8/browser identity together.
Verification
bun run verify: semantic/strict checks, build, 3 unit + 2 integration + 4 smoke = 9 tests, zero failures. Contract-corrected Firefox default composition failed before the fix and passes afterward; raw status unit red/green and malformed/envelope negatives pass. Node default asset and exact owner adoption checks remain green. Archive .8 SHA-2566ed661574bbe10f00dfa09fafc84c60785e987152cd997ecb31395334077c4a2. Both exact-head Ubuntu 26.04 CI verify runs passed. API re-adoption's genuine Postgres/Keycloak/API/Caddy browser gate now passes with authenticated SDK status/application reads, responsive UI actions and exact prior-cookie revocation. Full API owner gate and remaining Task 3C transitions/acquisition/assembly are still pending.Risk and rollback
Private migration candidate. No production publication or cutover; preserve legacy branches and installations. Before merge, close or amend this draft without integration effects. After an authorized merge, revert its exact squash commit through a separate reviewed cordis PR; retain any durable records and require explicit repair instead of deleting uncertain state. Keep every issue, including Platform #678, open under release policy.
Completion summary
Bounded candidate submitted as draft. Parent Task 3C owner adoption, installed activation/source management and assembled acceptance remain pending. No claim of completed Task 3C or active user installation.
Submission checklist