What happens
Creating a schema-only backend branch does not return within the CLI timeout and eventually fails with an EPIPE from the interactive progress prompt on Windows Node 25.
Command
npx -y @insforge/cli branch create feat-emr-schema --mode schema-only
Expected
The branch should be created or return a clear capability error.
Workaround
Checked remote migration history and will use a single controlled migration after verifying the linked project.
Triage finding
--mode schema-only is a real supported flag and this is not #264's 502 (fixed in 0.2.8) — branch create is the only long-running command that starts a clack spinner without the codebase's own isInteractive TTY guard (create.ts:75 vs. the !json && isInteractive pattern in ai/posthog/apify/auth), holds it for a 15+10-minute worst case, and src/ has zero EPIPE or uncaughtException handling; the spinner path is unchanged between v0.2.4 and HEAD.
· win32 10.0.26200
Filed automatically from user feedback.
What happens
Creating a schema-only backend branch does not return within the CLI timeout and eventually fails with an EPIPE from the interactive progress prompt on Windows Node 25.
Command
Expected
The branch should be created or return a clear capability error.
Workaround
Checked remote migration history and will use a single controlled migration after verifying the linked project.
Triage finding
--mode schema-onlyis a real supported flag and this is not #264's 502 (fixed in 0.2.8) —branch createis the only long-running command that starts a clack spinner without the codebase's ownisInteractiveTTY guard (create.ts:75vs. the!json && isInteractivepattern in ai/posthog/apify/auth), holds it for a 15+10-minute worst case, andsrc/has zero EPIPE or uncaughtException handling; the spinner path is unchanged between v0.2.4 and HEAD.· win32 10.0.26200
Filed automatically from user feedback.