Skip to content

release: v1.7.0 - #23

Merged
denfry merged 2 commits into
mainfrom
feat/find-trace-predict
Jul 29, 2026
Merged

release: v1.7.0#23
denfry merged 2 commits into
mainfrom
feat/find-trace-predict

Conversation

@denfry

@denfry denfry commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Problem

Agents need evidence-first codebase context and a way to predict the blast radius of current changes.

Solution

  • add diff-impact to the CLI and MCP server
  • refactor the skill into the compact Find / Trace / Predict protocol with progressive references
  • refresh the README, documentation, and reproducible brand assets
  • pin privileged release actions to commit SHAs and default workflow permissions to read-only
  • synchronize package, plugin, skill, installer, and documentation metadata for 1.7.0

Verification

  • pytest: 386 passed, 54 skipped, coverage 80.91%
  • pytest --runslow: 387 passed, 53 skipped, coverage 80.93%
  • ruff check src tests scripts
  • mypy src
  • doctor --strict
  • public benchmark: Recall@3 = 1.0
  • release_smoke.py
  • twine check dist/*
  • installer smoke: 11 passed, 0 failed

Compatibility and migration

No breaking migration is required. Existing commands remain available; diff-impact is additive.

Ship the evidence-first Find, Trace, Predict experience.

- add diff-aware impact analysis across CLI and MCP
- split the agent skill into a compact protocol and progressive references
- refresh product docs and reproducible brand assets
- pin privileged release actions to immutable commits
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Make the pre-0.16 rule profile explicit so dependency updates cannot
silently redefine the release gate. Pin CI actions and default workflow
permissions to read-only to reduce supply-chain risk.
@denfry
denfry merged commit bff0a5a into main Jul 29, 2026
10 checks passed
@denfry
denfry deleted the feat/find-trace-predict branch July 29, 2026 07:59
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