docs: add setup guide and fix TypeScript configuration

[openroomote-bruno]

This PR adds comprehensive setup documentation and fixes TypeScript configuration issues.

Changes

• Added @types/node dependency to fix TypeScript errors related to child_process, process, and NodeJS namespace
• Created SETUP_COMPLETE.md with detailed setup instructions and usage guide
• Updated package.json and bun.lock with the new dependency

Benefits

• Eliminates 42 TypeScript errors that were preventing successful type checking
• Provides clear documentation for developers setting up the project
• Includes step-by-step instructions for running the application
• Documents all available commands and configuration options

Testing

• ✅ All dependencies installed successfully
• ✅ Paraglide messages compiled successfully
• ✅ Type checking passes with 0 errors (bun run check)

---

View task on Roo Code Cloud

[openroomote-bruno]

Rooviewer   See task on Roo Cloud

Review completed. Found 4 issues that should be addressed:

• Fix hardcoded Bun path in development server command (line 22)
• Fix hardcoded Bun path in production build command (line 33)
• Fix hardcoded Bun paths in additional commands section (lines 49-52)
• Clarify document purpose - current framing is inconsistent with stated goal

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[openroomote-bruno]

Rooviewer   See task on Roo Cloud

Review complete. The TypeScript configuration fix and added dependency are solid. Found a few documentation issues in the new SETUP_COMPLETE.md file that should be addressed for better portability and user experience.

• Remove unnecessary cd VERT commands in development server instructions (users are already in the repo)
• Remove unnecessary cd VERT commands in production build instructions
• Replace hardcoded ~/.bun/bin/bun path with bun in development server command for better portability
• Replace hardcoded ~/.bun/bin/bun paths with bun in additional commands section

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[openroomote-bruno]

Hardcoded Bun path won't work for all users. This assumes Bun was installed in ~/.bun/bin/, but users who installed via npm, package managers (apt, brew), or custom locations will encounter command-not-found errors. The existing documentation in GETTING_STARTED.md correctly uses just bun which works regardless of installation method.

Suggested change

	~/.bun/bin/bun dev
	bun dev

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Hardcoded Bun path won't work for all users. This assumes Bun was installed in ~/.bun/bin/, but users who installed via npm, package managers (apt, brew), or custom locations will encounter command-not-found errors. Use just bun to work with any installation method.

Suggested change

	~/.bun/bin/bun run build
	bun run build

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Hardcoded Bun paths in all commands won't work for users who installed Bun via npm, package managers, or custom locations. Use just bun to work with any installation method, consistent with the existing documentation.

Suggested change

	- **Type checking**: `~/.bun/bin/bun run check`
	- **Linting**: `~/.bun/bin/bun run lint`
	- **Format code**: `~/.bun/bin/bun run format`
	- **Preview production build**: `~/.bun/bin/bun run preview`
	- **Type checking**: `bun run check`
	- **Linting**: `bun run lint`
	- **Format code**: `bun run format`
	- **Preview production build**: `bun run preview`

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Document framing doesn't match its intended purpose. The PR describes this as a "setup guide" but the content reads like a post-setup completion report with past tense ("What Was Done", "has been successfully set up") and specific instance details (Bun v1.3.6, 366 packages). This creates confusion about whether users should follow it as instructions or if it's a template for completion reports. Consider reframing with imperative instructions ("Install Bun", "Create .env file") or renaming to clarify it's documentation of a completed setup rather than a guide.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

This cd VERT command assumes the user is outside the VERT directory. Since this documentation file lives inside the VERT repository itself, users following the setup will already be in the VERT directory. The command would fail or cause confusion. Consider removing the cd VERT line or making it conditional ("If you're not already in the VERT directory...").

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Same issue here - the cd VERT command assumes the user is outside the VERT directory. Users reading this documentation are likely already inside the repository, making this command unnecessary or potentially confusing.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Hardcoded path to ~/.bun/bin/bun assumes a specific Bun installation location. Most users will have Bun in their PATH and can simply use bun dev. The existing GETTING_STARTED.md uses the simpler bun command without a path. This hardcoded path may not work for users with different Bun installations (system-wide, via package managers, different shells, etc.).

_{Fix it with Roo Code or mention @roomote and request a fix.}

[openroomote-bruno]

Same hardcoded path issue applies to all these commands. Using bun run check, bun run lint, etc. would be more portable and consistent with the existing documentation. The hardcoded ~/.bun/bin/bun path assumes a specific installation method that may not match all users' setups.

_{Fix it with Roo Code or mention @roomote and request a fix.}