From 853ea1fa6e6c34a84d066b22a0b34a8e3648260e Mon Sep 17 00:00:00 2001
From: Jakub Zych <jakub@keios.eu>
Date: Fri, 16 Oct 2026 00:03:25 +0200
Subject: [PATCH] docs(quick-261015-w7f): summercms.io deployed on v0.2.0

---
 .planning/STATE.md                                     |  5 +++--
 .../261015-w7f-SUMMARY.md                              | 10 +++++++++-
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/.planning/STATE.md b/.planning/STATE.md
index edb4ba0..1b3eda3 100644
--- a/.planning/STATE.md
+++ b/.planning/STATE.md
@@ -5,10 +5,10 @@ current_phase: "19.3"
 current_phase_name: Framework transport and infrastructure for WavePath (INSERTED)
 status: Phase 19.3 plans complete; release and whole-phase docs pending in the phase 19.3 main session
 stopped_at: Completed 19.3-06-PLAN.md (gap closure; release handed off to the phase 19.3 main session)
-last_updated: "2026-10-15T21:01:36.545Z"
+last_updated: "2026-10-15T22:03:18.736Z"
 last_activity: 2026-10-15
 last_activity_desc: 19.3-06 gap closure complete, release handed off
-state_head: 350d0355b27bdf38e106415cf56b14d0e903c6ae
+state_head: a204d38b49b7718c3b39cc8c2218d10be4d2b2f9
 progress:
   total_phases: 40
   completed_phases: 31
@@ -897,6 +897,7 @@ Recent decisions affecting current work:
 | 261011-mag | fix check-phase10.sh hygiene gaps from 10-VERIFICATION.md | 2026-10-11 | 1541cd4 | [261011-mag-fix-check-phase10-sh-hygiene-gaps-from-1](./quick/261011-mag-fix-check-phase10-sh-hygiene-gaps-from-1/) |
 | 261012-s3g | Fix Phase 10 security blockers: DOMPurify richeditor display sanitizer (T-10-16), check-phase10 hygiene green (T-10-24/25), CSP form-action/frame-src; --all still red on fonoteka.go TestPhase09SecurityRoutes | 2026-10-12 | 708b3ec | [261012-s3g-fix-phase-10-security-blockers-t-10-16-d](./quick/261012-s3g-fix-phase-10-security-blockers-t-10-16-d/) |
 | 261013-0wa | Close T-17-15: validate sitemap frontend_url and escape it in Rewrite | 2026-10-12 | 6e5a8e7 | [261013-0wa-close-t-17-15-validate-sitemap-frontend-](./quick/261013-0wa-close-t-17-15-validate-sitemap-frontend-/) |
+| 261015-w7f | Framework docs since v0.1.14 + Upgrading to 0.2, release v0.2.0 (plugins, layers), deploy summercms.io | 2026-10-15 | a204d38 | [261015-w7f-update-framework-docs-for-phase-19-3-rel](./quick/261015-w7f-update-framework-docs-for-phase-19-3-rel/) |
 
 ## Deferred Items
 
diff --git a/.planning/quick/261015-w7f-update-framework-docs-for-phase-19-3-rel/261015-w7f-SUMMARY.md b/.planning/quick/261015-w7f-update-framework-docs-for-phase-19-3-rel/261015-w7f-SUMMARY.md
index 474c253..4bc5474 100644
--- a/.planning/quick/261015-w7f-update-framework-docs-for-phase-19-3-rel/261015-w7f-SUMMARY.md
+++ b/.planning/quick/261015-w7f-update-framework-docs-for-phase-19-3-rel/261015-w7f-SUMMARY.md
@@ -3,7 +3,7 @@ phase: quick-261015-w7f
 plan: 01
 subsystem: docs, release
 tags: [docs, release, v0.2.0, summercms.io, deploy]
-status: checkpoint
+status: complete
 requires:
   - decision 2026-10-15-release-v0-2-0 (commit 76d7888)
   - 19.3-06 handoff (tag, plugin bumps, layer tags)
@@ -157,3 +157,11 @@ Otherwise the plan ran as written, up to the planned deploy checkpoint.
 - FOUND: aac8931 (site plugin), 36c3c50 (app), both pushed
 - FOUND: layer tags v0.3.0, v0.3.0, v0.5.0 on origin
 - FOUND: bin/summercms-io reporting v0.2.0
+
+## Deploy (orchestrator, 2026-10-16)
+
+Deployed to rome over `ssh -p 2222 debian@10.8.3.118` (the `rome` alias does not resolve on this workstation). Binary sha256 a1c573f9…ef81c85 matched on the server; `migrate` applied; `bin/summercms-io.prev` kept for rollback; supervisor `summercms-io` RUNNING; loopback 200.
+
+Live checks: `/`, `/docs/`, `/docs/setup/upgrading.html` (contains "Upgrading to 0.2"), `/docs/services/caching.html`, `/docs/api/cooler.html`, `/new` all 200; HSTS, www→apex 301, immutable `/_nuxt` assets, docs site link, extensionless 301, `/backend` 404, POST 403, http→https 301 as DEPLOY.md expects. `TestExternalLinks` ok. TASK3_DEPLOYED_OK.
+
+Finding: `/srv/summercms-io/config` is owned by `jin:jin`, not the `root:root` DEPLOY.md expects. Not the service account, so the swap risk DEPLOY.md guards against does not apply, but it should be `sudo chown root:root` to match the documented layout.