docs(11-01): complete plan 1 — tags schema + consolidation scripts, DB-execution gated

- Advance STATE.md to plan 2/4, record metrics/decisions/blocker for 11-01
- Fix Status/Progress fields regressed by state advance-plan (status was
  reset to "Ready to execute" / 0% despite phase being mid-execution)
- Note .planning/ROADMAP.md is an empty PLACEHOLDER (pre-existing v2.1
  planning gap) — roadmap update-plan-progress is a no-op until populated

.planning/STATE.md

@@ -3,15 +3,15 @@ gsd_state_version: 1.0
 milestone: v2.1
 milestone_name: milestone
 status: executing
-stopped_at: Phase 11 context gathered
+stopped_at: "11-01: tags schema/scripts committed; DB-execution gated (SSH access required)"
-last_updated: "2026-06-13T13:00:38.635Z"
+last_updated: "2026-06-13T13:32:41.303Z"
-last_activity: 2026-06-13 -- Phase 11 planning complete
+last_activity: 2026-06-13
 progress:
   total_phases: 11
   completed_phases: 8
   total_plans: 37
-  completed_plans: 30
+  completed_plans: 31
-  percent: 81
+  percent: 84
 ---
 
 # Project State
@@ -22,16 +22,16 @@ See: .planning/PROJECT.md (updated 2026-06-13)
 
 **Core value:** Il cliente apre il link e vede esattamente a che punto è il suo progetto, cosa deve ancora succedere e cosa ha già approvato — senza dover scrivere email per chiedere aggiornamenti.
 
-**Current focus:** Phase 11 — Catalog Database-View UX & Legacy Consolidation
+**Current focus:** Phase 11 — catalog-database-view-ux-legacy-consolidation
 
 ## Current Position
 
-Phase: 11 of 17 (Catalog Database-View UX & Legacy Consolidation)
+Phase: 11 (catalog-database-view-ux-legacy-consolidation) — EXECUTING
-Plan: — (not yet planned)
+Plan: 2 of 4
-Status: Ready to execute
+Status: Executing Phase 11
-Last activity: 2026-06-13 -- Phase 11 planning complete
+Last activity: 2026-06-13
 
-Progress: [░░░░░░░░░░] 0%
+Progress: [████████░░] 84%
 
 ## Performance Metrics
 
@@ -45,7 +45,7 @@ Progress: [░░░░░░░░░░] 0%
 
 | Phase | Plans | Total | Avg/Plan |
 |-------|-------|-------|----------|
-| - | - | - | - |
+| Phase 11 P01 | 25min | 2 tasks | 6 files |
 
 **Recent Trend:**
 
@@ -66,6 +66,7 @@ Recent decisions affecting current work:
 - Phase 13 (Workspace — Servizi Attivi) is independent of Phases 11/12 — can execute in parallel order if useful, but numbered after for narrative flow
 - Phase 15 (Dashboard Revenue Stats / DASH-11) is isolated and BLOCKED on user-provided mockup; no other phase depends on it — can be deferred/skipped without blocking Phase 16/17
 - Phase 16/17 split: schema/automation (payment link field + auto-provisioning) first, then AI builder + public page redesign + email — keeps the AI-dependent work last
+- [Phase 11]: Phase 11: hand-write Drizzle migration SQL (0006_add_tags_table.sql) following the project's established convention since drizzle-kit generate is non-functional (meta snapshots out of sync since migration 0001, pre-existing since Phase 8) — Avoids architectural snapshot-reconciliation work (Rule 4, out of scope) while matching exact precedent from migrations 0003-0005
 
 ### Pending Todos
 
@@ -77,6 +78,7 @@ None yet.
 
 - **Phase 15 (DASH-11)**: Blocked pending dashboard mockup from user. Do not start until mockup provided; safe to skip in execution order without impacting Phase 16/17.
 - **Migrations**: Per CLAUDE.md, every phase touching schema (11 legacy consolidation, 13 recurring-revenue tracking, 16 payment link + provisioning) MUST have its migration applied to prod via SSH+docker exec BEFORE pushing dependent code.
+- Phase 11 Plan 1 (11-01): DB-execution steps blocked — DATABASE_URL (178.104.27.55:54321) firewalled, reachable only via SSH+docker exec on the production host (out of scope for this agent's authorization). Required before OFFER-13/D-02 are satisfied: run scripts/push-11-tags-migration.ts, scripts/migrate-services.ts, scripts/validate-services-migration.ts, scripts/migrate-tags.ts, scripts/validate-tags-migration.ts via an SSH-accessible session (see 11-01-SUMMARY.md 'Issues Encountered' for exact commands). OFFER-13 requirement NOT yet marked complete.
 
 ## Deferred Items
 
@@ -90,6 +92,6 @@ Items acknowledged and carried forward from previous milestone close:
 
 ## Session Continuity
 
-Last session: 2026-06-13T10:02:08.473Z
+Last session: 2026-06-13T13:32:41.300Z
-Stopped at: Phase 11 context gathered
+Stopped at: 11-01: tags schema/scripts committed; DB-execution gated (SSH access required)
-Resume file: .planning/phases/11-catalog-database-view-ux-legacy-consolidation/11-CONTEXT.md
+Resume file: .planning/phases/11-catalog-database-view-ux-legacy-consolidation/11-01-SUMMARY.md

.planning/phases/11-catalog-database-view-ux-legacy-consolidation/deferred-items.md

@@ -20,3 +20,11 @@ Items discovered during execution that are out of scope for the current plan/tas
 - **Impact:** Low — admin-only label display in client/project workspace quote_items list. Non-blocking per `11-CONTEXT.md`.
 - **Recommended fix:** 4-line change — replace `leftJoin(service_catalog, ...)` with `leftJoin(services, eq(quote_items.service_id, services.id))` and `service_catalog.name` with `services.name` in both `COALESCE` expressions, at both line ranges.
 - **Status:** Not fixed. Candidate for Phase 12 cleanup or standalone hotfix.
+
+### 3. `.planning/ROADMAP.md` is an empty placeholder for v2.1
+
+- **Found during:** 11-01 state-update step (`gsd-sdk roadmap update-plan-progress 11`)
+- **Issue:** `.planning/ROADMAP.md` contains only the literal text `PLACEHOLDER` (11 bytes). `roadmap update-plan-progress 11` ran without error (`"updated": true`) but there is no "Phase 11" section to update, so the file content did not change. The real v2.1 roadmap content (referenced throughout `11-CONTEXT.md`/`STATE.md` as "ROADMAP.md") does not exist in this file — only `milestones/v1.0-ROADMAP.md` and `milestones/v2.0-ROADMAP.md` exist.
+- **Impact:** Low for this plan (doesn't block 11-01 deliverables), but `roadmap update-plan-progress` is a no-op for the rest of v2.1 until this is fixed, and any future agent reading `@.planning/ROADMAP.md` for phase goals/success-criteria (as referenced in `11-CONTEXT.md` canonical_refs) will find nothing.
+- **Recommended fix:** Populate `.planning/ROADMAP.md` with the v2.1 roadmap content (Phases 11-17), likely should have been written during `/gsd-plan-phase` v2.1 setup (commit `03898f2` "docs(planning): v2.1 milestone setup + Phase 11 context/patterns" added `11-CONTEXT.md`/`11-PATTERNS.md` but apparently not `ROADMAP.md` body content).
+- **Status:** Not fixed — pre-existing planning-artifact gap, out of scope for this execution plan.