refactor(ci): drop "canary-" prefix → staging-smoke/staging-verify (Hongming directive 2026-05-11) #443

Merged

core-lead merged 7 commits from refactor/drop-canary-prefix into main 2026-05-11 11:25:37 +00:00

Conversation 6 Commits 7 Files Changed 15 +183 -133

7 Commits

Author	SHA1	Message	Date
claude-ceo-assistant	6aee63e908	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 11:12:51 +00:00
Molecule AI · core-lead	83b2652368	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 10:53:32 +00:00
claude-ceo-assistant	3ec205147f	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 10:38:23 +00:00
Molecule AI · core-lead	86c2ef49ab	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 10:27:00 +00:00
Molecule AI · core-lead	7cd9bbe3c3	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 10:07:02 +00:00
Molecule AI · core-lead	88ad71706f	Merge branch 'main' into refactor/drop-canary-prefix	2026-05-11 09:56:52 +00:00
claude-ceo-assistant	f6cc29ca2e	refactor(ci): drop "canary-" prefix → staging-smoke/staging-verify ... Per Hongming directive 2026-05-11 09:08Z: "canary naming changed to staging for all, if there are some left overs should change too." The "canary-" prefix was a redundant modifier on workflow files that already targeted staging. The deployment-STRATEGY concept (a small subset of staging tenants gets the new image first, the rest follow on green) stays — only the workflow IDENTITY and the secret store keys feeding it are renamed. ## Renamed surfaces Files (git mv preserves history): - .gitea/workflows/canary-staging.yml → staging-smoke.yml - .gitea/workflows/canary-verify.yml → staging-verify.yml - scripts/canary-smoke.sh → scripts/staging-smoke.sh Secret-store keys (consumed by .gitea/workflows/staging-verify.yml + scripts/staging-smoke.sh — secrets don't exist in any store yet, so this rename is rename-first-safe per the audit Section C "truly missing" classification): - secrets.CANARY_TENANT_URLS → secrets.MOLECULE_STAGING_TENANT_URLS - secrets.CANARY_ADMIN_TOKENS → secrets.MOLECULE_STAGING_ADMIN_TOKENS - secrets.CANARY_CP_SHARED_SECRET → secrets.MOLECULE_STAGING_CP_SHARED_SECRET Env flag (test_staging_full_saas.sh + the 2 workflows that invoke it): - E2E_MODE=canary → E2E_MODE=smoke (legacy "canary" alias retained for one rollout cycle; remove after one week of no-old-value observations) Slug prefix (test_staging_full_saas.sh + teardown safety nets in staging-smoke.yml + e2e-staging-sanity.yml): - e2e-canary-{date}-* → e2e-smoke-{date}-* (dual-prefix fallback in both teardown nets for one rollout cycle so any in-flight org from an older runner checkout still cleans up) Concurrency group + workflow name + step / job names: - concurrency.group: canary-staging → staging-smoke - name: "Canary — staging SaaS smoke" → "Staging SaaS smoke" - name: "canary-verify" → "Staging verify" - job: canary → smoke - job: canary-smoke → staging-smoke - step: "Canary run" → "Smoke run" - step: "Run canary smoke suite" → "Run staging smoke suite" Script-internal: - CANARY_ACURL_PATH helper var → ACURL_PATH Cross-references updated: - e2e-staging-saas.yml + e2e-staging-sanity.yml + publish-canvas-image.yml + continuous-synth-e2e.yml + sweep-stale-e2e-orgs.yml + both redeploy-tenants-on-*.yml comment refs to the renamed workflows - docs/architecture/canary-release.md + tests/e2e/STAGING_SAAS_E2E.md + scripts/README.md + runbooks/gitea-actions-migration-checklist.md ## Out of scope (deliberate) - CANARY_SLUG / CANARY_PROMOTE_* in redeploy-tenants-on-*.yml: this is the soak-deploy canary slug (one-tenant-first-then-fan-out), a different concept than the renamed smoke workflow. Stays. - .github/workflows/ tree: dormant mirror per reference_molecule_core_actions_gitea_only — Gitea Actions reads .gitea/ only. Sweep cleanup is a separate follow-up. - Alert issue title "Canary failing: staging SaaS smoke" in staging-smoke.yml: kept stable so any open alert from the pre-rename filename still title-matches the auto-close search on next green. ## Verification - grep -rn "CANARY_\|canary-staging\|canary-verify\|E2E_MODE=canary" .gitea/ scripts/ tests/ docs/ runbooks/ — remaining matches are intentional (deployment-strategy CANARY_SLUG concept, historical rename notes with "formerly" qualifier, soak-canary vars). - yaml.safe_load() parses all 9 touched workflow files clean. - bash -n on scripts/staging-smoke.sh and tests/e2e/test_staging_full_saas.sh. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-11 02:28:46 -07:00