Skip to content

Feat/code quality capability metrics - #30

Merged
contactacefleetdev merged 8 commits into
mainfrom
feat/code-quality-capability-metrics
Aug 28, 2026
Merged

Feat/code quality capability metrics#30
contactacefleetdev merged 8 commits into
mainfrom
feat/code-quality-capability-metrics

Conversation

@contactacefleetdev

@contactacefleetdev contactacefleetdev commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Description

Summarize the changes made in this Pull Request and the problem being solved.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Verification

Describe the tests and checks performed to verify changes:

  • pytest passes cleanly.
  • python -m build and twine check dist/* pass.
  • E2E test script scripts/e2e_test.py passes.

Checklist

  • My code follows the code style of this project.
  • I have updated documentation where necessary.
  • I have updated CHANGELOG.md with my changes.

@contactacefleetdev
contactacefleetdev merged commit c926277 into main Aug 28, 2026
1 check passed
@contactacefleetdev
contactacefleetdev deleted the feat/code-quality-capability-metrics branch August 28, 2026 07:19
contactacefleetdev pushed a commit that referenced this pull request Aug 28, 2026
One conflict, in dashboard_render.py: both sides added functions at the same
point and both carried a _fleet definition.

Resolved by keeping both feature sets. main's _fleet is byte-identical to the
merge base -- it was never edited there -- so it is superseded by this
branch's, which takes the reference map. main's _quality is kept in full and
ordered ahead of it, because _fleet's signature has to stay adjacent to a body
that lives outside the conflict region.

Verified after resolving: the mode toggle, reference badges and per-metric
counterfactual render alongside main's quality section, and the suite is green
at 114 including main's nine new quality tests.

Note: PR #30 carried an older duplicate of this branch's lever work, swept in
by a parallel session. d2618af removed it before merge, so main has no levers
and there was no conflict over them. It also means main still carries the
silent-telemetry bug this branch fixes -- usage_to_request_log raising on
every turn into the except that protects the response.
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