Updated: 23 October 2026
This page consolidates the approved design, implementation status, remaining work, known issues, test plan, and recorded evidence for the GHCR/SSH deployment work (the Coding Agent Workflow part was removed, ADR-0067). Its scope is that deployment work only: other workstreams are recorded in their ADRs and reference pages, and the decision register lists them.
Stable product contracts remain in the ADRs and reference pages linked below. Update this page when implementation status or verification changes; do not create another dated status plan.
Build Kintsugi app and worker images from the monorepo, publish commit-tagged images to GHCR, and deploy that exact revision to the configured self-hosted Docker Compose host over SSH. Keep the app, worker, and PostgreSQL topology; run app and worker as non-root; mount runtime data read-only in the app and writable by the worker; keep credentials in GitHub Actions secrets and pin the SSH host key.
First-time host provisioning, Docker/firewall/DNS/TLS setup, and installation-specific database/bootstrap values remain operator tasks. The workflow does not add infrastructure or change the single-host Compose architecture.
The recorded implementation completed the app and worker images, GHCR publishing workflow, commit-SHA tags, SSH deploy gating, configuration validation, pinned known-hosts, Compose bundle transfer, operator setup guide, and ADR decision. Recorded checks built the API/portal and container targets, validated Compose interpolation with temporary non-secret values, parsed the workflow YAML, and reviewed secret handling.
A real deployment still depends on the repository's configured variables/secrets and a provisioned host. See ADR-0039, the installation guide, and the Compose operator guide for stable deployment instructions.
This is the single maintained delivery record for the implementation status and test evidence of the workstreams above. Keep stable architectural decisions in ADRs, exact command contracts in reference pages, and member instructions in the portal guide. Leave detailed agent planning drafts local; do not add another dated plan or progress log to the repository.