chore: bump phase 1 checkpoint to 0.1.1

DEVELOPMENT_LOG.md

@@ -1,5 +1,12 @@
 # Queue-North-Website — Development Log
 
+## v0.1.1 — Phase 1 Agent-Pass Checkpoint — 2026-05-12
+
+**Ripley** — Version correction and push rule alignment
+- Corrected Phase 1 version from `0.1.0` to `0.1.1` after user clarified that each completed agent pass/checkpoint should be uploaded to `dev` and reflected as a patch increment.
+- Updated package/version docs to make patch increments map to completed agent passes within the active phase.
+- Re-ran build and backend health check before committing/pushing.
+
 ## v0.1.0 — Phase 1 Foundation — 2026-05-12
 
 **Scarlett** — Design brief and UI polish

HISTORY.md

@@ -1,5 +1,16 @@
 # Queue-North-Website — Changelog
 
+## v0.1.1 — Phase 1 Agent-Pass Checkpoint — 2026-05-12
+
+### Changed
+- Corrected Phase 1 version to reflect completed agent-pass checkpoint semantics.
+- Documented that every completed agent pass/checkpoint within a phase increments the patch version.
+- Confirmed Phase 1 verified output is pushed to `dev` at `0.1.1`.
+
+### Verified
+- `npm run build` passes.
+- Backend health endpoint responds successfully at `/api/health`.
+
 ## v0.1.0 — Phase 1 Foundation — 2026-05-12
 
 ### Added

OVERHAUL_PLAN.md

@@ -810,7 +810,7 @@ Version numbers must correlate directly to the active overhaul phase.
 
 - **Phase 1** uses `0.1.x`
   - First Phase 1 release: `0.1.0`
-  - Iterations/fixes within Phase 1: `0.1.1`, `0.1.2`, etc.
+  - Every completed agent pass/checkpoint within Phase 1: `0.1.1`, `0.1.2`, etc.
 - **Phase 2** uses `0.2.x`
   - First Phase 2 release: `0.2.0`
   - Iterations/fixes within Phase 2: `0.2.1`, `0.2.2`, etc.
@@ -818,7 +818,7 @@ Version numbers must correlate directly to the active overhaul phase.
 - **Phase 4** uses `0.4.x`
 - **Phase 5** uses `0.5.x`
 
-Rule: the minor version maps to the phase number; the patch version maps to work inside that phase. Do not use unrelated semantic version bumps during the overhaul.
+Rule: the minor version maps to the phase number; the patch version maps to each completed agent pass/checkpoint inside that phase. Do not use unrelated semantic version bumps during the overhaul.
 
 ---
 

PROJECT.md

@@ -3,7 +3,7 @@
 ## Overview
 Project: Queue-North-Website
 Created: 2026-05-11
-Status: Active (Phase 1 Complete - 0.1.0)
+Status: Active (Phase 1 Complete - 0.1.1)
 Rebuild Phase: 1 (Vite + React + Express + SQLite)
 
 ## Description
@@ -44,7 +44,7 @@ Version numbers must correlate to the active overhaul phase.
 
 - Phase 1 releases use `0.1.x`
   - Phase 1 baseline: `0.1.0`
-  - Phase 1 patches/iterations: `0.1.1`, `0.1.2`, etc.
+  - Every completed agent pass/checkpoint within Phase 1 increments patch: `0.1.1`, `0.1.2`, etc.
 - Phase 2 releases use `0.2.x`
   - Phase 2 baseline: `0.2.0`
   - Phase 2 patches/iterations: `0.2.1`, `0.2.2`, etc.

STRUCTURE.md

@@ -26,7 +26,7 @@ Bishop owns verification documentation and must ensure version numbers correlate
 
 - Phase 1 uses `0.1.x`
   - Phase 1 baseline: `0.1.0`
-  - Phase 1 follow-up fixes/iterations: `0.1.1`, `0.1.2`, etc.
+  - Every completed agent pass/checkpoint within Phase 1 increments patch: `0.1.1`, `0.1.2`, etc.
 - Phase 2 uses `0.2.x`
   - Phase 2 baseline: `0.2.0`
   - Phase 2 follow-up fixes/iterations: `0.2.1`, `0.2.2`, etc.
@@ -34,7 +34,7 @@ Bishop owns verification documentation and must ensure version numbers correlate
 - Phase 4 uses `0.4.x`
 - Phase 5 uses `0.5.x`
 
-Rule: the minor version maps to the phase number; the patch version maps to work inside that phase. Do not use unrelated semantic version bumps during this overhaul.
+Rule: the minor version maps to the phase number; the patch version maps to each completed agent pass/checkpoint inside that phase. Do not use unrelated semantic version bumps during this overhaul.
 
 Before Bishop marks work verified, Bishop must check:
 - `package.json` version follows the active phase

package.json

@@ -1,7 +1,7 @@
 {
   "name": "queuenorth-website",
   "private": true,
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "scripts": {
     "dev": "concurrently \"vite\" \"node server/index.js\"",