cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

chore: integration batch — 6 features/tasks for v3.2.0, v3.4.0, v3.5.0 #508

Closed
freemo wants to merge 12 commits from integration/batch-2026-03-02 into master
pull from: integration/batch-2026-03-02
merge into: cleveragents:master
Conversation 1 Commits 12 Files changed 211 +27674 -18501
freemo commented 2026-03-02 08:34:58 +00:00
Owner
Copy link

Summary

Integration branch combining 6 independently implemented feature branches, all verified against the full nox suite (lint, typecheck, unit_tests, integration_tests, coverage_report).

Included PRs

PR Issue Title Milestone
#502 #485 perf(tests): consolidate 141 small feature files v3.2.0
#503 #486 perf(tests): add ASV benchmarks for test runtime v3.2.0
#504 #259 feat(config): add project-scoped config overrides v3.4.0
#505 #190 feat(acms): add context request protocol models v3.4.0
#506 #197 feat(service): add subplan service and spawn workflow v3.4.0
#507 #201 feat(interfaces): add server client stubs v3.5.0

Quality Gates — ALL PASSED

  • lint: PASS (ruff check — 0 issues)
  • typecheck: PASS (Pyright strict — 0 errors)
  • unit_tests: PASS (7612 scenarios, 239 features, 0 failures)
  • integration_tests: PASS (1023/1023 robot tests)
  • coverage_report: PASS (98% overall)

Merge Conflicts Resolved

  • vulture_whitelist.py: Both #197 (subplan) and #201 (server-stubs) added entries — combined both sections.
  • config_service.py: Auto-merged cleanly (both #259 and #201 added config keys in non-overlapping sections).

Notes

  • One conflict between cli_core.feature server_mode assertions and the server-stubs feature was caused by a leftover config.toml from a prior test run — not a code issue. Tests pass cleanly in a fresh environment.
  • All 6 individual PRs remain open for per-feature review; this integration PR validates that they combine cleanly.
## Summary Integration branch combining 6 independently implemented feature branches, all verified against the full nox suite (lint, typecheck, unit_tests, integration_tests, coverage_report). ### Included PRs | PR | Issue | Title | Milestone | |----|-------|-------|-----------| | #502 | #485 | perf(tests): consolidate 141 small feature files | v3.2.0 | | #503 | #486 | perf(tests): add ASV benchmarks for test runtime | v3.2.0 | | #504 | #259 | feat(config): add project-scoped config overrides | v3.4.0 | | #505 | #190 | feat(acms): add context request protocol models | v3.4.0 | | #506 | #197 | feat(service): add subplan service and spawn workflow | v3.4.0 | | #507 | #201 | feat(interfaces): add server client stubs | v3.5.0 | ### Quality Gates — ALL PASSED - **lint**: PASS (ruff check — 0 issues) - **typecheck**: PASS (Pyright strict — 0 errors) - **unit_tests**: PASS (7612 scenarios, 239 features, 0 failures) - **integration_tests**: PASS (1023/1023 robot tests) - **coverage_report**: PASS (98% overall) ### Merge Conflicts Resolved - `vulture_whitelist.py`: Both #197 (subplan) and #201 (server-stubs) added entries — combined both sections. - `config_service.py`: Auto-merged cleanly (both #259 and #201 added config keys in non-overlapping sections). ### Notes - One conflict between `cli_core.feature` server_mode assertions and the server-stubs feature was caused by a leftover `config.toml` from a prior test run — not a code issue. Tests pass cleanly in a fresh environment. - All 6 individual PRs remain open for per-feature review; this integration PR validates that they combine cleanly.
perf(tests): consolidate 141 trivially small feature files into 34 domain groups
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 23s
Details
CI / typecheck (pull_request) Successful in 35s
Details
CI / security (pull_request) Successful in 37s
Details
CI / unit_tests (pull_request) Successful in 3m2s
Details
CI / integration_tests (pull_request) Successful in 4m37s
Details
CI / docker (pull_request) Successful in 43s
Details
CI / coverage (pull_request) Successful in 3m49s
Details
CI / benchmark-regression (pull_request) Successful in 22m48s
Details
6088730897 
Consolidate 141 BDD feature files that each complete in under 0.1 seconds
into 25 domain-grouped feature files, reducing subprocess count from 339
to ~223. Each consolidated file groups scenarios from the same domain/module
that share step definitions and fixtures. All scenarios are preserved with
clear comment headers indicating their original source file.

This reduces subprocess overhead by ~116 invocations (141 original files
replaced by 25 consolidated files), targeting the 42% of subprocess count
that contributed only 0.2% of actual test runtime.

ISSUES CLOSED: #485
feat(service): add subplan service and spawn workflow
All checks were successful
CI / lint (pull_request) Successful in 16s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 29s
Details
CI / typecheck (pull_request) Successful in 55s
Details
CI / security (pull_request) Successful in 57s
Details
CI / unit_tests (pull_request) Successful in 2m58s
Details
CI / integration_tests (pull_request) Successful in 4m10s
Details
CI / docker (pull_request) Successful in 47s
Details
CI / coverage (pull_request) Successful in 3m48s
Details
CI / benchmark-regression (pull_request) Successful in 22m45s
Details
749e56eb4f 
Add SubplanService for building child plans from DecisionService spawn
entries and SubplanConfig. The service validates resource scopes, merge
strategies, and max_parallel bounds before spawning.

Key additions:
- SubplanService: Orchestrates child plan creation from spawn entries
- SpawnMetadata: Persisted metadata (spawn_decision_id, parent/root
  plan IDs, execution mode) for status output
- Spawn validation: Checks resource scopes, merge strategy, and
  parallelism bounds before spawning
- Documentation: subplan_service.md with spawn workflow and lifecycle

ISSUES CLOSED: #197
feat(acms): add context request protocol models
All checks were successful
CI / lint (pull_request) Successful in 14s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / quality (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 15s
Details
CI / security (pull_request) Successful in 53s
Details
CI / unit_tests (pull_request) Successful in 3m18s
Details
CI / integration_tests (pull_request) Successful in 3m55s
Details
CI / docker (pull_request) Successful in 40s
Details
CI / coverage (pull_request) Successful in 3m42s
Details
CI / benchmark-regression (pull_request) Successful in 22m48s
Details
7687c5e9b0 
Add CRP domain models for the Advanced Context Management System:
- ContextRequest: Focus-driven context retrieval with breadth, depth,
  strategy, temporal_scope, and skeleton_ratio parameters
- ContextFragment: Retrieved context with UKO URI, provenance,
  relevance score, token count, and detail level metadata
- ContextBudget: Token budget management with reservation support
- DetailLevel: Five-tier enum (skeleton through full)
- DetailLevelMap: Name-to-integer resolution registry with inheritance

Add builtin/context skill with stubbed tools (request_context,
query_history, get_context_budget) wired to future ACMS pipeline.

ISSUES CLOSED: #190
perf(tests): add ASV benchmarks for test suite runtime regression tracking
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Details
CI / lint (pull_request) Successful in 18s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / security (pull_request) Successful in 37s
Details
CI / unit_tests (pull_request) Successful in 3m12s
Details
CI / integration_tests (pull_request) Successful in 4m51s
Details
CI / docker (pull_request) Successful in 40s
Details
CI / coverage (pull_request) Successful in 4m19s
Details
CI / benchmark-regression (pull_request) Successful in 23m16s
Details
8683f36817 
Add ASV benchmark modules to track test suite performance over time:
- bench_unit_tests.py: Feature discovery, step module loading, parallel
  chunk computation, behave config parsing, and test suite metrics
- bench_coverage_report.py: Coverage collection pipeline timing and
  report generation overhead
- bench_subprocess_overhead.py: Subprocess count tracking and per-feature
  startup cost measurement

These benchmarks establish baselines for the post-optimization state
and enable CI-driven regression detection.

ISSUES CLOSED: #486
feat(config): add project-scoped config overrides
All checks were successful
CI / lint (pull_request) Successful in 15s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / security (pull_request) Successful in 51s
Details
CI / unit_tests (pull_request) Successful in 2m57s
Details
CI / integration_tests (pull_request) Successful in 4m34s
Details
CI / docker (pull_request) Successful in 39s
Details
CI / coverage (pull_request) Successful in 3m39s
Details
CI / benchmark-regression (pull_request) Successful in 22m18s
Details
b49059209a 
Add --project flag to config set, config get, and config list CLI
commands, enabling per-project configuration overrides stored under
[project."<name>"] TOML tables in the global config file.

Project-scoped resolution slots between environment variable and global
levels in the ConfigService resolution chain. config list --project
shows only overrides for the named project with source annotations.

Implementation:
- ConfigService: add set_project_value() and get_project_overrides()
  methods for TOML-backed project-scoped persistence and retrieval
- CLI config commands: wire --project flag through set, get, and list
  subcommands; project-scoped list filters to overrides only
- Database persistence: project-scoped config stored as alternative
  backend for projects not using TOML
- Documentation: update docs/reference/config_resolution.md with
  project-scopable key lists, CLI examples, precedence diagram, and
  non-scopable key rejection behavior

Tests:
- Behave: 12 BDD scenarios in features/config_project_scope.feature
  covering set/get/list, precedence over global defaults, and
  non-scopable key rejection
- Robot: 5 integration smoke tests in robot/config_project_scope.robot
  for end-to-end project-scoped round-trip verification
- ASV: benchmarks/config_project_scope_bench.py measuring resolution
  overhead with project scope active

All nox quality gates pass: lint, typecheck, unit_tests (7522 scenarios),
integration_tests (Config Project Scope suite passed), and coverage at
98% line rate (threshold 97%).

Closes #259
feat(interfaces): add server client stubs
All checks were successful
CI / lint (pull_request) Successful in 21s
Details
CI / quality (pull_request) Successful in 35s
Details
CI / security (pull_request) Successful in 47s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / typecheck (pull_request) Successful in 1m17s
Details
CI / build (pull_request) Successful in 19s
Details
CI / unit_tests (pull_request) Successful in 2m43s
Details
CI / integration_tests (pull_request) Successful in 3m26s
Details
CI / docker (pull_request) Successful in 40s
Details
CI / coverage (pull_request) Successful in 3m43s
Details
CI / benchmark-regression (pull_request) Successful in 22m20s
Details
5cb7dd42fb 
Add protocol stubs for remote server communication infrastructure:
- ServerClient: Health check and version negotiation protocol
- RemoteExecutionClient: Remote plan execution and status protocol
- AuthClient: Authentication and token management protocol
- StubServerClient/StubRemoteExecutionClient/StubAuthClient: Stub
  implementations raising NotImplementedError for all methods
- ServerConnectionConfig: Validated config model (server_url, namespace,
  auth_token_ref, tls_verify)
- Config keys: core.server_url, core.server_namespace, core.server_tls_verify
- CLI: agents connect <url> stub command with explicit warning
- CLI: agents info shows Server Mode (disabled/stubbed)

ISSUES CLOSED: #201
Merge remote-tracking branch 'origin/feature/m6-server-stubs' into integration/batch-2026-03-02
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 13s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 30s
Details
CI / security (pull_request) Successful in 31s
Details
CI / unit_tests (pull_request) Successful in 1m43s
Details
CI / docker (pull_request) Successful in 38s
Details
CI / integration_tests (pull_request) Successful in 2m53s
Details
CI / coverage (pull_request) Successful in 3m43s
Details
CI / benchmark-regression (pull_request) Successful in 22m43s
Details
8dce196184 
# Conflicts:
#	vulture_whitelist.py
freemo commented 2026-03-02 14:49:26 +00:00
Author
Owner
Copy link

Closing as I am merging via individual PR

Closing as I am merging via individual PR
freemo closed this pull request 2026-03-02 14:49:27 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 13s
Required
Details
CI / build (pull_request) Successful in 16s
Required
Details
CI / quality (pull_request) Successful in 17s
Required
Details
CI / typecheck (pull_request) Successful in 30s
Required
Details
CI / security (pull_request) Successful in 31s
Required
Details
CI / unit_tests (pull_request) Successful in 1m43s
Required
Details
CI / docker (pull_request) Successful in 38s
Required
Details
CI / integration_tests (pull_request) Successful in 2m53s
Required
Details
CI / coverage (pull_request) Successful in 3m43s
Required
Details
CI / benchmark-regression (pull_request) Successful in 22m43s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!508
No description provided.