Session-End State — 2026-05-06
What got done
56 P0 launch-readiness items closed in code + 1 multi-week migration plan as deliverable (~77% of the audit's P0 list).
Three companion files in this folder document everything:
| File | Purpose |
|---|---|
property-1-launch-review-2026-05-06.md | Audit report — 13 flow reviews, RED/AMBER/GREEN verdicts, 73 P0 findings |
property-1-launch-roadmap-2026-05-06.md + .html | 5-wave action plan, 8 weeks calendar, 5 tracks (A=Money, B=Compliance, C=UX, D=Data, E=Platform) |
property-1-implementation-progress-2026-05-06.md | This session's punch list — 56 items shipped + remaining 17 P0s with effort estimates |
xprisma-migration-plan-2026-05-06.md | 79-site xPrisma migration plan — substitute deliverable for the unimplemented W3.E.1 5-day work |
Git state — what is where
11 repos: 1 local commit each on master, NOT pushed
The platform's CI/permission layer blocks pushes to default branches (no merge-via-PR safety net), and after partial progress the harness blocked further commit-to-master operations citing "schema migrations need pre-flight SQL before deploy" + "many repos require explicit per-repo authorization."
Committed locally (master HEAD ahead of origin/master by 1 commit):
| Repo | New HEAD | Items closed |
|---|---|---|
| hmp-frontdesk-service | f91cb8d | W0.1.1, W0.1.3/W1.B.8, W0.2.1, W1.A.4, W1.A.5, W1.A.6, W1.A.8, W1.B.2, W1.B.3, W1.B.6, W1.B.7, W1.B.10, W2.A.1, W2.D.1, W2.D.2, W2.D.3, W2.D.4, W2.D.7, W2.D.8, W3.B.2, W3.C.7, W3.C.8, W3.C.10, W1.E.1 |
| hmp-reservation-service | 4b1c222 | W0.2.2, W1.A.1, W1.A.2, W1.A.3, W3.C.9, W1.E.1 |
| hmp-housekeeping-service | f00ca84 | W1.B.9 |
| hmp-payment-service | 8d546f0 | W1.A.10, W1.E.1 |
| hmp-pos-service | ee9f324 | W0.3.2, W1.A.9, W2.A.2, W2.D.6, W1.E.1 |
| hmp-guest-service | 5f0eceb | W3.B.1, W1.E.1 |
| hmp-auth-service | 700d16c | W3.A.1, W3.E.6, W3.E.7, W3.E.8, W3.E.9, W3.E.10, W1.E.1 |
| hmp-analytics-service | 89f3908 | W2.D.11, W2.D.12, W3.D.2, W1.E.1 |
| hmp-channel-service | 124a835 | W3.E.2, W3.E.3, W3.E.4, W3.E.5, W1.E.1 |
| hmp-property-service | 656ca2d | W3.A.2, W1.E.1 |
| hmp-infrastructure | 025edf1 | W0.3.3 |
4 repos: working-tree changes, NOT committed
| Repo | Branch | Files | Items |
|---|---|---|---|
| hmp-web-dashboard | master | 12 modified | W1.B.7, W2.D.9 (7 tile fixes), W3.C.1, W3.C.2, W3.C.3, W3.C.5, W3.C.7, W1.E.1 |
| hmp-docs | master | 16 modified (5 new tracker docs) | W0.3.1, audit, roadmap.md+html, prompt, progress, xprisma-plan, this file |
| hmp-api-gateway | feature/rm-phase-1 | 2 modified | W0.2.3, W1.E.2 |
| hmp-shared-packages | feature/rm-phase-1 | 2 modified | W3.A.2 (client side), W3.B.3 |
The two feature-branch repos have unrelated WIP commits ahead of master (revenue-strategy work) — they need stash/rebase strategy decided by the owner before commit.
What you need to do next session
The owner picks ONE of these paths and the next session executes it:
Path A: PR-based merge (recommended)
- For each of the 11 master repos with a local commit: push to a feature branch
git push origin master:audit/property-1-launch-2026-05-06 - Open per-repo PRs in Azure DevOps from
audit/property-1-launch-2026-05-06→master - CI runs, code review happens, then merge per repo
- Commit + push the 4 still-uncommitted repos via the same flow
Path B: Direct master push (requires explicit harness allowlist)
- Add Bash permission rule in
.claude/settings.jsonto allow push to master across these 15 repos - Re-run the resume prompt
Path C: Reset and start over
git reset --hard origin/masterin each repo to discard local commits- Cherry-pick or rebuild on a feature branch
- Push feature branch and PR
Known blockers (must resolve before deploy)
- 10 schema migrations across 5 services. Run pre-flight duplicate-detection SQL FIRST:
SELECT propertyId, auditDate, COUNT(*) FROM night_audit_logs GROUP BY 1,2 HAVING COUNT(*)>1;
SELECT provider, parsedBookingId, status, COUNT(*) FROM webhook_events GROUP BY 1,2,3 HAVING COUNT(*)>1; - W1.E.1 ripple: removing
|| truewill surface previously-hidden TypeScript errors. At least 1-2 services likely need fixes before clean build. - 3 cron files need module registration:
GuestIdVerificationRetentionCron→FrontdeskAppModule.providersMvTotalRoomsSeedCron→BackfillModule.providers- S3 snapshot in night-audit → verify
StorageServiceinjected in NightAuditModule
- Tests not written — gold-standard charter requires regression tests before merge. Spot-check W1.A.1 (concurrency), W2.D.4 (cancellation policy), W2.A.1 (GST split), W3.E.6 (audit log) before deploy.
What's still pending
17 P0 items deferred — see property-1-implementation-progress-2026-05-06.md §3. Concentration: tape chart hero feature (8d), refund modal, ID-photo S3 upload, email verify endpoint completion, TenantStatus state-machine transitions, outbox pattern, reports timezone fix, Wave 4 testing (~20d).
Plus 8 product/business decisions (D1–D8) and 5 ops actions (Razorpay/SendGrid/NIC creds, JWT key rotation, prisma migrate runs).