chris.dumas/holiday-property-booking
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync project notes with queued tickets
Some checks failed
Deploy Holiday Property Booking / deploy (push) Successful in 1m42s
Details
Playwright Holiday Property Booking / playwright (push) Successful in 11m1s
Details
Test & Build Holiday Property Booking / test-build (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Chris Dumas
2026-05-22 10:36:44 +00:00
parent 64dc8ecb5b
commit 93e4279577
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
PROJECT.md
View File

@@ -30,7 +30,8 @@ Phase 1 scaffold started from the approved planning docs, and the Vikunja board
- Container and host ports match for each environment - Container and host ports match for each environment
- Playwright browser test harness for dev and QA - Playwright browser test harness for dev and QA
- Vikunja board normalized to the playbook lane model - Vikunja board normalized to the playbook lane model
- The first build tickets are queued on the board, with later phase work staged behind them
## Next Build Step ## Next Build Step
- Start with `VIK-108` to define the property/content data model, then work through `VIK-109` to `VIK-111` in order. - Start with `VIK-108`, then work through `VIK-109` to `VIK-112` in order before pulling from the backlog queue.

1
README.md
View File

@@ -7,6 +7,7 @@ Planning workspace for the new project based on the functional specification.
Phase 1 scaffold has started. The repo now contains the Next.js app shell, Prisma schema, Docker entrypoint, and baseline project docs. Environment ports are mapped to `7003` for Dev, `6003` for QA, and `5003` for Production. Phase 1 scaffold has started. The repo now contains the Next.js app shell, Prisma schema, Docker entrypoint, and baseline project docs. Environment ports are mapped to `7003` for Dev, `6003` for QA, and `5003` for Production.
The browser test harness is now being added as a separate action that targets Dev and QA only. The browser test harness is now being added as a separate action that targets Dev and QA only.
The project has been onboarded to Vikunja and the board now uses the playbook lane model. The project has been onboarded to Vikunja and the board now uses the playbook lane model.
The next public work is queued as tickets, with `VIK-112` staged as the next active item after the current slice.
## Working Rule ## Working Rule