From 0f7b018d4dc1b453b11d76eecea3f100c2335619 Mon Sep 17 00:00:00 2001 From: Tom Boucher Date: Thu, 14 May 2026 19:03:42 -0400 Subject: [PATCH] chore: changeset for fix/3523 (branching_strategy false warning) Co-Authored-By: Claude Sonnet 4.6 --- .changeset/sunny-pandas-dance.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .changeset/sunny-pandas-dance.md diff --git a/.changeset/sunny-pandas-dance.md b/.changeset/sunny-pandas-dance.md new file mode 100644 index 000000000..782c550d0 --- /dev/null +++ b/.changeset/sunny-pandas-dance.md @@ -0,0 +1,5 @@ +--- +type: Fixed +pr: 3523 +--- +**Top-level `branching_strategy` in `.planning/config.json` no longer triggers a false "unknown config key" warning** — `loadConfig` in `core.cjs` actively read the key via its nested fallback (`git.branching_strategy`) but the `KNOWN_TOP_LEVEL` allowlist was built from dot-notation paths via `.split('.')[0]`, turning `'git.branching_strategy'` into `'git'` instead of `'branching_strategy'`. The fix adds a self-healing on-disk migration (mirroring the existing `multiRepo → planning.sub_repos` precedent): on first `loadConfig`, the top-level key is grafted into `git.branching_strategy` and the stale top-level entry is removed. A module-level deduplication Set also prevents the same unknown-key warning from appearing twice when `loadConfig` is invoked multiple times in a single CLI call. A contract test asserts CJS and SDK agree on legacy-shape fixtures. (#3523)