Add pd new command to bootstrap entry point files

[Copilot]

Implements pd new command for scaffolding new pipedown entry points with configurable templates.

New Command

pd new myPipe                      # script/lib entry point
pd new --type server myServer      # server entry point + wrapper
pd new --type cli myCli            # CLI entry point + wrapper
pd new --clean myLib               # minimal template with build config only
pd new --template myWrapper        # wrapper .ts importing index.ts

Changes

• pdCli/newCommand.ts — Command implementation with type validation, file existence checks, and template selection
• stringTemplates.ts — Added pdNewScriptTemplate, pdNewServerMdTemplate, pdNewCliMdTemplate, pdNewCleanTemplate, pdNewWrapperTemplate
• pdCli/mod.ts — Registered command with checkFlags(["new", "*"], newCommand), added --clean, --template, --type flags
• pdCli/helpCommand.ts — Updated help text

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dl.deno.land
  • Triggering command: /usr/bin/curl curl -s REDACTED (dns block)
  • Triggering command: /usr/bin/curl curl --fail --location --progress-bar --output /home/REDACTED/.deno/bin/deno.zip REDACTED (dns block)
• jsr.io
  • Triggering command: /home/REDACTED/.deno/bin/deno deno lint (dns block)
  • Triggering command: /home/REDACTED/.deno/bin/deno deno run -A /home/REDACTED/work/pipedown/pipedown/pdCli/mod.ts new --help (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add command to bootstrap/init new entrypoint files</issue_title>
<issue_description>pd new <name>
New entry point file (and maybe a wrapper)
Select from:

• script / lib (templated script entry point .md file with preconfiguration to export an esm file into the same directory next to the entry point .md)
• server (merely copies a templated server.ts into the same directory along with an index.md)
• cli (merely copies a templated cli.ts into the same directory along with an index.md)
• ... any other global templates

pd new --clean <name>
Same as without the --option but inits totally empty files save for the default export configuration to ensure build outputs are written to the current dir (next the entry point)

pd new --template <file>
make the target file a template that will import the index.ts from the same directory</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add command to bootstrap/init new entrypoint files #11

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.