Production-readiness: hosted E2E smoke harness + audit (WIP)#37
Draft
cooper (czxtm) wants to merge 1 commit into
Draft
Production-readiness: hosted E2E smoke harness + audit (WIP)#37cooper (czxtm) wants to merge 1 commit into
cooper (czxtm) wants to merge 1 commit into
Conversation
Adds apps/web/e2e-hosted/: a Playwright config that drives a DEPLOYED studio (production or staging) instead of a local dev server, plus a read-only, unauthenticated smoke spec: - landing renders with no uncaught page errors - /dashboard auth-gates unauthenticated visitors to /login - /login presents a sign-in affordance - /studio responds without a 5xx or crash SMOKE_BASE_URL selects the target; SMOKE_IGNORE_HTTPS_ERRORS=1 tolerates TLS-intercepting egress proxies while staying strict in clean CI so a genuine production cert regression still fails. README documents the deferred authenticated studio<->agent flow for when staging is healthy. Verified: 4/4 green against https://stackpanel.com via Chromium. https://claude.ai/code/session_01TMCMpDmbLomRBZbg3FpvMV
Contributor
|
Preview deployed to |
Contributor
|
Docs preview deployed to |
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.
Production-readiness workflow (WIP)
Running an end-to-end "ultracode" workflow to get StackPanel production-ready: a parallel audit of the three runtime planes plus a browser-driven E2E against the hosted studio.
Landed in this PR so far
apps/web/e2e-hosted/): a Playwright config that drives a deployed studio (production or staging) rather than a local dev server, plus a read-only, unauthenticated smoke spec:/dashboardauth-gates unauthenticated visitors to/login/loginpresents a sign-in affordance/studioresponds without a 5xx or crashSMOKE_BASE_URLselects the target;SMOKE_IGNORE_HTTPS_ERRORS=1tolerates TLS-intercepting egress proxies while staying strict in clean CI so a genuine production cert regression still fails.https://stackpanel.comvia Chromium.Observations already surfaced
/dashboardredirects unauthenticated users server-side to/login, but/studioreturns 200 and stays put (client-gated). Likely benign (studio data comes from the local agent), but flagged for review.Coming next (same branch)
staging.stackpanel.comnot responding, staging API returning 503).https://claude.ai/code/session_01TMCMpDmbLomRBZbg3FpvMV
Generated by Claude Code
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.