docs: start milestone v1.1 Backlog and Tech Debt

.planning/PROJECT.md

@@ -25,9 +25,16 @@ An IT pro can go from zero to a deployable rclone setup in minutes — without n
 
 ### Active
 
-- [ ] `scriptTargets` filtering: only render output blocks for selected Intune/RMM targets (tech debt TD-1)
-- [ ] ReviewStep Back button (UX consistency with other steps — tech debt TD-2)
-- [ ] Backend list in BackendSelectionStep driven by BACKEND_REGISTRY keys (maintainability — tech debt TD-4)
+**Milestone: v1.1 — Backlog & Tech Debt**
+
+*Tech debt:*
+- [ ] `scriptTargets` filtering: only render output blocks for selected Intune/RMM targets (TD-1)
+- [ ] ReviewStep Back button (UX consistency with other steps — TD-2)
+- [ ] Backend list in BackendSelectionStep driven by BACKEND_REGISTRY keys (maintainability — TD-4)
+- [ ] `BackendFormValues<T>` dead export removal from src/schemas/index.ts
+- [ ] `act()` warnings fixed in BackendSelectionStep tests
+
+*Backlog features:*
 - [ ] Additional backends: OneDrive, SFTP, Google Cloud Storage, Backblaze B2
 - [ ] Field-level format validation per backend (Azure account name format, S3 region codes)
 - [ ] Explanatory tooltips on sensitive fields (SAS token vs access key, region codes)
@@ -76,5 +83,18 @@ An IT pro can go from zero to a deployable rclone setup in minutes — without n
 | scriptTargets defaults to both ['intune','rmm'] | Users deselect rather than discover — less friction | — Pending (deferred filtering to v1.1) |
 | BACKEND_REGISTRY keys not wired to UI list | Hardcoded BACKENDS constant in BackendSelectionStep | ⚠️ Revisit — maintainability gap for v1.1 |
 
+## Current Milestone: v1.1 Backlog & Tech Debt
+
+**Goal:** Ship all deferred tech debt and backlog features from v1.0 — no new functionality.
+
+**Target features:**
+- scriptTargets filtering in ReviewStep
+- ReviewStep Back button
+- BackendSelectionStep driven by BACKEND_REGISTRY
+- Dead export + test warning cleanup
+- 4 additional backends (OneDrive, SFTP, GCS, Backblaze B2)
+- Field-level format validation per backend
+- Explanatory tooltips on sensitive fields
+
 ---
-*Last updated: 2026-03-27 after v1.0 milestone*
+*Last updated: 2026-03-27 after v1.1 milestone started*

.planning/STATE.md

@@ -1,11 +1,11 @@
 ---
 gsd_state_version: 1.0
 milestone: v1.1
-milestone_name: ""
-status: milestone_complete
-stopped_at: v1.0 MVP milestone archived — ready for next milestone
+milestone_name: "Backlog & Tech Debt"
+status: defining_requirements
+stopped_at: Milestone v1.1 started — defining requirements
 last_updated: "2026-03-27T00:00:00.000Z"
-last_activity: 2026-03-27 — v1.0 milestone complete
+last_activity: 2026-03-27 — Milestone v1.1 started
 progress:
   total_phases: 0
   completed_phases: 0
@@ -25,10 +25,10 @@ See: .planning/PROJECT.md (updated 2026-03-27)
 
 ## Current Position
 
-Phase: 1 of 4 (Foundation)
-Plan: 2 of 4 in current phase
-Status: In progress
-Last activity: 2026-03-26 — Completed plan 01-02 (Backend Schema Registry)
+Phase: Not started (defining requirements)
+Plan: —
+Status: Defining requirements
+Last activity: 2026-03-27 — Milestone v1.1 started
 
 Progress: [█████░░░░░] 50%