Add V2 Forgejo workflow publishing study:v2 image

Pushes to v2 typecheck and test inside the Node 24 image via a new Dockerfile
test stage, build and smoke-test the production image as a fresh non-root
container, then publish :v2 and :v2-<sha>. Never touches V1's :latest.
Document the image tags and Unraid 99:100 volume ownership.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Elijah 2026-11-12 11:29:22 -07:00
parent d7e19db468
commit 3046e46d1c
4 changed files with 107 additions and 10 deletions

View file

@ -78,5 +78,6 @@ account-specific model access, Linux container behavior and Unraid proxy configu
be checked in their target environments.
[PROGRESS.md](PROGRESS.md) records completed work, remaining verification, decisions and the
resume procedure. V1 remains on `main` and in Git history; all V2 work is on local `v2`.
Nothing is automatically pushed or published.
resume procedure. V1 remains on `main` and in Git history; V2 work is on the `v2` branch.
Pushing `v2` to Forgejo runs CI and publishes the `study:v2` image (never `:latest`); see
[deployment](docs/DEPLOYMENT.md). Nothing deploys automatically.