How to Build a SaaS MVP with AI on Adios

Help me plan a small SaaS MVP in this Adios workspace. Do not edit any files yet.

The product:
- Name: [SAAS NAME]
- Customer: [ONE TYPE OF CUSTOMER]
- Problem: [ONE COSTLY OR FRUSTRATING PROBLEM]
- Core result: [WHAT THE CUSTOMER CAN FINISH]
- Roles: [OWNER, MEMBER, OR OTHER REQUIRED ROLES]

For the first version, include only:
- account sign-in;
- one workspace or team per customer;
- [THE ONE CORE WORKFLOW];
- an owner view and a member view;
- a simple plan field, without live billing; and
- a clear empty state and sample data for testing.

Leave these for later:
- [FEATURE 1];
- [FEATURE 2]; and
- live subscription charging.

First inspect the current source, framework, tests, database setup, and adios.yaml. Then give me:
1. a plain-language user journey;
2. the smallest data model;
3. the tenant and permission boundaries;
4. the pages or API routes you would change;
5. the checks you will run; and
6. any decision you need from me.

Wait for my approval before editing.

Implement the SaaS MVP from the plan I approved.

Requirements:
- Keep the current framework, package manager, health route, and Adios deployment setup.
- Preserve adios.yaml and explain any required change before making it.
- Use the project's established authentication approach. Do not invent password storage or cryptography.
- Enforce the team boundary in server-side data access, not only by hiding interface controls.
- Store persistent records in the configured database and add reversible migrations when the project uses migrations.
- Give new accounts a useful empty state and provide clearly labelled development seed data.
- Treat the plan field as product state only. Do not connect live payments in this increment.
- Keep secret values out of source. Refer to required values by environment-variable name.
- Do not invent testimonials, customer logos, usage numbers, revenue, or security certifications.
- Add or update tests for the core workflow and for one user attempting to access another team's data.
- Run the existing formatter, lint, test, and build commands.

When finished, show me:
1. the changed files;
2. the data and permission model;
3. the test results;
4. environment variables I must configure in Adios; and
5. a manual Preview checklist.

Do not deploy to production.

Plan a separate test-mode billing increment for this SaaS. Do not edit or deploy yet.

Use the payment provider I confirm: [PROVIDER]. Use its current official SDK and hosted checkout or billing portal where appropriate. Never collect or store raw card details in this app.

The plan must cover:
- the product and price identifiers stored as configuration;
- test-mode checkout;
- signed webhook verification;
- idempotent event handling;
- subscription state transitions and failed payments;
- which features, if any, are gated by server-side authorization;
- cancellation and billing-portal behavior;
- secret names to configure in Adios; and
- automated and manual test cases.

List the tax, refund, privacy, support, and pricing decisions that remain my responsibility. Wait for my approval before changing files.

Perform a final release review of this SaaS MVP. Fix only confirmed problems and do not deploy.

Verify:
- a new customer can create an account and finish the core workflow;
- team data cannot be read or changed by another team;
- owner-only actions are enforced on the server;
- empty, loading, validation, forbidden, and error states are understandable;
- database migrations and seed behavior are safe for the target environment;
- no token, password, private key, or connection string is committed;
- the health route and existing Adios deployment configuration still work;
- the existing formatter, lint, tests, and production build pass; and
- live billing is disabled unless I separately approved and configured it.

Return the evidence, remaining risks, required Adios secrets, and a manual production checklist. Stop before deployment for my approval.