fix: restore runnable enterprise-grade autogen workbench#1
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 55866e1a78
ℹ️ 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".
| ## Demo Scenarios | ||
|
|
||
| The best way to understand the product is through operator outcomes: |
There was a problem hiding this comment.
For a new user trying any of these demo scenarios from a clean clone, this rewrite removes the only Quickstart and configuration guidance without replacing it. A repo-wide tree search also finds no dependency manifest, .env.example, launcher, or documented start command, so readers cannot determine how to install or run the advertised workbench. Please restore concrete setup/configuration/run instructions or link to an existing runnable guide.
Useful? React with 👍 / 👎.
|
|
||
| - `tests/test_workspace_contract.py` validates workspace discovery, repo-root safety, and session creation contracts against real temporary git repos. | ||
| - `tests/test_run_persistence.py` verifies durable session layout, artifact manifests, attempts, diffs, validation outputs, and atomic persistence behavior. | ||
| - `tests/test_phase4_approval.py` proves destructive writes and externally visible commands are classified and paused behind approval. |
There was a problem hiding this comment.
Qualify the approval-test evidence claim
From a clean checkout, the cited approval suite cannot collect: tests/test_phase4_approval.py imports autogen_starter.config and autogen_starter.providers, but a repo-wide search of this commit finds no autogen_starter package. Since CI runs only the two static UI suites, it does not establish this claim either. Restore the missing runtime package or qualify the statement rather than presenting this test as executable proof.
Useful? React with 👍 / 👎.
…0' into docs/portfolio-hardening-20260610
…0' into docs/portfolio-hardening-20260610
Summary
Verification
Manual follow-up