Stacked on #11 (references scripts/smoke-test.sh, which doesn't exist on main yet).
Phase 0 is actually done — this just makes the docs say so accurately instead of describing the original Postgres+RLS/docker-compose/auto-redeploy design that isn't what got built.
docs/PLAN.md: Phase 0 marked done, with its two deliberate deviations (D15, D16/D17) stated plainly instead of left as stale prose contradicting the code. "Done when"/Verification split into what's actually verified (login persists — real bug, real fix, real test) vs. what's still untried (PWA home-screen install).
docs/DECISIONS.mdD19: the Unraid update-checker fix (a third independent place the D17 cert needed trusting), why "up to date" still can't be fully trusted on this host (CI shares this host's dockerd, so the local tag is always fresh independent of the running container), the failed first Watchtower attempt, and why CI-auto-redeploy was rejected again. Three new "Deliberately deferred" entries: finish Watchtower, migrate Gitea/CI to a dedicated VM (the actual root cause), persist the accumulated host-local trust files across a reboot.
deploy/README.md: flags that Unraid's update badge isn't trustworthy for this container specifically, and consolidates the "what's not here yet" list.
Stacked on #11 (references `scripts/smoke-test.sh`, which doesn't exist on `main` yet).
Phase 0 is actually done — this just makes the docs say so accurately instead of describing the original Postgres+RLS/docker-compose/auto-redeploy design that isn't what got built.
- `docs/PLAN.md`: Phase 0 marked done, with its two deliberate deviations (D15, D16/D17) stated plainly instead of left as stale prose contradicting the code. "Done when"/Verification split into what's actually verified (login persists — real bug, real fix, real test) vs. what's still untried (PWA home-screen install).
- `docs/DECISIONS.md` **D19**: the Unraid update-checker fix (a third independent place the D17 cert needed trusting), why "up to date" still can't be fully trusted on this host (CI shares this host's `dockerd`, so the local tag is always fresh independent of the running container), the failed first Watchtower attempt, and why CI-auto-redeploy was rejected again. Three new "Deliberately deferred" entries: finish Watchtower, migrate Gitea/CI to a dedicated VM (the actual root cause), persist the accumulated host-local trust files across a reboot.
- `deploy/README.md`: flags that Unraid's update badge isn't trustworthy for this container specifically, and consolidates the "what's not here yet" list.
No code changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs/PLAN.md's Phase 0 section and its "Done when"/Verification entries
still described the original Postgres+RLS, docker-compose, auto-redeploying
design — none of which is what actually got built and deployed. Marks it
done, states the two deliberate deviations plainly (SQLite not Postgres+RLS,
manual redeploy not automatic), and separates what's actually verified
(login persists a session, checked by scripts/smoke-test.sh after a real bug)
from what nobody has tried yet (PWA home-screen install).
docs/DECISIONS.md D19 records the auto-update investigation: the real fix
for Unraid's own "not available" update-check badge (a third, independent
place the D17 self-signed cert needed trusting — Unraid's PHP update
checker doesn't share Docker's own certs.d), the structural reason "up to
date" can't be fully trusted on this host even after that fix (CI builds on
the same dockerd the app runs on, so the local :latest tag is always fresh
regardless of whether the container was recreated from it), the failed
first Watchtower attempt (stale image, wrong Docker API version) and why
CI-triggers-a-redeploy was rejected again rather than reconsidered.
"Deliberately deferred" gets three new entries: finishing Watchtower,
migrating Gitea/CI to a dedicated VM (raised as the real fix for the
root cause D19 kept running into), and persisting the accumulated
host-local trust files across a reboot.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R2ZKeWkZV7ehf7fivrAkkG
BBergle
merged commit b1e5aaf908 into test/deploy-login-smoke-test2026-09-21 22:59:59 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Stacked on #11 (references
scripts/smoke-test.sh, which doesn't exist onmainyet).Phase 0 is actually done — this just makes the docs say so accurately instead of describing the original Postgres+RLS/docker-compose/auto-redeploy design that isn't what got built.
docs/PLAN.md: Phase 0 marked done, with its two deliberate deviations (D15, D16/D17) stated plainly instead of left as stale prose contradicting the code. "Done when"/Verification split into what's actually verified (login persists — real bug, real fix, real test) vs. what's still untried (PWA home-screen install).docs/DECISIONS.mdD19: the Unraid update-checker fix (a third independent place the D17 cert needed trusting), why "up to date" still can't be fully trusted on this host (CI shares this host'sdockerd, so the local tag is always fresh independent of the running container), the failed first Watchtower attempt, and why CI-auto-redeploy was rejected again. Three new "Deliberately deferred" entries: finish Watchtower, migrate Gitea/CI to a dedicated VM (the actual root cause), persist the accumulated host-local trust files across a reboot.deploy/README.md: flags that Unraid's update badge isn't trustworthy for this container specifically, and consolidates the "what's not here yet" list.No code changes.
🤖 Generated with Claude Code