chore(drift-sync): needs-human model-family decision (2026-08-14)

[copilotkit-bot]

Needs a human decision (drift-sync)

The deterministic, zero-LLM drift-sync found a model-family change it must
NOT auto-apply (a genuinely new/unclassified family, or a registry
structural mismatch). It wrote the note file(s) below and opened this PR so
the decision is REACHABLE in the repo.

Not auto-merged — a human decides. For a new-family note: set the
note's decision line to Decision: include (to classify it) or delete the
note / close this PR (to reject), then merge this PR. The NEXT drift-sync
run reads the approved note from main and mechanically applies the registry
edit (still zero-LLM — a human-authored marker, not generated code), opening a
separate data-only PR. That two-run hand-off is how the loop closes.

Note file(s) in this PR

• drift-proposals/gemini-gemini-3.7-flash-new-family.md

drift-sync outcome

npm warn Unknown project config "minimum-release-age". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "block-exotic-subdeps". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
needs-human note(s) written this run — routed to human without a live re-collect (no registry edit to re-verify)
  [needs-human-new-family] gemini/gemini-3.7-flash: "gemini-3.7-flash" is unclassified — routed to human (drift-proposals/gemini-gemini-3.7-flash-new-family.md)
npm warn Unknown env config "block-exotic-subdeps". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown env config "minimum-release-age". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "minimum-release-age". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "block-exotic-subdeps". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
�[33m[STARTED]�[39m Backing up original state...
�[32m[COMPLETED]�[39m Backed up original state in git stash (ea47089)
�[33m[STARTED]�[39m Running tasks for staged files...
�[33m[STARTED]�[39m package.json�[0;90m — 1 file�[0m
�[33m[STARTED]�[39m *.{ts,mts,js,mjs,cjs,json,html,css,md}�[0;90m — 1 file�[0m
�[33m[STARTED]�[39m *.{ts,mts,js,mjs}�[0;90m — 0 files�[0m
�[33m[SKIPPED]�[39m *.{ts,mts,js,mjs}�[0;90m — no files�[0m
�[33m[STARTED]�[39m prettier --write
�[32m[COMPLETED]�[39m prettier --write
�[32m[COMPLETED]�[39m *.{ts,mts,js,mjs,cjs,json,html,css,md}�[0;90m — 1 file�[0m
�[32m[COMPLETED]�[39m package.json�[0;90m — 1 file�[0m
�[32m[COMPLETED]�[39m Running tasks for staged files...
�[33m[STARTED]�[39m Applying modifications from tasks...
�[32m[COMPLETED]�[39m Applying modifications from tasks...
�[33m[STARTED]�[39m Cleaning up temporary files...
�[32m[COMPLETED]�[39m Cleaning up temporary files...
[fix/drift-2026-08-14-31777041713 5b42042] fix(drift-sync): mechanical model-family sync (needs-human note file(s))
 1 file changed, 14 insertions(+)
 create mode 100644 drift-proposals/gemini-gemini-3.7-flash-new-family.md
unchecked-providers=
reason=needs-human
changeset-key=811e6c6dc03dc3aa

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@copilotkit/aimock@376

commit: 5b42042

[jpr5]

Superseded by #378, which classifies both families: gemini-3.7-flash included, gemini-3.7-flash-video-understanding-eap excluded as gated pre-GA. Both notes are resolved and both checksum pins re-frozen there.

Note the procedure in this PR's body was wrong: Decision: include + merge reds its own gate, because adding to includeFamilies moves the checksum pin and drift-sync's allowlist bars it from re-pinning. #378 corrects that text and pins the correction with a test.