[SYMPP-779B] Gate the production dashboard build - #586
Open
Pimpmuckl wants to merge 1 commit into
Open
Conversation
Pimpmuckl
force-pushed
the
2kftdpbmfedr2ihh
branch
from
August 7, 2026 01:38
4fc6f7a to
ae7409d
Compare
Summary: - install locked frontend dependencies and build dashboard assets once - add the production build to the PR gate and correct onboarding Rationale: - fail delivery when Vite cannot produce the production dashboard - keep fast backend iteration free of frontend build work Tests: - npm ci && npm run build && npm test && npm run quality - make all (1658/1662 tests passed; 4 existing Windows artifact launcher failures report database_unsupported) - dry-run counts: root build 1, Elixir-only build 0 Co-authored-by: Codex <codex@openai.com>
Pimpmuckl
force-pushed
the
2kftdpbmfedr2ihh
branch
from
August 7, 2026 01:42
ae7409d to
f284e98
Compare
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.
Context
The full delivery gate did not prove that Vite could produce the production dashboard, and Elixir onboarding named an outdated toolchain.
TL;DR
Build production dashboard assets once in full local and PR gates; keep the fast Elixir loop unchanged.
Summary
make allinstall locked frontend packages and run the production build once.Alternatives
make -C elixir allunchanged instead of slowing the backend-only development loop.Test Plan
make -C elixir all- 1658/1662 passed; four existing Windows artifact tests reportdatabase_unsupported.make -C elixir ci-full- not required for this quick-fix package.npm ci && npm run build && npm test && npm run quality- all frontend gates passed in delivery order.rvw_06a253d1- clean after verified findings were fixed.