1.8 KiB
1.8 KiB
Why
AI provider setup currently exposes implementation fields such as provider ID, Base URL, models, timeout, and redaction policy as the primary workflow. This is too noisy for normal provider onboarding and makes operators fill fields that the platform can derive from a provider preset. The magical-girl theme also becomes visually harsh when a user-uploaded background is active because the custom-background overrides reintroduce high-saturation pink/gold overlays on already busy imagery.
What Changes
- Simplify AI provider onboarding so the normal path is provider kind plus platform secret reference, with provider ID generated automatically.
- Move Base URL, model list, default model, relay mode, timeout, and redaction policy into an advanced section with provider-specific defaults.
- Preserve the platform boundary: the frontend manages secret references and does not persist or display raw API keys.
- Require AI provider management API routes to use platform administrator authentication.
- Reduce magical-girl custom-background surface saturation, frame accessory opacity, and pink/gold glow while keeping the crystal-moonlight visual direction.
- Document the local debug port discipline: use
scripts/local-debug-start.shand the documentedLOCAL_DEBUG_*overrides instead of starting ad hoc ports.
Impact
- Affected roots:
platform/,platform_web/,docs/,openspec/. - Expected files: AI provider API handlers/tests, AI provider frontend contracts/schema/page/tests, shared theme CSS/tests/readme, local-debug docs.
- No billing, cloud host sales, provider marketplace, direct run socket, plugin credential, or unrelated SaaS behavior changes.
- Verification: focused backend/frontend tests,
scripts/check-structure.sh,openspec validate polish-ai-provider-onboarding --strict, and browser walkthrough against the existing local debug stack.