You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Phase: 07 (azure-functions-and-cloud-control-plane) - READY TO START
29
29
Plan: 07-01 (next)
30
30
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.
31
-
Last activity: 2026-03-22 - Phase 6 complete - Plan 03 delivered Command Center parity tests, legacy compatibility notices, and README External API section
31
+
Last activity: 2026-06-10 - Completed quick task 260610-ppt: PR #1 follow-up truthful Quickstart and Configuration guidance
32
32
33
33
## Performance Metrics
34
34
@@ -135,6 +135,12 @@ None yet.
135
135
- Local Python is `3.14.2`, but Azure Functions hosted deployment work should target GA-supported Python such as `3.13` or `3.12`
136
136
- A cloud-hosted control plane cannot assume local CLI logins, desktop-bound tooling, or direct repo access unless a compatible worker is attached
137
137
138
+
### Quick Tasks Completed
139
+
140
+
| # | Description | Date | Commit | Status | Directory |
| F-01 | High | Auto-fixable | Clean clone could not collect the shipped full test suite because required runtime modules and dependency/bootstrap files were missing. |
8
+
| F-02 | High | Auto-fixable | CI ran only two static contract tests and could report green while the broader suite was broken. |
9
+
| F-03 | High | Auto-fixable |`SessionStore` composed unvalidated session, stage, and attempt identifiers into filesystem paths. |
10
+
| F-04 | High | Auto-fixable | Dashboard CORS allowed wildcard origins with credentials. |
11
+
| F-05 | Medium | Auto-fixable | Repo write operations accepted arbitrary encodings and used non-atomic direct writes. |
12
+
| F-06 | Medium | Auto-fixable | Missing `.gitignore` exposed secrets and runtime/test artifacts to accidental commits. |
13
+
| F-07 | Medium | Manual-only | Legacy dashboard and MAF runtime contracts overlap and require an architectural consolidation decision. |
14
+
| F-08 | Medium | Manual-only | Production authentication, worker isolation, and remote deployment boundaries remain intentionally unimplemented. |
`agent-framework-core 1.0.0rc5` expects `azure-ai-projects>=2.0.0,<3.0`, while the shared environment contains `azure-ai-projects 2.0.0b3`.
16
+
CI installs from `requirements.txt` in a clean environment and now treats dependency consistency as a required gate.
17
+
18
+
## Manual Verification Remaining
19
+
20
+
- Observe the Windows and Linux GitHub Actions jobs on PR #1. The workflow was committed through the authenticated GitHub connector because the local GitHub CLI token does not carry the `workflow` scope.
21
+
- Exercise one real provider-backed dashboard run with a non-production key.
22
+
- Decide whether to consolidate or retire the parallel legacy and MAF runtime contracts.
23
+
- Define production authentication and isolated worker execution before any non-loopback deployment.
# PR #1 follow-up: truthful Quickstart and Configuration guidance
9
+
10
+
## Goal
11
+
12
+
Restore practical README guidance that helps readers validate and understand the checked-in repository without claiming a missing dependency manifest, `.env.example`, launcher, or supported full-runtime bootstrap.
13
+
14
+
## Must Haves
15
+
16
+
- Quickstart commands operate against files present on `docs/portfolio-hardening-20260610`.
17
+
- The README clearly distinguishes the CI-aligned static contract tests from a full runtime launch.
18
+
- Configuration guidance is derived from `maf_starter/config.py` and does not claim an `.env.example` exists.
19
+
- Validation includes the documented test command, README claim checks, and `git diff --check`.
20
+
21
+
## Tasks
22
+
23
+
### Task 1: Restore truthful operator guidance
24
+
25
+
**Files:**`README.md`
26
+
27
+
**Action:** Add a Quickstart that runs the same static contract tests as CI, disclose the current runtime-bootstrap limitations, and add a configuration reference based only on variables read by `maf_starter/config.py`.
28
+
29
+
**Verify:** Confirm every named repository path exists and every documented command is appropriate for this snapshot.
30
+
31
+
**Done:** Readers can validate the portfolio evidence and understand configuration boundaries without being told to use missing files or unsupported launch commands.
**Action:** Run the CI-aligned tests and `git diff --check`, verify README claims against tracked files and configuration source, then record the quick-task result.
38
+
39
+
**Verify:** All validation commands pass and the final commit contains only the README follow-up and GSD quick-task artifacts/state.
40
+
41
+
**Done:** The task is documented, verified, atomically committed, and ready to push on the existing PR branch.
Restored practical README Quickstart and Configuration guidance for PR #1 without presenting the incomplete repository snapshot as a supported full-runtime distribution.
11
+
12
+
## Delivered
13
+
14
+
- Added a PowerShell Quickstart that runs the same dependency-light operator-workbench contract tests used by CI.
15
+
- Explicitly documented the missing dependency manifest, `.env.example`, launcher, and legacy dashboard imports that prevent a truthful clean-clone runtime launch command.
16
+
- Added a configuration table derived from environment variables actually read by `maf_starter/config.py`.
Restore practical, truthful Quickstart and Configuration guidance without claiming missing files or unsupported runtime bootstrap.
12
+
13
+
## Result
14
+
15
+
Passed. The README now provides an executable CI-aligned validation path, identifies the full-runtime bootstrap as unsupported in the checked-in snapshot, and documents configuration from `maf_starter/config.py`.
16
+
17
+
## Evidence
18
+
19
+
- The documented pytest command completed with 16 passing tests.
20
+
-`README.md`, `maf_starter/config.py`, the two documented tests, and `.github/workflows/ci.yml` exist.
21
+
-`requirements.txt`, `pyproject.toml`, `setup.py`, `.env.example`, `main.py`, and `autogen_starter/` are absent, matching the README limitation statement.
22
+
- Configuration names and defaults were checked against `load_settings()` in `maf_starter/config.py`.
23
+
-`git diff --check` passed before the implementation commit.
0 commit comments