Skip to content

Add Pay-as-you-go billing & usage settings screen (mock UI)#6503

Open
reecebrowne wants to merge 2 commits into
mainfrom
feat/payg-settings-screen
Open

Add Pay-as-you-go billing & usage settings screen (mock UI)#6503
reecebrowne wants to merge 2 commits into
mainfrom
feat/payg-settings-screen

Conversation

@reecebrowne
Copy link
Copy Markdown
Contributor

Adds the Pay-as-you-go (PAYG) billing & usage settings screen as a mock UI, wired into the SaaS config nav. All data is mocked via usePaygMock; no backend yet. PaygSnapshot defines the intended API contract. Demo hooks (?payg=1) allow previewing in the proprietary build and must be removed before merge.

@dosubot dosubot Bot added size:XXL This PR changes 1000+ lines ignoring generated files. enhancement New feature or request labels Jun 1, 2026
@stirlingbot stirlingbot Bot added Front End Issues or pull requests related to front-end development and removed enhancement New feature or request labels Jun 1, 2026
Comment on lines +106 to +107
state === "DEGRADED"
? ["CLIENT_SIDE"]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Degraded-state enabledGates excludes OFFSITE_PROCESSING, but the new cap policy says only AI/AUTOMATION pause. This contradiction can yield wrong gate behavior when enabledGates is used.

Suggested change
state === "DEGRADED"
? ["CLIENT_SIDE"]
state === "DEGRADED"
? ["CLIENT_SIDE", "OFFSITE_PROCESSING"]
Details

✨ AI Reasoning
​​1) The new section models cap-reached behavior in two places: the mocked snapshot state and the gate behavior description.
​2) In degraded mode, the snapshot enables only CLIENT_SIDE, which excludes OFFSITE_PROCESSING.
​3) Elsewhere, the behavior table and user-facing copy state that OFFSITE_PROCESSING should continue working at cap, with only AI and automation pausing.
​4) This creates contradictory assumptions in the same feature and can produce incorrect behavior once enabledGates is consumed.

Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info

@reecebrowne reecebrowne force-pushed the feat/payg-settings-screen branch from 4e6b4f8 to 86bc9f5 Compare June 1, 2026 12:22
@reecebrowne reecebrowne force-pushed the feat/payg-settings-screen branch from 86bc9f5 to 058f6d6 Compare June 1, 2026 13:04
@stirlingbot
Copy link
Copy Markdown
Contributor

stirlingbot Bot commented Jun 3, 2026

🚀 V2 Auto-Deployment Complete!

Your V2 PR with embedded architecture has been deployed!

🔗 Direct Test URL (non-SSL) http://54.175.155.236:6503

🔐 Secure HTTPS URL: https://6503.ssl.stirlingpdf.cloud

This deployment will be automatically cleaned up when the PR is closed.

🔄 Auto-deployed for approved V2 contributors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Front End Issues or pull requests related to front-end development size:XXL This PR changes 1000+ lines ignoring generated files. Translation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants