Skip to content

feat(coverage): add calibrated ascent automation#1405

Open
neuron7xLab wants to merge 11 commits into
mainfrom
coverage_calibration_automation
Open

feat(coverage): add calibrated ascent automation#1405
neuron7xLab wants to merge 11 commits into
mainfrom
coverage_calibration_automation

Conversation

@neuron7xLab

@neuron7xLab neuron7xLab commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Summary

Adds a deterministic calibration automation layer for the TD-023 coverage-ascent campaign.

This PR does not measure coverage and does not claim a new coverage percentage. It consumes the existing machine-written coverage_summary.json from tools.coverage.geosync_coverage_intelligence and converts that evidence into a ranked 90 → 92 → 95 → 97 work plan.

What this adds

  • tools/coverage/calibrate_coverage_ascent.py
  • tests/tools/test_coverage_calibration.py
  • .claude/commit_acceptors/coverage-calibration-automation.yaml

Quality discipline

  • No production thresholds changed.
  • No coverage omit rules changed.
  • No production code path changed.
  • No synthetic global coverage percentage is invented.

Measurement command

PYTHONPATH=. python -m pytest tests/tools/test_coverage_calibration.py -q

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: be117381a7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +261 to +262
_write_json(plan, out_dir)
_write_markdown(plan, out_dir)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Gate invalid evidence before emitting plans

When a valid summary has evidence_valid: false and the CLI is run with the default --enforce-evidence behavior, these writes still create both JSON and Markdown plans before the later EXIT_EVIDENCE_INVALID return. That leaves machine-readable work plans derived from evidence the tool claims to refuse, and any wrapper or rerun that consumes existing outputs can advance from invalid coverage evidence; perform the enforcement check before writing, reserving artifact emission for --no-enforce-evidence.

Useful? React with 👍 / 👎.

@neuron7xLab neuron7xLab force-pushed the coverage_calibration_automation branch from 0468df9 to a755b46 Compare July 2, 2026 04:25
@neuron7xLab neuron7xLab enabled auto-merge (squash) July 2, 2026 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant