🔧 update: migrate runtime to node.js with bun tooling

[warengonzaga]

Summary

• migrate production execution from Bun to Node.js
• keep Bun for dependency installation, bundling, tests, and tooling
• replace bun:sqlite with better-sqlite3
• align Docker build stages and Node version matrix with wgtechlabs/devin-discord-bot
• prepare the persistent Railway SQLite volume before dropping to the non-root runtime user

Validation

• bun run build
• bun test (59 passing)
• git diff --check

Deployment

Railway production was temporarily rolled back to wgtechlabs/zentrynel:0.11.0 as a hot-patch safety measure. This PR targets main directly per request.

[Copilot]

🟡 Changes recommended

Critical startup and production packaging issues remain unresolved.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Migrates production execution from Bun to Node.js, replaces the SQLite driver, and updates Docker, CI, documentation, and branding.

Changes:

• Adds Node-based production builds and runtime configuration.
• Replaces bun:sqlite with better-sqlite3.
• Updates deployment setup, CI, website content, and branding.

File summaries

File	Description
tsconfig.json	Updates Node-compatible compiler settings.
src/db/sqlite.ts	Replaces Bun SQLite APIs.
src/db/schema.ts	Adapts schema operations to better-sqlite3.
site/zentrynel-icon.svg	Adds branded icon artwork.
site/styles.css	Styles updated website sections.
site/index.html	Updates marketing and setup content.
README.md	Updates database and invite documentation.
package.json	Defines Node production scripts and dependencies.
Dockerfile	Adds multi-stage Node runtime image.
docker-entrypoint.sh	Prepares persistent database storage.
bun.lock	Locks new dependencies.
.github/workflows/build-flow.yml	Adds Node version matrix.

Review details

Suppressed comments (2)

Dockerfile:42

• This healthcheck always exits successfully without inspecting the bot process, so a hung or otherwise unhealthy Node application will still be reported as healthy by the container platform. Use a probe that reflects the bot's actual liveness, or remove this healthcheck instead of publishing a false status.

	CMD node -e "process.exit(0)"

site/index.html:335

• The self-hosting section still advertises Bun >= 1.0 as the runtime (site/index.html:365), but production now launches Node (package.json:8 and Dockerfile:44). That directs deployers to install the wrong runtime; update the runtime label to Node >=22 and show Bun only for the build/tooling steps.

        <li class="setup-step">

• Files reviewed: 8/10 changed files
• Comments generated: 3
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

🔥 Container Build Complete - Patch Build

Build Status: ✅ Success
Flow Type: patch
Description: Hotfix for production

---

📦 Pull Image

Docker Hub: docker pull wgtechlabs/zentrynel:patch-3a4b6db

GHCR: docker pull ghcr.io/wgtechlabs/zentrynel:patch-3a4b6db

---

📋 Build Details

Property	Value
Flow Type	patch
Commit	7346699
Registry	Docker Hub + GHCR

🏷️ Image Tags

• wgtechlabs/zentrynel:patch-3a4b6db
• ghcr.io/wgtechlabs/zentrynel:patch-3a4b6db

---

🔍 Testing Your Changes

1. Pull the image using one of the commands above
2. Run the container with your test configuration
3. Verify the changes work as expected
4. Report any issues in this PR

---

🚀 Quick Start

# Pull and run the container
Docker Hub: docker pull wgtechlabs/zentrynel:patch-3a4b6db
docker run <your-options> <image>

---

---

🔒 Security Scan Results

📋 Pre-Build Security Checks

✅ Source Code Scan: 0 vulnerabilities found
✅ Dockerfile Scan: 0 misconfigurations found

🐳 Container Image Vulnerabilities

Severity	Count
Total	0

📊 Detailed Security Reports

View detailed vulnerability reports in the GitHub Security tab.

---

_{🤖 Powered by Container Build Flow Action vfb5c0662b33f7702bc1ccf85350689436989f606
💻 with ❤️ by Waren Gonzaga under WG Technology Labs, and Him 🙏}