Repository navigation
docs: mark Phase 4 complete; move access containment to Phase 5 - #42
Conversation
…hase 5 Phase 4's unified workflows shipped in 0.4.0 and the Tower connector in 0.3.6. Tool-level permissions, revocation at dispatch, stop/revoke, denial evidence and hosted Tower credentials protect hosted users rather than add workflows, so they become Phase 5 hosted access control. Phase 5's publishing goals are recorded as in place.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 31ff0e32a1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - **Phase 4: Unified Workflows** ✅ Complete — unified comparison, | ||
| fail-closed release-check, incident-summary and report-export tools in | ||
| `0.4.0`; local Tower connector since `0.3.6` | ||
| - **Phase 5: Publishing and Adoption** 🏗️ In progress — PyPI, GitHub Release, | ||
| MCP Registry and AWS release automation are in place; hosted access control | ||
| (tool-level permissions, revocation at dispatch, denial evidence, hosted Tower | ||
| credentials) moved here from Phase 4 on 2026-10-19 |
There was a problem hiding this comment.
This changes the public milestone status and reassigns access-containment work, but the patch updates only this repository; the repository guidance requires a corresponding update to the shared .github profile documentation when a milestone change affects the public ecosystem story. Without coordinating profile/README.md and, where relevant, profile/ROADMAP.md, the organization-level roadmap will continue advertising the previous Phase 4/5 plan.
AGENTS.md reference: AGENTS.md:L158-L162
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
🟡 Changes recommended
Documentation inconsistencies and a line-length issue remain unresolved.
1 open issue
What changed in this PR
Updates documentation to mark Phase 4 complete and move hosted access-control work to Phase 5.
Changes:
- Updates roadmap and project status documentation.
- Reclassifies hosted access-control milestones.
- Records the status change in the changelog.
| File | Summary | Review notes |
|---|---|---|
ROADMAP.md |
Updates Phase 4/5 status and milestones | Resolve Phase 5/6 labeling and audit-status contradiction. |
README.md |
Reflects updated project status | No final comments. |
docs/unified-workflows.md |
Clarifies Phase 4 completion | No final comments. |
docs/roadmap.md |
Updates roadmap summary | No final comments. |
CHANGELOG.md |
Records the documentation change | Clarify contradictory Phase 4 completion wording. |
AGENTS.md |
Updates current roadmap focus | Wrap the overlong Phase 5 description. |
Review effort: Lite
|
|
||
| ## 0.4.0 - 2026-10-19 | ||
|
|
||
| First Phase 4 (Unified Workflows) slice. No sibling release, dependency range |
There was a problem hiding this comment.
Fixed: the Unreleased note now says this is a roadmap decision made after 0.4.0 shipped, and that the 0.4.0 notes still call it the first slice. I left the published 0.4.0 release notes unchanged on purpose.
Phase 4 (Unified Workflows) is complete as of 0.4.0: the unified
core.*tools shipped in 0.4.0 and the local Tower connector in 0.3.6.The access-containment items move to a Phase 5 hosted access control workstream: tool-level permissions per key, revocation re-checked at dispatch, authenticated Tower/Sidecar stop/revoke, correlated denial evidence and per-user hosted Tower credentials. They protect hosted users rather than add workflows, and they need spec, Sidecar and Tower work first.
Phase 5 is now marked in progress, and its publishing goals (PyPI, MCP Registry,
server.json, release CI) are recorded as done. Docs only; no release.