4 Commits

Author	SHA1	Message	Date
hurui200320	e2b127b7e5	fix(e2e): replace naive OpenAI key-presence check with live API probe in E2E suite setups ... The existing actor-selection logic in several E2E suite setups checked only whether OPENAI_API_KEY was present (non-empty). A valid key that has hit its quota limit passes that check but fails at runtime with HTTP 429, causing the test to fail even though Anthropic credits are available. Changes: - Add robot/e2e/check_openai_key.py: stdlib-only (urllib.request) script that sends a minimal chat-completion request ('Hi', max_tokens=1, gpt-4o-mini) to the OpenAI API. Exits 0 on HTTP 200; exits 1 for quota (429), auth (401), network errors, or any other failure. - Add 'Resolve LLM Actor' keyword to robot/e2e/common_e2e.resource: runs the probe script via ${PYTHON} and returns the openai_model argument (default openai/gpt-4o) on success, or the anthropic_model argument (default anthropic/claude-sonnet-4-20250514) on failure. Skips the probe entirely when OPENAI_API_KEY is not set. - Update m6_acceptance.robot, wf04_multi_project.robot, wf05_db_migration.robot, wf07_cicd.robot, and wf16_devcontainer.robot to use 'Resolve LLM Actor' instead of the inline has_openai boolean check. No production source code (src/) is modified. The decision to fall back to Anthropic is made once per suite setup, before any test runs. Closes #10198	2026-04-17 18:00:47 +08:00
freemo	8ea00f5185	fix: restore CI quality tests to passing state (#4175) ... Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>	2026-04-08 11:02:14 +00:00
freemo	48cff5cfe0	refactor(cli): rename plan lifecycle-list and lifecycle-apply to match specification ... Renames `plan lifecycle-list` to `plan list` and `plan lifecycle-apply` to `plan apply` to align with the specification's canonical command names. Removes legacy V2 plan commands that occupied those names. - Renamed CLI command registrations from lifecycle-list/lifecycle-apply to list/apply - Removed legacy V2 apply and list commands (~200 lines) - Updated apply shortcut in main.py to delegate to v3 lifecycle - Added defensive null check for plan existence in apply command - Updated 63+ test, doc, and benchmark files for consistency Closes #881 Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>	2026-04-02 19:09:04 +00:00
freemo	845cf61b47	test(e2e): workflow example 4 — multi-project dependency update (supervised profile) ... Implement WF04 E2E test coverage for multi-project dependency update using the supervised automation profile. A parent plan targets four projects (common-lib + 3 services), spawns child subplans per project, executes in dependency order, validates per project, and applies in dependency order. Key components: - Robot test (robot/e2e/wf04_multi_project.robot): full supervised workflow exercising plan use, strategize, execute, validate, apply, and final status. JSON output parsing via raw_decode for resilience. Test-level guard skips the entire test (visible SKIPPED in CI) when the LLM produces zero subplans, preventing silent AC-4/5/6/7 bypass. Count Decision Nodes keyword delegates to the Python helper to avoid duplicating recursive tree-walking logic. - Snapshot helper (robot/e2e/wf04_snapshot_helper.py): collects deterministic parent/subplan metadata from the lifecycle service. Timestamps normalised to UTC. Depth-guarded count_decision_nodes() function (max_depth=50) for safe reuse from Robot keywords. sys.path.append (not insert) to avoid shadowing the standard library. - Behave unit tests (features/wf04_snapshot_helper.feature + steps): 17 scenarios covering _iso(), _enum_value(), count_decision_nodes(), and _build_snapshot() with mocked lifecycle service. Includes tests for no-subplans (verifies plan_id, project_scopes, validation_summary), with-subplans (verifies concrete mapped project names and subplan_count), child-plan-is-None (verifies empty-string defaults), unmapped resources, and exact-match aware-datetime UTC normalisation. ISSUES CLOSED: #750	2026-03-30 11:47:37 +08:00