Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
@@ -97,7 +97,7 @@ smoke runs.
|
||||
`REQUIRE_E2E_READINESS=1` intentionally requires the mobile browser matrix, strict a11y mode, real log-only workflow-run opt-in, and every seeded path or credential consumed by the non-mutating strict specs: dashboard, account/profile settings, governance/policies, subscription, API overview/keys/docs/logs, portal analytics/settings, admin email sequences, plugin settings, read-only plugin credentials, workflow engine index, workflow builder/API-run/manual-run, webhook builder/manual-run, and the local plugin binary base path. That keeps staging/readiness runs from silently exercising only the desktop Chromium lane, skipping account/profile continuity, API docs/logs, portal management coverage, plugin permission coverage, workflow engine coverage, email-sequence dashboard coverage, or governance coverage, or ignoring moderate accessibility regressions. It does not require `E2E_ALLOW_WORKFLOW_WEBHOOK_RUN=1`; real webhook delivery stays operator-owned.
|
||||
|
||||
Subscription checkout success remains a separate strict opt-in because it
|
||||
requires an externally acquired Stripe checkout session return path. Normal
|
||||
requires an externally acquired Legacy-Provider checkout session return path. Normal
|
||||
readiness runs stay non-mutating and do not require
|
||||
`E2E_TENANT_SUBSCRIPTION_SUCCESS_PATH`. In an operator-approved lane that has a
|
||||
valid success return URL, enable the manual `subscription_success` dispatch
|
||||
@@ -114,8 +114,8 @@ page reload and a full logout plus re-login (a fresh appData load). Because
|
||||
reconciliation is loader-side (pull-based), the reconciled state is read back
|
||||
through the real subscription settings loader rather than the success-page
|
||||
render alone, and the flow only navigates app routes (dashboard, settings,
|
||||
login/logout) so it never triggers a real Stripe network call. This stays a
|
||||
strict opt-in for the same external-blocker reason: it needs a real Stripe
|
||||
login/logout) so it never triggers a real Legacy-Provider network call. This stays a
|
||||
strict opt-in for the same external-blocker reason: it needs a real Legacy-Provider
|
||||
checkout return path, so the lane skips when `E2E_REQUIRE_SUBSCRIPTION_SUCCESS`
|
||||
is off and fails loudly when it is required but `E2E_TENANT_SUBSCRIPTION_SUCCESS_PATH`
|
||||
or tenant credentials are missing.
|
||||
@@ -124,7 +124,7 @@ The static a11y coverage gate also enforces named browser readiness surfaces,
|
||||
not only raw file counts. `pnpm run verify:a11y-coverage` must keep explicit
|
||||
coverage for registration-to-dashboard, plugin settings, tenant API docs/logs,
|
||||
tenant API keys, audit logs, audit export, privacy self-service, tenant members,
|
||||
tenant notification settings, tenant chatbot settings, AI usage, workflow
|
||||
tenant notification settings, workflow
|
||||
builder/run, portal management, admin email sequences, subscription smoke, authenticated mobile shell,
|
||||
authenticated mobile locale persistence, public auth, and auth-locale flows. The required
|
||||
files must contain the expected guard calls, not only exist: mobile/readiness
|
||||
|
||||
Reference in new issue
Block a user