diff --git a/PROJECT.md b/PROJECT.md index e35b3c8..ce0a78e 100644 --- a/PROJECT.md +++ b/PROJECT.md @@ -6,7 +6,7 @@ Public holiday property booking website with a booking engine, admin management, ## Status -Phase 1 scaffold started from the approved planning docs. +Phase 1 scaffold started from the approved planning docs, and the Vikunja board is now onboarded. ## Stack @@ -29,7 +29,8 @@ Phase 1 scaffold started from the approved planning docs. - Environment ports aligned to `7003`, `6003`, and `5003` for dev, QA, and production - Container and host ports match for each environment - Playwright browser test harness for dev and QA +- Vikunja board normalized to the playbook lane model ## Next Build Step -- Wire the first data-backed screens after the foundation is in place. +- Start with `VIK-108` to define the property/content data model, then work through `VIK-109` to `VIK-111` in order. diff --git a/README.md b/README.md index 52a6148..097b773 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,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. 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. ## Working Rule diff --git a/VIKUNJA.md b/VIKUNJA.md index 942e5ad..6744bcd 100644 --- a/VIKUNJA.md +++ b/VIKUNJA.md @@ -1,12 +1,47 @@ # Vikunja -## Notes +## Board -The project has not been onboarded to a board yet. +URL: http://vikunja.skynet.arpa/projects/19/77 +Project ID: 19 +Kanban view ID: 77 -## Expected Workflow +## Buckets + +This board is normalized to the shared playbook lane model. + +| Order | Bucket | ID | Playbook lane | Purpose | +|---:|---|---:|---|---| +| 1 | Backlog | 136 | Backlog | Ideas, rough tasks, and future work. | +| 2 | Ready for Dev | 137 | Ready | Refined and ready for implementation. | +| 3 | In Dev | 138 | In Progress | Active implementation work. | +| 4 | Ready for Test | 139 | Validate | Implementation complete and ready for validation. | +| 5 | Deploying to Dev | 140 | Validate | Dev deploy/verification in progress. | +| 6 | In QA | 141 | Validate | QA/live validation work. | +| 7 | Failed QA | 142 | Ready | Validation failed; return to the top of the fix queue with evidence. | +| 8 | Immediate Fix | 143 | Blocked | Urgent blocker requiring fast follow-up. | +| 9 | Ready for QA Promotion | 144 | Release | Ready for develop -> qa promotion sequencing. | +| 10 | Deploying to QA | 145 | Release | QA promotion/deploy in progress. | +| 11 | QA Deployed | 146 | Release | QA deploy complete and awaiting release decision. | +| 12 | Ready for Production | 147 | Release | Ready for production release batching. | +| 13 | Included in Next Release | 148 | Release | Queued for the next production release sweep. | +| 14 | Deploying to Production | 149 | Release | Production deployment in progress. | +| 15 | Production Deployed | 150 | Release | Production deploy complete and awaiting final closeout. | +| 16 | Done | 151 | Done | Fully complete. | +| 17 | Failed Deployment | 152 | Blocked | Deployment failure or broken promotion requiring intervention. | +| 18 | Blocked | 153 | Blocked | Cannot proceed without missing input/access/decision. | + +## Labels + +| Label | Purpose | +|---|---| +| [blocked] | Explicit blocker marker when work cannot continue. | +| [high risk] | Work that needs extra release/validation care. | +| [research] | Research is required before implementation. | + +## Workflow Notes - Planning docs are approved before build work. - Phase 1 foundation work lands first. -- Feature work should be tracked as separate tickets once the board exists. - +- Feature work now lives on this board and should be tracked as separate tickets. +- Use the playbook lane names exactly when routing work.