Repository navigation
feat: integrate the landing, mock store and admin applications - #6
Merged
Merged
Conversation
marcelopenas
marked this pull request as ready for review
November 9, 2026 08:14
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.
Integrate three independent static Next.js applications on one domain: landing at /, store at /store/, and administration at /admin/. Pin fetchable private repository commits, add local Dockerfiles/Compose routing and a clearly labeled disposable UI fixture environment. The experience is an educational mock store: no real payments, transactions or shipments.
Gateway owns HttpOnly browser sessions/CSRF and public catalog access; Gateway/Account enforce administrator permissions. The store provides an online-only PWA manifest. Faro and Umami are integrated but collection is disabled until endpoints and policy are agreed. CDN hosting and per-app environment values must be discussed before deployment; no frontend Kubernetes deployment is added.
Coordinated draft reviews:
Validation: all three frontend CI workflows passed formatting/lint/types, 15 unit tests and 16 desktop/mobile browser cases, including two-tab logout regression coverage. Static exports and all three Docker builds passed. Local browser flows exercised catalog, cart, login, demo orders, authorization, product management, themes and mobile layout. Gateway/Account Maven verify passed 8/4 tests and coverage both locally with the workstation JDK 24 override and remotely with Java 25. Both Compose configurations validate and documentation builds with no issues. Detailed antislop delivery gate and evidence are in docs/frontend/verification.md.
Real Product/Exchange images/contracts, full backend integration, device PWA installation and actual collector payload verification remain acceptance prerequisites. Eight moderate development-tool audit findings are documented; production package audit is clean. Platform backend workflows initialize only backend submodules so private web repositories do not require broader access credentials.
The private frontend CodeQL scans reached analysis, but GitHub rejected uploads because Advanced Security is disabled. The owner chose to keep the repositories private and configure this later; private scanning is now opt-in via ENABLE_CODEQL=true after organization setup. Build, type, unit and browser checks remain automatic. Gateway/Account Java 25 tests, coverage and CodeQL passed, as did the platform backend/Compose/CodeQL workflows.
This review isolates the frontend task from pre-existing local infrastructure commits, which remain preserved on feature/frontend-applications-workspace. AI-assisted implementation and documentation; human review pending.