Skip to content

v0.1.0-rc.3 — Cosplay signature-prop fidelity repair

Pre-release
Pre-release

Choose a tag to compare

@windforce19820520-ai windforce19820520-ai released this 17 Aug 15:11
f424705

This release candidate repairs the Cosplay signature-prop fidelity path reported in issue #19 while keeping the change inside the existing declarative and deterministic boundaries.

Highlights:

  • Expanded the data-only Cosplay ScenarioPack with explicit signature-prop ontology paths, source-isolation policies, required detail dependencies, prompt coverage, and separate semantic-review criteria.
  • Required signature-prop references now fail closed when the effective reference budget cannot retain them; optional pose references remain omittable with a reason.
  • Unadjudicated semantic fail or uncertain findings remain needs_review, and human decisions are bound to the exact execution run.
  • Generated CaseSpec roots bind to the exact loaded ScenarioPack version.
  • Added deterministic regression coverage and an RC.3 compatibility snapshot.

Validation:

  • The annotated release tag resolves to reviewed source revision f424705bbf554e23336e8b4179f24b287145cdf6.
  • Post-merge release-candidate, offline clean-room, and checksum gates passed.
  • All four @voce-engine/* packages were published at 0.1.0-rc.3 under npm next with signatures and provenance.
  • A clean public-registry consumer passed package, CLI, and all three bundled ScenarioPack offline paths.
  • One separately authorized Seedream Cosplay call returned HTTP 200 and passed identity, costume, visible signature-weapon, and intended half-body presentation review.
  • Issue #19 was closed as completed.

Publication note:

  • The package checkout and gates used the exact RC.3 tag. Because the workflow was dispatched from main, npm provenance records the workflow invocation revision main@1e8baf8dc4049a34e9d14d621cc9d864047cf0db; existing immutable versions were not republished.
  • The publish workflow now requires its selected workflow ref to match the release tag and tolerates bounded registry propagation delay for future releases.

This remains a prerelease candidate and is not production-ready. Full acceptance details are in docs/acceptance/v0.1.0-rc.3.md on main.