Skip to content

v3.1.1 — orchestrator boundary verification, mandatory skip notes

Choose a tag to compare

View all tags
@jeffrigby jeffrigby released this 17 Sep 03:41
· 6 commits to main since this release
v3.1.1
f7dcdcc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Backfilled release for the v3.1.1 tag.

v3.1.1 — /deep-audit orchestrator boundary hardening

Follow-up to the PR #8 review of the orchestrator refactor shipped in v3.1.0.

Fixed

  • codebase-health 2.1.1: The orchestrator now verifies each specialist's return value against the expected ## <Name> Findings heading and severity sections (### Critical / ### High / ### Medium) before pasting it into the report. Empty, missing-heading, or malformed results are recorded under a new Specialists that failed: line in Notes instead of being silently dropped — a launched specialist is never omitted from the final report.
  • The dead-code skip note is now mandatory: when dead is requested (or selected via all) but no dependency manifest exists, Notes must include an explicit Dead code: skipped — no manifest line, regardless of whether other specialists ran.
  • Added a ### Notes section to the library-modernizer and code-quality-reviewer output templates so per-specialist skip-notes (Context7 unavailable, no CLAUDE.md to read conventions from) survive aggregation — closing a parity gap with security-auditor and performance-analyzer.

Full diff: v3.1.0...v3.1.1

Assets 2
Loading