forked from molecule-ai/molecule-core
claude-ceo-assistant
8f1d24f33f
Re-applies PR#462 on current main (PR#443 merged first and renamed canary-staging.yml -> staging-smoke.yml, conflicting #462). Swept 6 files (15 secret-ref flips): - .gitea/workflows/staging-smoke.yml (3 refs + drop continue-on-error + add notify-on-failure step) - .gitea/workflows/e2e-staging-saas.yml (3 refs) - .gitea/workflows/e2e-staging-sanity.yml (3 refs) - .gitea/workflows/e2e-staging-canvas.yml (3 refs) - .gitea/workflows/e2e-staging-external.yml (3 refs) - tests/e2e/STAGING_SAAS_E2E.md (1 heading flip + 1 historical-rename breadcrumb) Each workflow keeps one inline breadcrumb comment pointing back to the old name and internal#322. staging-smoke is the 30-min canary cadence for the entire staging SaaS stack; silent failure (continue-on-error: true) masked exactly the regressions the smoke exists to surface, same class as PR#461 (`sweep-stale-e2e-orgs`). Dropped continue-on-error from the smoke job + added a fail-loud `if: failure()` Notify step mirroring PR#461. The four other `e2e-staging-*` workflows KEEP continue-on-error: true per RFC #219 §1 — they are advisory. Excluded from this PR: - .gitea/workflows/sweep-stale-e2e-orgs.yml (PR#461 owns) - .gitea/workflows/staging-verify.yml (only references the plural MOLECULE_STAGING_ADMIN_TOKENS canary-fleet secret, out of scope) - scripts/staging-smoke.sh (same — plural only) - docs/architecture/canary-release.md (same — plural only) - .github/ mirror tree (separate scope per reference_molecule_core_actions_gitea_only) Verified locally: yaml.safe_load clean on all 5 workflows; grep returns ZERO non-breadcrumb references in the swept files; the plural MOLECULE_STAGING_ADMIN_TOKENS references in staging-verify.yml / scripts/staging-smoke.sh / canary-release.md are intentionally untouched. Refs: internal#322, PR#461, feedback_rename_pr_and_edit_pr_conflict_sequence