docs: document build trigger in frontend spec - #390
Merged
Conversation
|
This was referenced Jul 14, 2026
Merged
Scr4tch587
had a problem deploying
to
github-pages
July 17, 2026 02:32 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Blackgaurd
approved these changes
Jul 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
2 participants
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.
What
Documents the build trigger in
SPEC-frontend.md: new "Build panel" feature section,build-panel.tsxin the file structure, andtriggerBuild/dryRunBuildin the api-integration list (with the note that browsing still never builds — builds only happen explicitly through the panel).Why
Repo convention: spec files track what the code actually does, updated as the final PR of the stack.
Benefit
The frontend spec stays an accurate map of the shipped UI for the next person touching it.