Jason Stirnaman e4a659b269 fix: write logs to stderr to avoid interfering with piped output ... Change log() function to use console.error instead of console.log. This ensures that when stdout is piped (e.g., to 'code -'), only the prompt file path is sent through the pipe, while progress messages remain visible on the terminal via stderr. Usage: echo 'content' | yarn --silent docs:create --products X | code -		2025-11-01 10:24:55 -05:00
..
lib	refactor: simplify link following behavior - treat relative paths as local files, all HTTP/HTTPS as external	2025-10-31 15:05:17 -05:00
schemas	chore(scripts): docs:create and docs:edit scripts for content creation and editing	2025-10-27 23:43:08 -04:00
templates	chore(scripts): docs:create and docs:edit scripts for content creation and editing	2025-10-27 23:43:08 -04:00
README-add-placeholders.md	chore(scripts): docs:create and docs:edit scripts for content creation and editing	2025-10-27 23:43:08 -04:00
add-placeholders.js	chore(scripts): docs:create and docs:edit scripts for content creation and editing	2025-10-27 23:43:08 -04:00
docs-create.js	fix: write logs to stderr to avoid interfering with piped output	2025-11-01 10:24:55 -05:00
docs-edit.js	chore(scripts): docs:create and docs:edit scripts for content creation and editing	2025-10-27 23:43:08 -04:00