feat: add SSI suite entry point - #12
Merged
Merged
Conversation
Add a static /ssi route, home tile, and nav entry for the folded SSI Control Tower backend module. Document the root browser-runtime boundary and cover the route with unit and Playwright privacy tests.
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.
Summary
/ssiroute for SSI Control Tower inside the root Payment Intelligence Modules suite.Backendposture, while keeping the page static and fetch-free.Privacy / architecture boundary
/ssidoes not call the FastAPI app, iframe it, fetch status, use storage, use telemetry, or link to localhost.apps/ssi-control-tower/.Verification
pnpm verifypnpm test:e2egit diff --checkcd apps/ssi-control-tower && make test