feat: add dory CLI tool with build and preview commands

[hkdeman]

Implements the requested Dory CLI tool for building and previewing documentation sites.

Changes

• Updated package.json for npm publishing with proper metadata
• Created CLI entry point at bin/dory.js with build and preview commands
• Updated README.md with CLI installation and usage instructions

Resolves #14

Generated with Claude Code

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Command Injection in log message	High	Create a dory.json file with a malicious name field like "name": "$(touch /tmp/pwned)". Run dory build.	The console.log statement in bin/dory.js is vulnerable to command injection if the name field in dory.json contains shell commands.
Missing Input Sanitization	Medium	Create a file named -rf. Run dory build.	bin/dory.js blindly executes rmSync(docsDir, { recursive: true, force: true });. If docsDir were to be crafted to be -rf, it could have unintended consequences.
Confusing instructions in README.md	Low	Follow the instructions in "3️⃣ Copy Documentation Content".	The instructions suggest running rm -rf ./docs && cp ../wherever-the-docs-are/. ./docs. Since the dory build command already handles clearing and preparing the docs folder, this step is redundant when using the CLI. Also, the command cp ../wherever-the-docs-are/. ./docs is dangerous because of the dot after wherever-the-docs-are/. It should be cp -r ../wherever-the-docs-are ./docs.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Incorrect working directory for npm run build	Critical	Run dory build in a Dory project.	The npm run build command is executed in the Dory CLI's installation directory instead of the user's project directory, causing the build to fail.

_{Comments? Email us.}