cleveragents/cleveragents-core

Fork 3

bug(cli): project context set missing --execution-env-priority flag #1079

New issue

Closed

opened 2026-03-20 08:22:31 +00:00 by hurui200320 · 2 comments

hurui200320 commented

2026-03-20 08:22:31 +00:00

Member

Metadata

Commit Message: fix(cli): implement --execution-env-priority on project context set
Branch: bugfix/m8-project-exec-env-priority

Background

Specification Workflow Example 17 describes setting the execution environment priority at the project level via project context set --execution-env-priority override. However, the --execution-env-priority flag is currently only available on plan use, not on project context set. This prevents WF17 AC #3 (project-level override priority) from being satisfied.

Discovered during E2E testing in #763.

Expected Behavior

project context set should accept --execution-env-priority flag to set the execution environment priority at the project level (precedence level 2 per spec).

Acceptance Criteria

project context set accepts --execution-env-priority flag
Setting is persisted and retrievable via project context show
Project-level priority takes effect when no plan-level override exists
E2E test in WF17 suite exercises project-level override priority

Subtasks

Implement --execution-env-priority CLI flag on project context set
Persist execution env priority at project level
Verify priority propagation when no plan-level override exists
Remove @tdd_expected_fail from WF17 project-level override test case
Verify via nox -s e2e_tests

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

## Metadata - **Commit Message**: `fix(cli): implement --execution-env-priority on project context set` - **Branch**: `bugfix/m8-project-exec-env-priority` ## Background Specification Workflow Example 17 describes setting the execution environment priority at the project level via `project context set --execution-env-priority override`. However, the `--execution-env-priority` flag is currently only available on `plan use`, not on `project context set`. This prevents WF17 AC #3 (project-level override priority) from being satisfied. Discovered during E2E testing in #763. ## Expected Behavior `project context set` should accept `--execution-env-priority` flag to set the execution environment priority at the project level (precedence level 2 per spec). ## Acceptance Criteria - [x] `project context set` accepts `--execution-env-priority` flag - [x] Setting is persisted and retrievable via `project context show` - [x] Project-level priority takes effect when no plan-level override exists - [x] E2E test in WF17 suite exercises project-level override priority ## Subtasks - [x] Implement `--execution-env-priority` CLI flag on `project context set` - [x] Persist execution env priority at project level - [x] Verify priority propagation when no plan-level override exists - [x] Remove `@tdd_expected_fail` from WF17 project-level override test case - [x] Verify via `nox -s e2e_tests` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.

hurui200320 added the

labels

2026-03-20 08:22:57 +00:00

hurui200320 referenced this issue

2026-03-20 08:43:02 +00:00

test(e2e): workflow example 17 — explicit container with directory mount (trusted profile) #819

hurui200320 referenced this issue

2026-03-20 10:28:24 +00:00

test(e2e): workflow example 17 — explicit container with directory mount (trusted profile) #763

freemo referenced this issue

2026-03-22 16:30:11 +00:00

TDD: Write failing test for #1079 — project context set missing --execution-env-priority flag #1100

hurui200320 was assigned by freemo

2026-03-22 16:31:11 +00:00

freemo added this to the v3.5.0 milestone

2026-03-22 16:31:11 +00:00

freemo added

and removed

labels

2026-03-22 16:31:11 +00:00

freemo commented

2026-03-22 16:31:11 +00:00

Owner

Assigned to @hurui200320 for bug fix based on developer expertise (CLI flags — Rui). Milestone set to v3.5.0. State changed from Unverified to Verified. This bug is top priority per project policy — bugs always take precedence over feature work.

freemo added a new dependency

2026-03-22 16:32:54 +00:00

#1100 TDD: Write failing test for #1079 — project context set missing --execution-env-priority flag

freemo commented

2026-03-22 16:32:54 +00:00

Owner

TDD workflow initiated for this bug:

Created TDD issue #1100 to write a tagged test that captures this bug.
Dependency link added: this issue is blocked by #1100.
Once #1100 is merged to master, the bug fix assignee should create the bugfix branch and implement the fix.
The fix must remove the @tdd_expected_fail tag from the test so it runs normally.

TDD workflow initiated for this bug: - Created TDD issue #1100 to write a tagged test that captures this bug. - Dependency link added: this issue is blocked by #1100. - Once #1100 is merged to `master`, the bug fix assignee should create the bugfix branch and implement the fix. - The fix must remove the `@tdd_expected_fail` tag from the test so it runs normally.

hurui200320 was unassigned by freemo

2026-03-23 03:30:06 +00:00