From 93e4279577f6b7ad0b32cd18df0a74b660e8d613 Mon Sep 17 00:00:00 2001 From: Chris Dumas Date: Fri, 22 May 2026 10:36:44 +0000 Subject: [PATCH] Sync project notes with queued tickets --- PROJECT.md | 3 ++- README.md | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/PROJECT.md b/PROJECT.md index ce0a78e..746065b 100644 --- a/PROJECT.md +++ b/PROJECT.md @@ -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 - Playwright browser test harness for dev and QA - 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 -- 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. diff --git a/README.md b/README.md index 097b773..2f758e4 100644 --- a/README.md +++ b/README.md @@ -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. 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 next public work is queued as tickets, with `VIK-112` staged as the next active item after the current slice. ## Working Rule