v1.2.0

The Gemba Flow rebrand release. v1.1.0 was the redirect-safety enabler that let the GitHub repo rename happen transparently; v1.2.0 ships the rest of the rebrand — package names, env vars, dotfile names, all URLs, agent footers, workshop docs.

Migration on first /upgrade

When you run /upgrade against this release, scripts/template-sync.sh will:

1. Auto-rename your dotfiles (one-time, idempotent):
   • .agile-flow-version → .gembaflow-version
   • .agile-flow-meta/ → .gembaflow-meta/
   • .agile-flow-overrides → .gembaflow-overrides
2. Sync the new framework files (which now reference .gembaflow-* natively — no dual-read fallback as of v1.2.0).

The migration step prints INFO: migrating <old> -> <new> for each rename. No-ops if you're already on the new names.

If you set AGILE_FLOW_* env vars

AGILE_FLOW_WORKER_ACCOUNT, AGILE_FLOW_REVIEWER_ACCOUNT, AGILE_FLOW_SOLO_MODE still work via the dual-read shim in scripts/lib/env-compat.sh — you'll see a one-line stderr deprecation warning when they're the only thing set. Rename them to GEMBAFLOW_* in your shell rc / Codespaces secrets / devcontainer at your convenience.

Fork-maintained files you must update

Backfilled 2026-06-02 per the convention added in #373 — this section was missing from the original release notes. Reconstructed from the gembaflow-site session journal that surfaced the breakage.

• features/ BDD tests on forks bootstrapped before the rebrand — v1.2.0 removed the Phase 4 dual-read fallback in scripts/report-issue.sh (and 5 other scripts). Forks whose features/*.{py,feature} files still reference .agile-flow-version literals broke 12 BDD scenarios post-/upgrade. Edit required: either delete the affected features/ fixtures and let v1.2.1's expanded syncDirectories (which now includes features/) refresh them on the next sync, or rewrite the literals to .gembaflow-version immediately. gembaflow-site was bitten by this on 2026-05-28.
• None other. Dotfile renames (.agile-flow-version → .gembaflow-version, etc.) and env-var renames (AGILE_FLOW_* → GEMBAFLOW_*) are handled by template-sync.sh's migration step and the env-compat shim respectively — no manual edit required for those.

Changed

• Package metadata: package.json name: agile-flow-starter → gembaflow-starter. pyproject.toml name: agile-flow → gembaflow. description: "Gemba Flow Framework". (#347)
• Dotfiles renamed (with auto-migration step on first /upgrade): .agile-flow-version → .gembaflow-version, .agile-flow-meta/ → .gembaflow-meta/, .agile-flow-overrides → .gembaflow-overrides. Sync branch prefix agile-flow-sync/v… → gembaflow-sync/v…. (#348)
• Env vars now read GEMBAFLOW_* first, fall back to AGILE_FLOW_* with deprecation warning. Helper at scripts/lib/env-compat.sh. (#346)
• URL references and agent source footers now natively reference vibeacademy/gembaflow. Old URLs continue to work via GitHub's 301 redirect for legacy clones. (#345)
• scripts/template-sync.sh: UPSTREAM_REPO="vibeacademy/gembaflow" (was vibeacademy/agile-flow); FALLBACK_REPO="vibeacademy/agile-flow" defensive belt-and-suspenders. (#345)
• Workflow guards in deploy.yml, preview-deploy.yml, preview-cleanup.yml: if: github.repository != 'vibeacademy/gembaflow' (was agile-flow) — without this, the template repo would have started running preview/deploy CI on its own PRs after the rename. (#345)

Added

• upstream field auto-normalized in .gembaflow-version from full URL or bare owner/repo (Phase 0.5 capability, formalized in v1.2.0 docs).
• Migration step in template-sync.sh that git mvs legacy dotfiles to new names on first sync after upgrade. Kept indefinitely for dormant forks. (#348)

Removed

• Phase 4 dual-read fallback removed across 6 scripts (template-sync.sh, report-issue.sh, doctor.sh, lib/overrides.sh, validation/validate-version-parity.sh, bootstrap.sh). Net -60 LOC. Forks on .agile-flow-* paths must run /upgrade once to trigger the migration step before scripts will function. (#359)

Fixed

• Pre-push hook: scripts/hooks/pre-push now runs uv run --extra dev pytest and uv run --extra dev ruff check. Without --extra dev, fresh contributors' first push failed with Failed to spawn: pytest. (#350, closes #341)
• template-cleanliness CI check: removed vibeacademy/agile-flow-gcp test fixture references that tripped \bgcp\b rule; replaced with generic vibeacademy/example-variant. (#348)
• BDD tests: reports-dir assertions updated to .gembaflow-reports/ so the test suite passes against the renamed dotfiles. (#348, #359)
• #352 downstream-report — three v1.1.0 bugs (scripts/report-issue.sh hardcoded paths, template-cleanliness violations, BDD assertion mismatch) all resolved on this release.

Upgrade notes

After running /upgrade against this release:

• First-time migration: expect INFO: migrating .agile-flow-version -> .gembaflow-version (and similar lines) in the sync output. The renames go into the sync PR alongside the framework file updates.
• If your .agile-flow-version had an upstream field, it's preserved (the rename is a git mv, not a recreate). Downstream variant forks (e.g. gembaflow-gcp) that point at their own upstream continue working.
• AGILE_FLOW_* env vars: still work, but rename at your convenience to silence the deprecation warning. Future minor release will drop the shim.
• Reviewer bot PAT: if you provisioned one before v1.0.11, it may be missing the project scope. Remediate with gh auth refresh --user {org}-reviewer --scopes repo,workflow,project,gist,read:org. (See .claude/README.md "Remediation" section.)

Rebrand epic

The agile-flow → Gemba Flow rebrand is now structurally complete: gembaflow-meta#96 (closed). v1.2.0 is the shipping artifact for that work.