41 lines
3.0 KiB
Markdown
41 lines
3.0 KiB
Markdown
# GuestOps Release Notes
|
|
|
|
## Next release — Unreleased
|
|
|
|
The reviewed candidate is now promoted into the local `main` history. It is not yet approved for live hotel operations and does not become a release until the merge is pushed, CI evidence is retained and a new immutable semantic-version tag is approved.
|
|
|
|
### Promoted scope
|
|
|
|
- AI-assisted reply suggestions and staff-reviewed Gmail sending.
|
|
- Approval-controlled OHIP PMS and NMI payment workflows.
|
|
- FAQ automation controls, team invitations, password recovery, and stronger Google connection recovery.
|
|
- Backup, restore, deployment, diagnostic, release-evidence and rollback tooling.
|
|
|
|
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 successful default-branch CI run, durable off-host release archive, target-Debian deployment, persistent storage/key validation, monitoring, and a successful restore/rollback exercise.
|
|
- Gate B still requires real Google acceptance and supervised staff testing. Before pilot use, safely paginate beyond the 500-conversation limit, protect drafts across every navigation path, make login throttling proxy-aware, and render dates in the saved hotel timezone—or record and approve explicit operational containment.
|
|
- 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.
|
|
|
|
See [MILESTONES.md](MILESTONES.md) for the gate assessment, delivery sequence, and remaining work.
|
|
|
|
## 0.1.0 — 29 September 2026
|
|
|
|
The `0.1.0` tag identifies the initial GuestOps Web foundation. It is not approved for live hotel operations.
|
|
|
|
### Foundation scope
|
|
|
|
- Responsive shared inbox, search and status filters, saved reply drafts, approved hotel answers, activity history, and hotel settings.
|
|
- 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.
|
|
- Live email sending, PMS writes, payment workflows, and automatic FAQ replies were disabled in this foundation.
|
|
|
|
### Versioning
|
|
|
|
The .NET projects and frontend package currently share version `0.1.0`. Before the next approval tag, choose the next semantic version and update both files together. Move the **Next release** section to that version only after the exact commit, checksummed artifacts and acceptance evidence have been approved.
|