replace docker deployment with native system

This commit is contained in:
2026-10-22 15:40:27 +01:00
parent 36aa23c4b3
commit 6193409838
24 changed files with 317 additions and 319 deletions
+7 -7
View File
@@ -1,8 +1,8 @@
# GuestOps Release Notes
## 0.2.1 — Gate B release candidate
## 0.2.2 — Gate B native deployment candidate
This candidate freezes the implemented Gate B scope for controlled acceptance. It is not yet approved for live hotel operations and does not become a release until the exact commit is pushed, a checksummed source package and operational evidence are retained, the supervised pilot is approved and the immutable `0.2.1` tag is created.
This candidate freezes the implemented Gate B scope for controlled acceptance and replaces the unsuccessful source-build `0.2.1` deployment artifact with self-contained Linux x64 API and worker applications managed by systemd. It is not yet approved for live hotel operations and does not become a release until the exact commit is pushed, a checksummed native package and operational evidence are retained, the supervised pilot is approved and the immutable `0.2.2` tag is created.
### Promoted scope
@@ -13,13 +13,13 @@ This candidate freezes the implemented Gate B scope for controlled acceptance. I
- Release-bound automation and identity/privacy acceptance records covering training, provider decisions, retention ownership and known limitations.
- Stable tenant-scoped inbox pagination beyond the former 500-message view, unsaved-draft guards including browser history navigation, consistent hotel-timezone timestamps across operational screens, and a release-bound desktop-parity acceptance record.
- A bounded read-only sandbox capacity probe plus machine-validated, release-bound supervised-pilot run, go/no-go and incident-exercise records.
- Backup, restore, opt-in systemd scheduling, deployment, persistence-drill, diagnostic, release-evidence, Google acceptance-record validation and rollback tooling.
- Native systemd API and worker deployment with persistent Data Protection keys, loopback-only HTTP, Nginx HTTPS, and version-selected rollback.
These capabilities still require their separately documented provider, host and operational acceptance. Google, PMS and payment-provider acceptance is not established by local automated tests.
### Known limitations and launch conditions
- Gate A still requires a checksummed source package from the exact default-branch commit, Ansible installation on the target Debian host, persistent storage/key validation, monitoring, and a successful restore/rollback exercise.
- Gate A still requires a checksummed native package from the exact default-branch commit, Ansible installation on the target Debian host, persistent storage/key validation, monitoring, and a successful restore/rollback exercise.
- Gate B still requires real Google acceptance and supervised staff testing, including desktop-parity acceptance of pagination, draft protection, proxy-aware login throttling and saved-hotel-timezone rendering.
- Gate C still requires the Rezlynx/Guestline adapter and independently accepted PMS/payment workflows, plus privacy, identity, capacity, and release approvals.
- FAQ live mode and all external write actions must remain disabled until their corresponding acceptance gate has passed.
@@ -28,7 +28,7 @@ See [MILESTONES.md](MILESTONES.md) for the gate assessment, delivery sequence, a
## 0.2.0 — Superseded candidate identifier
The published `0.2.0` tag is retained unchanged for auditability but is not the approved deployment candidate. It identifies a development-line commit that is not on the clean Gate B release branch. Do not package or deploy it; `0.2.1` supersedes it.
The published `0.2.0` tag is retained unchanged for auditability but is not the approved deployment candidate. It identifies a development-line commit that is not on the clean Gate B release branch. Do not package or deploy it; `0.2.2` supersedes it.
## 0.1.0 — 29 September 2026
@@ -40,9 +40,9 @@ The `0.1.0` tag identifies the initial GuestOps Web foundation. It is not approv
- ASP.NET Core authentication with protected cookies, password hashing, CSRF validation, login throttling, role checks, and server-derived hotel membership.
- Tenant-scoped MongoDB storage with optimistic concurrency, unique mailbox/message indexes, OAuth state expiry, and worker leases.
- Read-only Google OAuth and recent-message import foundation with checkpoint and duplicate protection.
- Preview mode, Linux container definitions, Nginx HTTPS example, and automated backend/frontend verification.
- Preview mode, native Linux packaging, Nginx HTTPS example, and automated backend/frontend verification.
- Live email sending, PMS writes, payment workflows, and automatic FAQ replies were disabled in this foundation.
### Versioning
The foundation remains tagged `0.1.0`. The .NET projects and frontend package now share candidate version `0.2.1`; create that immutable tag only after the exact commit, checksummed artifacts and Gate B acceptance evidence have been approved.
The foundation remains tagged `0.1.0`. The .NET projects and frontend package now share candidate version `0.2.2`; create that immutable tag only after the exact commit, checksummed artifacts and Gate B acceptance evidence have been approved.