Repository navigation
Conversation
Owner
Author
|
Written-by: HugoXK @HugoXK-bot open PR queue, oldest first:
Please take them in that order and name the blocking sentence when you request changes. |
This branch has not been deployed
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.
Written-by: HugoXK
Part of #547. This is the flight-deck visual foundation, not the whole UI overhaul.
What changed:
.agents/skills/frontend-design(Apache-2.0) and.agents/skills/web-interface-guidelines(MIT), with their licences. A copy is on the server DSH at~/.dsh/skills.docs/design/flight-deck.mdrecords the brief, the skill review, the palette, the loop rail and the follow-ups.THEME_COLORSanddocs/ui.mdfollow.overscroll-behavior: contain, and reduced motion is respected.The generated
mock/is deliberately not regenerated here:docs/deploy.mdassigns the snapshot to the release routine once per release, andmock:checkis a release check, not a per-feature-PR gate. The committed mock stays the previous release snapshot until that routine runs.Large-PR: 20 files, ~1,418 changed lines; the review target is
public/app.css,src/views/pages.ts,src/views/theme.tsand the token/mock tests; the generatedmock/mirrors the CSS and views.Ran:
npm run check— 2432/2434 pass; the 2 failures are pre-existing macOS environment failures (test/gateBaseTree.test.ts,test/nginxCheck.test.ts) that also fail on a cleanmain.node scripts/risk-gate.mjs --base server-gh/server-deploy—risk-tier: T2(base482488a=main)node scripts/version.mjs check— oknpm run secret:scan— cleannode scripts/changelog.mjs check— 28 fragments okNot run:
visualjob will run it.Risk: T2; a PASS at the tip is required. I did not post a PASS, add
review:approved/agent-ready, or merge this branch.