Skip to content

chore(release): v1.2.0 — Coverage and Diagnostics - #83

Merged
Joncik91 merged 1 commit into
mainfrom
v1.2.0-release
May 15, 2026
Merged

chore(release): v1.2.0 — Coverage and Diagnostics#83
Joncik91 merged 1 commit into
mainfrom
v1.2.0-release

Conversation

@Joncik91

@Joncik91 Joncik91 commented May 15, 2026

Copy link
Copy Markdown
Owner

v1.2.0 minor release - 13 fixes from Vidence v1.1 dogfooding. Why: v1.1 evaluator surface lacked first-class handling for legitimate spec patterns (Python-stack lifecycle, cross-step input sanitization, narrative-form decisions, post-ship-iteration sentinel), so that specs operators wrote naturally were flagged incorrectly or not at all. Closing piecemeal would have produced 6+ point releases each shifting evaluator behavior; a coordinated minor lets us bump the marketplace version once with a single CHANGELOG entry, to prevent operator churn. Tests: 1842 -> 1923 (+81). All 6 feature PRs (#77 #78 #79 #80 #81 #82) merged. Opus Wave 4 review one BLOCK fixed (#81 glossary). No spec contract changes. Surface bumps: marketplace 1.1.1 -> 1.2.0. EVALUATOR_VERSION + WALKER_VERSION unchanged because the spec contract is stable since v1.0.

13 fixes across 5 classes surfaced by Vidence's v1.1 dogfooding cycle:
- L: sanitized-input field with per-artifact-version taint tracking (#80)
- E: gated Python-stack walker detection (#78)
- H/I/N: --project flag + wizard placeholders + skill doc fix (#79)
- A: calibrated-for exemplar audit (#77)
- O/P/Q: excessive-post-ship-iteration wiring + tier3 run fingerprint + ADR
  extractor extensions (#82)
- B/C/D/M: step-precision + thin-coverage + walker round + self-cycle
  wording (#81)

No spec contract changes — v1.0/v1.1/v1.1.1 locked specs remain valid.

Tests: 1842 → 1923 (+81). Five new finding kinds / status codes, all
documented in docs/glossary.md.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@Joncik91
Joncik91 merged commit d0b7165 into main May 15, 2026
2 checks passed
@Joncik91
Joncik91 deleted the v1.2.0-release branch May 15, 2026 19:39
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