titan/atlas-iac
3
0
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

Complete direct CLI lane concurrency omitted by #30 (supersedes #31) #35

Merged
bstein merged 2 commits from feature/hermes-direct-cli-lane-concurrency-2-replacement into main 2026-08-21 07:58:18 +00:00
Conversation 1 Commits 2 Files Changed 2 +4 -2
hermes-automation commented 2026-08-21 07:14:29 +00:00
Member
Copy Link

Supersedes conflict-blocked draft PR #31, which is frozen and must remain unmerged. This replacement is based directly on current main at db70509e, including merged PR #30.

PR #30 persisted only the normal Hermes kanban.max_in_progress_per_profile cap of 2; it omitted the independent direct CLI lane setting. This PR completes that direct-lane half by setting HERMES_CLI_LANE_CONCURRENCY to 2 in execution-coordinator-patch.yaml. It intentionally does not touch agent-configmap.yaml or duplicate PR #30 coverage.

Preserved policy:

  • gateway api_server max_concurrent_runs remains 4
  • profile max_in_progress_per_profile remains 2 from main
  • provider quota/cooldowns remain 15/300/3600

Verification:

  • focused assignment/control-plane tests: 13 passed
  • source and kustomize-rendered Hermes values asserted
  • fresh current-main render comparison changes only direct CLI lane concurrency 1 -> 2
  • broader two-file run: 25 passed with 2 unrelated resource-expectation failures reproduced identically on pristine current main
  • git diff --check passed

Draft only; no merge, reconcile, or deploy. Once this replacement exists, Brad should close #31 unmerged.

Supersedes conflict-blocked draft PR #31, which is frozen and must remain unmerged. This replacement is based directly on current main at db70509e, including merged PR #30. PR #30 persisted only the normal Hermes kanban.max_in_progress_per_profile cap of 2; it omitted the independent direct CLI lane setting. This PR completes that direct-lane half by setting HERMES_CLI_LANE_CONCURRENCY to 2 in execution-coordinator-patch.yaml. It intentionally does not touch agent-configmap.yaml or duplicate PR #30 coverage. Preserved policy: - gateway api_server max_concurrent_runs remains 4 - profile max_in_progress_per_profile remains 2 from main - provider quota/cooldowns remain 15/300/3600 Verification: - focused assignment/control-plane tests: 13 passed - source and kustomize-rendered Hermes values asserted - fresh current-main render comparison changes only direct CLI lane concurrency 1 -> 2 - broader two-file run: 25 passed with 2 unrelated resource-expectation failures reproduced identically on pristine current main - git diff --check passed Draft only; no merge, reconcile, or deploy. Once this replacement exists, Brad should close #31 unmerged.
hermes-automation added 1 commit 2026-08-21 07:14:30 +00:00
bstein added 1 commit 2026-08-21 07:57:37 +00:00
bstein approved these changes 2026-08-21 07:58:08 +00:00
bstein changed title from WIP: Complete direct CLI lane concurrency omitted by #30 (supersedes #31) to Complete direct CLI lane concurrency omitted by #30 (supersedes #31) 2026-08-21 07:58:12 +00:00
bstein merged commit e3de466ad1 into main 2026-08-21 07:58:18 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
bstein
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
atlas-reconciler bstein hermes-automation
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: titan/atlas-iac#35
No description provided.
Delete Branch "feature/hermes-direct-cli-lane-concurrency-2-replacement"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?