v1.2.1

Patch release fixing three real bugs hit on first downstream consumption of v1.2.0. All three were filed as [downstream-report] issues on the same day v1.2.0 shipped.

Fork-maintained files you must update

Backfilled 2026-06-02 per the convention added in #373 — the typecheck-rename warning was previously buried inside the "Changed" section. Lifted here for visibility; the original "Changed" entry remains for historical accuracy.

• Branch-protection ruleset on main (and any fork's main) — v1.2.1 renamed the CI job typecheck → version-parity. Branch-protection rulesets that mirror upstream's required-status-check name still listing typecheck will block PRs forever — the new workflow reports version-parity, not typecheck. Edit required: rename typecheck → version-parity in your ruleset's required-checks list (or remove typecheck if you don't want the new name required). Applies to both the repo-level ruleset on vibeacademy/gembaflow AND any org-level ruleset that targets gembaflow-family repos. This bit at least one PR after the v1.4.0 series (see gembaflow#399 on 2026-06-02 — same drift, still unfixed at the org-ruleset level).
• features/ BDD tests — v1.2.1 added features/ to syncDirectories, so forks now receive clean upstream features/* files. Forks that have customized their own features/*.{py,feature} files should add the affected paths to .gembaflow-overrides BEFORE running this /upgrade — otherwise the customizations are overwritten.

Fixed

• template-sync.sh now bumps package.json version alongside .gembaflow-version (#361). Previously, every sync PR landed with red CI because validate-version-parity.sh found the two version sources disagreeing. The fix uses jq (with a python3 fallback) to update package.json only if its version differs from the new release. Idempotent; skipped on non-Node forks. (#365)
• features/ directory added to syncDirectories (#362). Downstream forks bootstrapped before the rebrand had stale features/* files referencing .agile-flow-version that /upgrade never touched, causing the BDD suite to fail post-sync. Future /upgrade runs now refresh these files. (#364)
• .claude/agents/*.md now classified as hybrid with FRAMEWORK markers (#363). Previously bootstrap-agents and template-sync.sh silently contradicted each other — every sync wiped out project-specific agent specialization. Now template-sync.sh only updates content between <!-- FRAMEWORK:START --> and <!-- FRAMEWORK:END --> markers; user-supplied specialization outside markers is preserved. (#366)

Changed

• CI job renamed typecheck → version-parity (#361). The job had been misleadingly named typecheck — it never ran tsc, only the version-parity check. The real TypeScript tsc --noEmit lives in the node job and is unchanged.

  ⚠ Branch protection action required for consumers: if you have a fork with branch protection that mirrors upstream, the required-status-check named typecheck now needs to be renamed to version-parity in your ruleset. Otherwise sync PRs against your fork will block on a check that no longer exists.

Added

• bootstrap-agents skill updated with one-shot migration logic: when run on a legacy agent file (no markers), wraps the framework persona content in markers and appends project specialization after. Forks that ran bootstrap-agents before this release should re-run it once to gain marker protection. (#366)

Migration notes

After /upgrade against this release:

• Existing .claude/agents/*.md files without <!-- FRAMEWORK:* --> markers are preserved entirely (preserve-and-warn behavior). The sync PR includes a [!WARNING] callout listing those files and recommending /bootstrap-agents to gain marker protection.
• features/*.{py,feature} files with .agile-flow-version literals (a leftover from pre-rebrand bootstrap) will be replaced by the clean upstream versions. Forks that have customized their own feature tests should add features/<file> to .gembaflow-overrides to protect them before the sync.
• Sync PRs land green on CI. The version-parity job verifies .gembaflow-version and package.json agree; template-sync.sh writes both, so they always do.

Downstream-report status

#352 (the original consolidated downstream-report against v1.1.0) was resolved by v1.2.0. This release picks up the three separate reports filed against v1.2.0 itself by the same consumer (vibeacademy/gembaflow-site): #361, #362, #363.