chore: remove phase 7 (Azure Functions Host and Durable API Surface)

Author: Aitomates

.planning/PROJECT.md

@@ -24,7 +24,7 @@ You can give one prompt and watch a trustworthy multi-agent coding system drive
 
 ### Validated
 
-- Existing: repo-aware local agent runtime via Microsoft Agent Framework and DevUI in `maf_starter/` and `entities/`
+- Existing: repo-aware local agent runtime via Microsoft Agent Framework and DevUI in `maf_core/` and `entities/`
 - Existing: multi-agent workflow scaffolding, including the `repo_team` planner/researcher/implementer/reviewer workflow
 - Existing: provider and model routing with fallback across Gemini API, optional Anthropic, and CLI fallbacks
 - Existing: human-in-the-loop and route trace mechanisms in local form through tool approval, route metadata, and DevUI patching
@@ -53,7 +53,7 @@ You can give one prompt and watch a trustworthy multi-agent coding system drive
 
 ## Context
 
-This is a brownfield codebase with an existing local agent runtime. The active path is MAF-first: `main.py` dispatches into `maf_starter/cli.py`, entities are discovered from `entities/`, and DevUI is used for local interaction. The repo also retains a substantial legacy AutoGen stack in `autogen_dashboard/` and `autogen_starter/`, which creates both opportunity and drift risk.
+This is a brownfield codebase with an existing local agent runtime. The active path is MAF-first: `main.py` dispatches into `maf_core/cli.py`, entities are discovered from `entities/`, and DevUI is used for local interaction. The repo also retains a substantial legacy AutoGen stack in `autogen_dashboard/` and `autogen_starter/`, which creates both opportunity and drift risk.
 
 The workstation context matters. GSD is already installed locally, and you also have Gemini CLI, Claude CLI, and Codex CLI available, along with Gemini API access and local Azure Functions development tools. On this machine, Azure Functions Core Tools `4.8.0`, Azure CLI `2.80.0`, and Docker `29.1.5` are available. `azd` is not currently installed, so this milestone should not depend on `azd`-only templates or flows. The intended operating model is to use the local machine as the main execution environment, let Gemini API answer most orchestration and GSD questions automatically, and use the installed CLIs as specialist workers or fallback engines when appropriate.
 

.planning/ROADMAP.md

@@ -16,8 +16,7 @@ This roadmap now enters milestone v1.1: Cloud API and Azure Function Hosting. Th
 - [x] **Phase 4: Autonomous Repo Execution and Validation Guardrails** - Turn the system into a safe default-doer for repo work
 - [x] **Phase 5: Polished Operator Workbench** - Replace prototype interaction with a durable operator-grade UI
 - [ ] **Phase 6: API Boundary and Control Plane Contract** - Extract a shared orchestration service layer and expose it through a stable HTTP API
-- [ ] **Phase 7: Azure Functions Host and Durable API Surface** - Host the control plane in Python Azure Functions with durable run state and async status behavior
-- [ ] **Phase 8: Worker Boundary and Cloud-Safe Execution Profiles** - Separate cloud ingress from long-running repo execution and local-only provider assumptions
+- [ ] **Phase 7: Worker Boundary and Cloud-Safe Execution Profiles** - Separate cloud ingress from long-running repo execution and local-only provider assumptions
 
 ## Phase Details
 
@@ -37,23 +36,7 @@ Plans:
 - [ ] 06-02: Add REST endpoints for submit, status, control, routing, agents, and artifacts
 - [ ] 06-03: Align Operator Workbench and HTTP API parity over the shared run contract
 
-### Phase 7: Azure Functions Host and Durable API Surface
-**Goal**: Host the control plane on Azure Functions with durable state and local Core Tools parity.
-**Depends on**: Phase 6
-**Requirements**: AZFN-01, AZFN-02, AZFN-03, AZFN-04
-**Success Criteria** (what must be TRUE):
-  1. The shared control-plane API can run inside a Python Azure Functions host without rewriting the orchestration core.
-  2. Long-running run state survives host restarts and outlives the original HTTP request.
-  3. The Functions-hosted API can be started and validated locally with Azure Functions Core Tools.
-  4. Routes, settings, and auth behavior are documented and behave consistently between local and Azure environments.
-**Plans**: 3 plans
-
-Plans:
-- [ ] 07-01: Create the Functions host entrypoint and cloud-safe configuration surface
-- [ ] 07-02: Add durable run-start and async status behavior with local Core Tools verification
-- [ ] 07-03: Document routes, auth, and deployment-ready function settings
-
-### Phase 8: Worker Boundary and Cloud-Safe Execution Profiles
+### Phase 7: Worker Boundary and Cloud-Safe Execution Profiles
 **Goal**: Make long-running execution explicit and safe when the control plane is hosted away from the local workstation.
 **Depends on**: Phase 7
 **Requirements**: WRKR-01, WRKR-02, WRKR-03
@@ -65,9 +48,9 @@ Plans:
 **Plans**: 3 plans
 
 Plans:
-- [ ] 08-01: Introduce the worker boundary and background run dispatch contract
-- [ ] 08-02: Add cloud-safe provider and execution profiles with explicit capability enforcement
-- [ ] 08-03: Validate end-to-end API-driven runs across local and cloud-safe execution modes
+- [ ] 07-01: Introduce the worker boundary and background run dispatch contract
+- [ ] 07-02: Add cloud-safe provider and execution profiles with explicit capability enforcement
+- [ ] 07-03: Validate end-to-end API-driven runs across local and cloud-safe execution modes
 
 ## Progress
 
@@ -76,11 +59,10 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7 -> 8
 
 | Phase | Plans Complete | Status | Completed |
 |-------|----------------|--------|-----------|
-| 1. Workspace and Durable Run Foundation | 3/3 | Complete | 2026-03-21 |
-| 2. Manager-Led Orchestration Core | 3/3 | Complete | 2026-03-21 |
-| 3. Specialist Delegation and Routing Visibility | 3/3 | Complete | 2026-03-21 |
-| 4. Autonomous Repo Execution and Validation Guardrails | 3/3 | Complete | 2026-03-21 |
-| 5. Polished Operator Workbench | 3/3 | Complete | 2026-03-22 |
+| 1. Workspace and Durable Run Foundation | 3/3 | Complete | 2007-03-21 |
+| 2. Manager-Led Orchestration Core | 3/3 | Complete | 2007-03-21 |
+| 3. Specialist Delegation and Routing Visibility | 3/3 | Complete | 2007-03-21 |
+| 4. Autonomous Repo Execution and Validation Guardrails | 3/3 | Complete | 2007-03-21 |
+| 5. Polished Operator Workbench | 3/3 | Complete | 2007-03-22 |
 | 6. API Boundary and Control Plane Contract | 0/3 | Planned | - |
-| 7. Azure Functions Host and Durable API Surface | 0/3 | Planned | - |
-| 8. Worker Boundary and Cloud-Safe Execution Profiles | 0/3 | Planned | - |
+| 7. Worker Boundary and Cloud-Safe Execution Profiles | 0/3 | Planned | - |

.planning/STATE.md

@@ -1,16 +1,17 @@
 ---
 gsd_state_version: 1.0
 milestone: v1.1
-milestone_name: cloud-api-and-azure-function-hosting
-status: ready
-stopped_at: Phase 6 context gathered
-last_updated: "2026-03-22T19:11:41+02:00"
-last_activity: 2026-03-22 - Phase 6 context gathered
+milestone_name: milestone
+status: completed
+stopped_at: Phase 6 complete
+last_updated: "2026-04-15T19:56:10.036Z"
+last_activity: 2026-03-22 - Phase 6 complete - Plan 03 delivered Command Center parity tests, legacy compatibility notices, and README External API section
 progress:
-  total_phases: 8
-  completed_phases: 5
-  total_plans: 24
-  completed_plans: 15
+  total_phases: 2
+  completed_phases: 1
+  total_plans: 3
+  completed_plans: 4
+  percent: 100
 ---
 
 # Project State
@@ -20,20 +21,20 @@ progress:
 See: .planning/PROJECT.md (updated 2026-03-22)
 
 **Core value:** You can give one prompt and watch a trustworthy multi-agent coding system drive real repo work end-to-end with clear traces, specialist visibility, and minimal manual intervention.
-**Current focus:** Phase 6 context gathered - ready for planning
+**Current focus:** Phase 6 in progress - REST API complete
 
 ## Current Position
 
-Phase: 06 (api-boundary-and-control-plane-contract) - READY TO PLAN
-Plan: -
-Status: Phase context captured and ready for plan-phase
-Last activity: 2026-03-22 - Phase 6 context gathered
+Phase: 07 (azure-functions-and-cloud-control-plane) - READY TO START
+Plan: 07-01 (next)
+Status: Phase 6 complete - Shared control-plane API delivered with /api/v1 REST router, Command Center parity validation, and external API documentation. Ready for Azure Functions deployment.
+Last activity: 2026-03-22 - Phase 6 complete - Plan 03 delivered Command Center parity tests, legacy compatibility notices, and README External API section
 
 ## Performance Metrics
 
 **Velocity:**
 
-- Total plans completed: 15
+- Total plans completed: 18
 - Average duration: 1 min
 - Total execution time: 0.3 hours
 
@@ -46,10 +47,11 @@ Last activity: 2026-03-22 - Phase 6 context gathered
 | 03 | 3 | 3 min | 1 min |
 | 04 | 3 | 3 min | 1 min |
 | 05 | 3 | 3 min | 1 min |
+| 06 | 3 | 3 min | 1 min |
 
 **Recent Trend:**
 
-- Last 5 plans: 04-02 (1 min), 04-03 (1 min), 05-01 (1 min), 05-02 (1 min), 05-03 (1 min)
+- Last 5 plans: 05-02 (1 min), 05-03 (1 min), 06-01 (1 min), 06-02 (1 min), 06-03 (1 min)
 - Trend: Stable
 
 | Phase 01 P01 | 1 min | 2 tasks | 8 files |
@@ -67,6 +69,9 @@ Last activity: 2026-03-22 - Phase 6 context gathered
 | Phase 05 P01 | 1 min | 3 tasks | 4 files |
 | Phase 05 P02 | 1 min | 3 tasks | 5 files |
 | Phase 05 P03 | 1 min | 3 tasks | 6 files |
+| Phase 06 P01 | 1 min | 4 tasks | 4 files |
+| Phase 06 P02 | 1 min | 4 tasks | 4 files |
+| Phase 06 P03 | 1 min | 4 tasks | 4 files |
 
 ## Accumulated Context
 
@@ -87,7 +92,7 @@ Recent decisions affecting current work:
 - Phase 02 planning: Use one canonical manager stage sequence `planning -> research -> implementation -> review -> validation`
 - Phase 02 planning: Make stage-scoped pause, resume, and retry part of the durable run contract instead of transcript-only behavior
 - Phase 02 planning: Answer routine GSD clarification questions automatically from planning docs, phase context, workspace snapshot, and repo facts
-- Phase 02-01: Canonical stage state lives in `maf_starter/orchestration.py` and is shared by workflow builders and dashboard runtime
+- Phase 02-01: Canonical stage state lives in `maf_core/orchestration.py` and is shared by workflow builders and dashboard runtime
 - Phase 02-02: Planning pauses after plan output, while blocked or failed later stages resume from the same stage without replaying completed work
 - Phase 02-03: Operator-facing orchestration visibility is exposed through dashboard cards and API payloads, not only raw traces
 - Phase 03 context: Keep the manager as the only canonical run owner while surfacing `planner`, `researcher`, `implementer`, and `reviewer` as first-class visible specialists
@@ -132,6 +137,6 @@ None yet.
 
 ## Session Continuity
 
-Last session: 2026-03-22T19:11:41+02:00
-Stopped at: Phase 6 context gathered
-Resume file: .planning/phases/06-api-boundary-and-control-plane-contract/06-CONTEXT.md
+Last session: 2026-03-22T22:00:00+02:00
+Stopped at: Phase 6 complete
+Resume file: .planning/phases/06-api-boundary-and-control-plane-contract/06-03-SUMMARY.md