QAMap 0.4.16 tightens deterministic QA evidence boundaries, release validation, and public packaging.
Added
- Added a complete public brand asset inventory with editable masters, app and web icons, social cards, and dedicated light and dark plugin artwork.
- Added exact diff evidence and measurable QA contracts for changed rendering work, image request priority, deferred modules, initial HTML and hydration, font loading, and delivery cache policy.
- Added bounded OpenAPI and Swagger response-example parsing as the authoritative source for generated local JSON response scaffolds.
Changed
- Release-focused changes prefer a repository-declared non-publishing validation gate and avoid repeating commands already covered by that gate.
- Network evidence can route affected behavior and QA, but repository types, schemas, UI copy, and fixture keys no longer authorize invented response values.
- Refreshed the README, skill, plugin, GitHub preview, and reusable brand assets around one production-ready visual identity.
Fixed
- Performance-focused changes no longer stop at a generic screen flow when the changed hunk supports a measurable runtime or delivery contract.
- Changed endpoint implementations are observed instead of intercepted, while schemas or status codes without concrete response examples remain explicit evidence gaps.
- Publishing, tagging, pushing, and deployment scripts are never promoted as automatic release validation.
- Working-tree-only release changes no longer inherit test contracts from an earlier target-branch commit outside the active comparison.
Validation
- 429/429 tests passed
- 37/37 static recommendation contracts passed
- 10/10 context checks passed
- 3/3 execution contracts passed and caught all three seeded regressions
- Agent benchmark dry-run contract passed without an external provider call
- Scan completed with zero findings
- Coverage thresholds passed; two consecutive runs measured 90.69-90.73% lines, 87.13-87.21% branches, and 95.97% functions
- Plugin isolated-install smoke and 207-file package preview passed
The GitHub Action can be pinned to IvoryCanvas/QAMap@v0.4.16. Generated scenarios and drafts remain not-run until an explicit execution action produces a receipt.