Deployment setup - the parts the workflow deliberately left out

Host setup checklist, real domains and ports, the database backup
script the deploy workflow only ever invokes, and a rollback plan.
Also drafted the FTPS switch procedure for whenever production moves
off the Pi, with a note that shared hosting is likely IIS-based -
that's a bigger change than swapping the transport.

aidlc-docs/features/gitea-deployment-workflow/aidlc-state.md

@@ -38,6 +38,17 @@
 - **Include Operations Phase**: Yes
 - **Decided At**: Requirements Analysis
 
+### Deployment Setup
+- **Included**: Yes
+- **Method**: CI/CD (Gitea Actions — confirms what U5/U6 already built)
+- **Completed**: 2026-07-28. Real domains: `test.slpsoftware.nl` / `slpsoftware.nl`. Ports 5100/5101
+  chosen for the Pi's local Kestrel bindings. Database backup script drafted. Full FTPS future-switch
+  procedure drafted (Q5 = B), with an explicit caveat that shared hosting is very likely IIS-based,
+  so systemd-restart and atomic-symlink-switch do not carry over unchanged — treated as a starting
+  brief for a future Infrastructure Design pass, not a ready-to-execute procedure
+- **Artifacts**: `operations/deployment/deployment-plan.md`, `deployment-instructions.md`,
+  `rollback-plan.md`
+
 ## Scope Decisions (from feature-selection.md)
 - **Public website**: documentation/instructions only — where the website build lands in `wwwroot/`, how it coexists with `wwwroot/admin/`, and what a per-website workspace must deliver. The website's own build/deploy workflow stays out of scope (Q4 = A).
 - **Environments**: local, test, production only.