1dfeb13a72
Some checks failed
Sync dev → Gitea / Mirror dev to Gitea (push) Has been cancelled
Fusion is allowed to ship to dev.sase.tr (staging) only — the user owns the dev→main GitHub merge that promotes to production. Heartbeat-created tasks kept hallucinating prod deploys / monitoring (FN-291 / 315 / 323 / 324 / 311 etc.), and an entire e2e suite targeting live sase.tr was merged under FN-320 with hardcoded test creds. Changes: - Add "Project-wide rule: Fusion ships to dev.sase.tr only" block to all 7 agent personas (ceo/cto/cpo/designer/qa/backend-eng/frontend-eng). - Add /AGENTS.md at project root as the canonical rule (loaded once pi-markdown-workflows is reinstalled in the container). - Remove production-targeted e2e suite under apps/web/e2e/ (auth.setup.ts, deployment-audit.cjs, p0-subscription-cro.spec.ts, p0-subscription-cro-verify.cjs, playwright.config.ts, screenshots/). - Remove docs/product/funnel-monitoring-p0-cro-post-deploy-2026-05.md (prod-monitoring deliverable, out-of-scope). - Subscription downgrade-offer dialog: avoid mobile-viewport overflow by capping width at calc(100vw - 2rem) below sm breakpoint (formerly attempted in failed/duplicate FN-291/295).