Skip to content

Paperclip v0.3.0

Latest

Choose a tag to compare

@robertdevore robertdevore released this 13 Nov 05:27
v0.3.0
fda9eb8

Kujo for Paperclip 0.3.0 adds approved execution assurance and an issue-level Verification Center, tied to Paperclip's native tasks, agents, runs and human approvals.

  • Run opt-in Workcell, Lens, Muzzle and PackWrite workflows and retain logs, screenshots, failures and cancellation outcomes.
  • Import RunLedger receipts and measured Watchdog metadata; compare attempts without promoting imported claims into verified results.
  • Review current-source acceptance, human decisions and explicit waivers.
  • Browse delegated evidence in bounded pages beyond 50 assignments.
  • Preserve all 21 previous tools, add manage-kujo-assurance, and ship 19 pinned component snapshots with verified Workcell and Lens fixes.

Install with npx paperclipai plugin install @kujolang/paperclip, then restart Paperclip. Back up host data before upgrading. New assurance execution is disabled by default and requires macOS or Linux plus feature-specific prerequisites. Workcell admission is local Docker; Lens targets unauthenticated loopback pages. Official Paperclip 2026.1106.0 lacks a plugin run-tab mount, so use the issue Verification Center and scoped evidence tools.

Read the release and upgrade guide, configuration and limits, and reproducible demonstration.

The release workflow verifies the signed annotated tag, repeats unit/build/package and browser checks, publishes with npm provenance, and verifies a clean registry install. Attached assets include the npm archive, SHA-256 checksum, CycloneDX SBOM, component lock and schemas.

Publication recovery: npm processing exceeded the original workflow's five-minute visibility window after accepting the package. The public archive was then independently installed, its npm signatures/attestations verified, and its SHA-256 matched to the original GitHub build attestation (74057fd7672bec3f3a44f05fcd595867c5a0a5af3c13ec84f60f7bee7a903fab). The signed tag was unchanged. The SBOM was reconstructed from the tagged lockfile; the archive is the original CI-published artifact.