Skip to content

LoopSkill v3.3.3

Choose a tag to compare

View all tags
@amanayayatu-tech amanayayatu-tech released this 19 Jul 06:51
· 141 commits to main since this release
v3.3.3
4a46ae9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

LoopSkill v3.3.3

This patch release adds schema-v3 Decision Gateway operations for registering a bounded user decision and recording the user's explicit response. Decision responses are normalized and hashed at the MCP boundary, bound to the current Controller turn and exact goal/dispatch/artifact/surface context, and fail closed on stale or mismatched identity. Explicit loopback preview URLs may differ only by port when scheme, host, and path remain identical.

It also makes canonical coverage runs remove stale generated coverage artifacts before measurement, preventing local result inflation.

Release evidence

  • Protected-main exact SHA and annotated tag target: 4a46ae95120dad44a1b2e10f42da4293fbaf4c08
  • Same-SHA macOS install receipt: LoopSkill 3.3.3, zero source/install drift, MCP configuration readback successful
  • Frozen local gate: 657 tests PASS; branch coverage 80.324457%; generator fuzz 5,000 PASS; state fuzz 5,000 PASS; Skill/SPEC/schema/installer/risk/secret checks PASS
  • Independent Reviewer: P0/P1/P2 = 0/0/0
  • Compatibility CI on the exact candidate tree: 632 canonical tests PASS; branch coverage 80.091827%; both 5,000-case fuzz lanes PASS; Linux/macOS install and Final gate PASS
  • Real authorized Life Blueprint path on the exact installed build: bounded visual decision REGISTERED and APPLIED, FINAL_AUDIT PASS, heartbeat PAUSED with readback, and canonical FINALIZATION_ACKED / LOOP_COMPLETE

Evidence boundary

Disposable decision fixtures A and B remain individually recorded as FAIL because of harness input errors (Controller attestation mismatch and logical-time regression). Both were rejected with zero canonical side effects. They are preserved as fail-closed negative evidence and are not described as passing canaries. The required positive capability evidence comes from the authorized exact-main Life Blueprint execution above.

The Life Blueprint product remained local-only: no product commit, push, pull request, merge, deployment, or external write was performed.

Assets 2
Loading