feat(ci): parallel coverage engine + explicit-gated coverage job; de-razor coverage to 96.62% #11258

Merged

HAL9000 merged 5 commits from coverage-engine-master-port into master 2026-06-02 03:34:31 +00:00

Conversation 3 Commits 5 Files Changed 9

+724 -90

HAL9000 commented 2026-06-01 21:13:45 +00:00

Owner

Copy Link

Copy Source

Phase 2 — parallel coverage engine → master + de-razored coverage

Ports the fast/parallel slipcover coverage engine onto master, reconciles the coverage gate to a single source, and adds genuine coverage headroom.

noxfile.py — coverage_report full-suite path now fans out K concurrent slipcover processes (K=COVERAGE_PROCESSES, default 4) over N bin-packed chunks, fails loud on any dead chunk (never merges survivors), and merges per-chunk JSON. Bounds per-process peak RSS (~658 MB/chunk, ceiling ~2.6 GB) — kills the single-process OOM/reaper collapse (~1.4 GB). COVERAGE_THRESHOLD reads pyproject [tool.coverage.report].fail_under. Features enumerated by glob (no run_behave_parallel orchestrator import).

pyproject.toml — adds [tool.coverage.report].fail_under = 96.5 as the single source of truth (+ evidence-gated ratchet rule, objective 97%).

.forgejo/workflows/ci.yml — coverage job carries the skip_coverage operator valve; propagates nox's exit explicitly (set -uo pipefail + PIPESTATUS + exit $rc) instead of relying on the runner's implicit pipefail; adds timeout-minutes: 30; deletes the dead threshold=50 step; fixes the phantom-97 label.

Coverage — de-razored from 96.465% (passed only by rounding) to 96.623% (genuine buffer): omit the TYPE_CHECKING-only application/services/__init__.py (uncoverable, slipcover has no per-line pragma) + new coverage_validation_error_paths.feature (16 scenarios over core/validation.py defensive branches). fail_under stays 96.5 (ratchet rule).

Local full engine run on master's suite: NOX_EXIT=0, all 12 chunks alive, 96.623%.

🤖 Generated with Claude Code

## Phase 2 — parallel coverage engine → master + de-razored coverage Ports the fast/parallel slipcover coverage engine onto master, reconciles the coverage gate to a single source, and adds genuine coverage headroom. **noxfile.py** — `coverage_report` full-suite path now fans out K concurrent slipcover processes (K=`COVERAGE_PROCESSES`, default 4) over N bin-packed chunks, fails loud on any dead chunk (never merges survivors), and merges per-chunk JSON. Bounds per-process peak RSS (~658 MB/chunk, ceiling ~2.6 GB) — kills the single-process OOM/reaper collapse (~1.4 GB). `COVERAGE_THRESHOLD` reads `pyproject [tool.coverage.report].fail_under`. Features enumerated by glob (no `run_behave_parallel` orchestrator import). **pyproject.toml** — adds `[tool.coverage.report].fail_under = 96.5` as the single source of truth (+ evidence-gated ratchet rule, objective 97%). **.forgejo/workflows/ci.yml** — coverage job carries the `skip_coverage` operator valve; propagates nox's exit **explicitly** (`set -uo pipefail` + `PIPESTATUS` + `exit $rc`) instead of relying on the runner's implicit pipefail; adds `timeout-minutes: 30`; deletes the dead `threshold=50` step; fixes the phantom-97 label. **Coverage** — de-razored from 96.465% (passed only by rounding) to **96.623%** (genuine buffer): omit the TYPE_CHECKING-only `application/services/__init__.py` (uncoverable, slipcover has no per-line pragma) + new `coverage_validation_error_paths.feature` (16 scenarios over `core/validation.py` defensive branches). `fail_under` stays 96.5 (ratchet rule). Local full engine run on master's suite: NOX_EXIT=0, all 12 chunks alive, 96.623%. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

HAL9000 added 2 commits 2026-06-01 21:13:45 +00:00

feat(ci): parallel coverage engine + explicit nox-gated coverage job (Phase 2) ... 4dec646e2f

Ports the WS1 fast/parallel coverage engine onto master and reconciles the
coverage gate to a single source. Local full-suite run on master's suite:
NOX_EXIT=0, all 12 chunks alive (no dead chunks), peak 658MB/chunk
(ceiling ~2.6GB vs the old ~1.4GB single-process that OOMs/reaper-kills),
96.465% -> 96.5 (rounded) >= 96.5 floor.

noxfile.py — coverage_report full-suite path now fans out K concurrent
slipcover processes (K=COVERAGE_PROCESSES, default 4) over N bin-packed
chunks (by scenario count), failing loud on any dead chunk (never merges
survivors) and merging per-chunk JSON. Bounds per-process peak RSS, killing
the single-process OOM/reaper collapse. Targeted (.feature posargs) runs keep
the single-process path. COVERAGE_THRESHOLD now reads
pyproject [tool.coverage.report].fail_under. Features are enumerated by direct
glob (NOT by importing run_behave_parallel, whose top level imports
behave/behave_parallel and is unavailable in the nox orchestrator process).

pyproject.toml — adds [tool.coverage.report].fail_under = 96.5 as the single
source of truth, with the evidence-gated ratchet rule (objective 97%).

.forgejo/workflows/ci.yml — coverage job: carries the skip_coverage operator
valve; propagates nox's exit EXPLICITLY (set -uo pipefail + PIPESTATUS +
exit $rc) instead of relying on the runner's implicit bash -eo pipefail;
adds timeout-minutes: 30 so a hang fails cleanly with diagnostics; deletes
the dead threshold=50 "Surface coverage summary" step; fixes the phantom-97
step label. Gating remains nox's --fail-under (sourced from pyproject).

coverage_threshold_config_steps.py — the fail-under feature step resolves the
floor from pyproject when COVERAGE_THRESHOLD delegates to the reader.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

test(coverage): de-razor master coverage 96.465% -> 96.623% ... a49f37eb1f

Master passed the 96.5 floor only by rounding (96.465 -> 96.5). Add genuine
behave coverage + omit a structurally-uncoverable module so the floor has real
headroom. fail_under stays 96.5 (ratchet rule: raise only after coverage holds).

- omit src/cleveragents/application/services/__init__.py (noxfile + pyproject):
  100% of its "missing" lines are inside an `if TYPE_CHECKING:` block (never
  executes at runtime) and slipcover has no per-line pragma to exclude them.
- features/coverage_validation_error_paths.feature (+ steps): 16 scenarios
  exercising the defensive error-path branches in core/validation.py that the
  existing structural_validation.feature does not reach (non-dict node, dup
  decision_id, non-list children, invalid child ULID, missing decision fields,
  wrong-typed confidence/parent/sequence, malformed structured-output, unknown
  dispatcher target). Routed through the public
  validate_structured_component_output dispatcher; pure functions, no DB/CLI.

Full engine run: NOX_EXIT=0, no dead chunks, 96.623% (validation.py now fully
covered).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

drew added 1 commit 2026-06-01 21:37:28 +00:00

fix(coverage): resolve fail-under from pyproject in threshold-enforcement step (WS5) ... b499834c0f

The coverage_report noxfile session now delegates COVERAGE_THRESHOLD to the
pyproject single source (`COVERAGE_THRESHOLD = _read_coverage_fail_under()`),
so the AST value is a Call, not a Constant. The
coverage_threshold_enforcement.feature step "I parse the COVERAGE_THRESHOLD
constant from noxfile.py" raised ValueError (errored scenario) because it only
handled a literal constant — this was the missed third WS5 step file (the
config + consolidated steps were already reconciled).

Add the same pyproject `[tool.coverage.report].fail_under` fallback used by
coverage_threshold_config_steps.py, and fix the phantom-97 in the feature
description prose. Verified: the four coverage feature files now pass
(136 scenarios, 0 errored); previously unit_tests errored on
coverage_threshold_enforcement.feature:7.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

drew added 1 commit 2026-06-02 02:11:58 +00:00

fix(coverage): reconcile robot coverage-threshold test with pyproject delegation (WS5) ... 8119043837

integration_tests (Robot/pabot) failed on robot/coverage_threshold.robot
"Noxfile Contains Coverage Threshold Constant": it asserted the literal
`COVERAGE_THRESHOLD = 96.5` in noxfile.py, but the coverage_report session now
delegates the constant to pyproject's single source
(`COVERAGE_THRESHOLD = _read_coverage_fail_under()`).

This was the last WS5 reconciliation gap (the plan enumerated behave feature
steps + ci.yml + guidelines prose, but not the Robot suite). Assert the
delegation plus the pyproject floor (`fail_under = 96.5`) instead of the literal,
mirroring the behave step fix in b499834c0. The other assertions in the suite
(--fail-under= substring, [tool.coverage.run], branch=true, source=["src"]) are
unaffected; verified no other robot/behave/pytest test depends on the literal.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

drew added 1 commit 2026-06-02 02:32:47 +00:00

perf(ci): raise pabot integration parallelism cap min(2)->min(6) ... 11c0fd11d5

integration_tests was throttled to `min(2, _default_processes())` (commit
92e258535, a flaky-stabilization measure). Evidence from a cached CI run shows
the suite does ~47min of work serialized through 2 pabot lanes on a 32-core
runner -> ~24min wall (exactly 2x == 2 lanes), the chronic ~21-30min seen
across recent runs. It is linearly parallelism-bound.

Raise the cap to `min(6, _default_processes())`: ~4x more lanes -> projected
~6-8min wall, while staying well short of per-core fan-out (the runner reports
32 cores; behave already uses all of them). The cap is kept (not removed)
because the suite makes live LLM calls — ~149 HTTP 429 rate-limit responses
were observed even at 2-way, and unbounded fan-out would spike 429/OOM flakes
(the exact failure 92e258535 was masking). 6 is a deliberate middle ground;
TEST_PROCESSES / --processes still override.

Updates the now-stale "<=2 processes" docstrings on integration_tests and
slow_integration_tests. Behave/unit_tests parallelism (_default_processes(),
uncapped) is unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

HAL9000 added the controller-managed label 2026-06-02 03:15:24 +00:00

HAL9001 approved these changes 2026-06-02 03:29:49 +00:00

HAL9001 left a comment

Owner

Copy Link

Copy Source

✅ Approved

Reviewed at commit 11c0fd1.

Confidence: medium.

**✅ Approved** Reviewed at commit `11c0fd1`. Confidence: medium. <!-- controller:fingerprint:b6a7c6ab4cc646aa -->

HAL9000 added the auto/claimed-merge label 2026-06-02 03:34:25 +00:00

HAL9000 commented 2026-06-02 03:34:25 +00:00

Author

Owner

Copy Link

Copy Source

Claimed by merge_drive.py (pid 2496307) until 2026-06-02T05:04:25.113249+00:00.

This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

<!-- merge_drive.py: claim --> Claimed by `merge_drive.py` (pid 2496307) until `2026-06-02T05:04:25.113249+00:00`. This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.

HAL9001 approved these changes 2026-06-02 03:34:29 +00:00

HAL9001 left a comment

Owner

Copy Link

Copy Source

Approved by the controller reviewer stage (workflow 124).

Approved by the controller reviewer stage (workflow 124).

HAL9000 merged commit 6200574444 into master 2026-06-02 03:34:31 +00:00

HAL9000 removed the auto/claimed-merge label 2026-06-02 03:34:31 +00:00

HAL9000 referenced this issue from a commit 2026-06-02 03:34:32 +00:00

Merge pull request 'feat(ci): parallel coverage engine + explicit-gated coverage job; de-razor coverage to 96.62%' (#11258) from coverage-engine-master-port into master

Sign in to join this conversation.

Reviewers

No Reviewers

HAL9001

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.

overdue

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 Label controller-managed

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents

No Assignees

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#11258