docs(docker): clean up on-prem runbooks

[pascalandr]

Summary

Isolates Docker/on-prem runbook cleanup: Docker ignore/build/compose updates, static Den on-prem runbook/README corrections, and portable Den demo seed tooling for disposable E2E setups.

Verification

• docker compose -f packaging/docker/docker-compose.yml config — passed.
• docker compose -f packaging/docker/docker-compose.den-dev.yml config — passed.
• pnpm --filter @openwork-ee/den-api exec node --check scripts/seed-demo-org-runner.mjs — passed.
• pnpm --filter @openwork-ee/den-api exec node --import tsx -e "console.log('tsx import ok')" — passed.
• pnpm --filter @openwork-ee/den-api build — passed.
• Fresh Proxmox E2E on VM 151 used the seed script successfully without printing the password.
• git diff --name-status upstream/dev...pr/docker-onprem-runbook reviewed; no tasks/**, docs/scrs/**, codemaps, or generated app-version included.

Known risks

• Compose config output includes documented placeholder/dev tokens only; no real secrets were added.
• Demo seed tooling is for disposable E2E/dev setup, not a production first-admin bootstrap flow.

Linked issues

• Fixes Dockerfile.den missing @openwork/email package — build fails #1804
• Partially fixes [Question] Is it possible to use the program in an air-gapped network? #1413
• Helps fix [Bug]: Dockerized Ubuntu computer-use flow is not deliverable end to end #1155

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	May 23, 2026 1:43am

[vercel]

@pascalandr is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.