Skip to content

v0.4.14

Choose a tag to compare

View all tags
@ivory-code ivory-code released this 20 Aug 09:57
· 17 commits to main since this release
v0.4.14
20adf8f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

QAMap 0.4.14 strengthens the path from a pull request diff to the evidence a reviewer or coding agent should trust before optional E2E work.

Added

  • Detects delivery-integrity risks such as referenced assets that are missing from the committed change and validation commands that can rewrite shared history.
  • Traces supported runtime activation changes across guards, configuration sources, side effects, and restart, reload, or deployment boundaries.
  • Separates stable repository QA facts from the current pull request delta through the versioned qamap.context contract.
  • Adds a deterministic, provider-neutral benchmark for context identity, reuse, invalidation reasons, and compact payload size.

Changed

  • Keeps independent behavior-bearing commits separate when broad package vocabulary is their only connection.
  • Treats removed UI as an absence contract rather than an executable entry point.
  • Keeps formatting-only UI changes contextual while preserving real React and Vue state transitions.
  • Aligns the npm package, CLI, native plugin manifests, portable skill, changelog, and submission metadata on 0.4.14.

Validation

  • 382/382 tests passing
  • 0 scanner findings
  • 33/33 static recommendation contracts passing
  • 10/10 context identity and reuse checks passing
  • 3/3 execution contracts passing with all seeded regressions caught
  • Coverage: 90.30% lines, 87.06% branches, 95.80% functions
  • Published package smoke verified from @ivorycanvas/qamap@0.4.14
  • 195 files in the npm package

GitHub Actions users can pin this release with uses: IvoryCanvas/QAMap@v0.4.14.

QAMap still treats static scenarios and generated drafts as not-run until an explicit validation action is executed. The OpenAI Plugin Directory update remains a separate review and publication step.

Assets 2
Loading