Docs/DX: very long --issue text hits the Windows command-line limit with a cryptic OS error; point users at --issue-file / stdin

[aryamthecodebreaker]

Found while stress testing the CLI on Windows (v0.9.0). Low priority / docs nit.

What happens

On Windows, passing a very large --issue string inline fails before Node even starts, with a cryptic OS error:

node : Program 'node.exe' failed to run: The filename or extension is too long

Reproduced with a ~100 KB --issue. This is the Windows CreateProcess command-line limit (~32 KB), not a FixMap bug - but nothing in the CLI output or docs points Windows users at the escape hatch.

Suggestion

• Document on the get-started / docs page (and in --help for --issue): for long task text, use fixmap plan --issue-file task.md or pipe it via fixmap plan --issue -.
• Optionally, if argv parsing ever fails at startup on win32 with ERROR_FILENAME_EXCED_RANGE-style symptoms, print a hint pointing to --issue-file / stdin.

FixMap already handles large issue text fine once it gets it: a 5 MB --issue-file planned successfully in ~10s.