Shipyard development worker

Shipyard is the Ubuntu worker for native agents, application processes, builds, Docker dependencies and the shared browser. Connect with ssh shipyard as akshat.

Reported baseline and verified operations

The setup record reports Ubuntu 24.04.5 amd64, Ryzen 7800X3D, 32 GB installed RAM, RTX 3070, a 2 TB NVMe with expanded LVM, 8 GB swap and swappiness 10. SSH/Tailscale/Docker startup and masked sleep targets were configured. These are dated setup facts, not a current hardware census; normal boot and controlled AC-return checks passed on 6 October. Off-LAN access and complete task restoration remain untested; see power recovery.

Important locations

Location	Purpose
~/code/api, ~/code/dashboard, ~/code/appliance	Primary repositories
~/dev-environment/scripts	Active lifecycle and browser scripts
~/dev-environment/private	Private persistent browser profile
~/dev-environment/state	Ownership, locks and retained companions
~/dev-environment/logs	Private logs; review locally and redact
~/.config/dev-environment	Credential references and worker key
~/code/dev-environment	Intended checkout of this personal repository

Process lifecycle

Applications run in tmux; Docker hosts dependencies. They survive SSH/UI disconnects. The shared browser starts manually after reboot. Do not infer readiness from installation or a tmux name: use diagnostics and task status.

The primary local api-pg container supplies seed data. It is deliberately distinct from worktree databases. Archive task resources individually and retain volumes. No periodic cleanup or automatic repair is configured by this repository.

Current constraints

One managed dashboard and one browser session. Serial API setup; four-job, serialized appliance compilation. Google access is curated and incomplete for some workflows. See access, resources and known issues.