Repository navigation
Add basic Environment Templates administration to Core Web - #44
Merged
Merged
Conversation
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.
Administrators currently have to open Session creation to find basic Environment Templates. Add a dedicated Templates view for the existing public client operations: complete catalog reads, name/network creation and partial updates, and confirmed deletion. Successful changes refresh the catalog shared with Session creation.
The view distinguishes empty, unsupported and failed reads; it fences responses after Core changes and never automatically replays an uncertain write. It does not create Sessions, allocate Runtime instances or call models. Advanced Template profiles remain explicitly outside the current client coverage. No server APIs, queries, runtime behavior, installer or business features change.
Validation: targeted component/client/type checks and Web build; 15 new Chrome browser scenarios; real Core with dedicated PostgreSQL and two project identities covering CRUD, pagination, omitted-field preservation, unauthenticated rejection and cross-project read/update/delete denial. Independent GPT-6 Astra high review passed, including 17 focused unit tests and 15 browser cases. Server
make checkpassed its database/sqlc/Go/Core/microsandbox/Claude gates but cannot launch browser tests because the host lacks libatk-1.0.so.0 (including with its installed Chromium). Fullmake check-webpassed on desktop Chrome: 903 client/Web unit tests and all 94 browser cases. Remaining MiniMax/Rust gates passed on the server (including format and Clippy). No repository test configuration changes are included. All component gates, real API acceptance and independent review have passed; this does not claim a clean single-hostmake checkrun.