Pageprint · Changelog

Release history.

Pageprint 0.1.21 is available from the Chrome Web Store. Its exact package passed automated release proof and owner smoke testing on macOS before publication on September 7, 2026.

0.1.21
September 7, 2026

A quieter success signal

  • Every successful full capture now shows a simple checkmark in the toolbar instead of turning the remaining allowance into a badge.
  • The bottom-right completion notice remains the clear place to see how many included captures remain.
  • The exact package passed automated Chrome proof and an owner smoke test on macOS before Chrome Web Store publication.
  • Capture, cancellation, failure, quota, price, and licensing behavior are unchanged from 0.1.20.
0.1.20
September 7, 2026

One capture means one transaction

  • The active-capture lock now exists before asynchronous license or capture work begins.
  • Rapid second clicks cancel visibly instead of allowing overlapping capture transactions.
  • Cross-tab busy feedback, toolbar state, and completion notices recover cleanly after cancellation or navigation.
  • The capture traversal, stitching, output limits, quota, price, and licensing paths remain unchanged.
0.1.19
September 6, 2026

Clearer boundaries and status

  • Protected browser surfaces now answer an explicit click with a brief unavailable signal without injecting into the page or consuming a capture.
  • The local status page pairs usage with activation or restore and keeps implementation details secondary.
  • This candidate was superseded before submission after operator testing exposed a rapid-invocation control race.
0.1.18
September 6, 2026

Completion without getting in the way

  • The post-capture notice moved to the bottom-right so it no longer competes with Chrome's download UI.
  • The notice remains readable longer, pauses while engaged, and clears when another capture begins.
  • This candidate was exercised through its included allowance and superseded before submission.
0.1.17
September 6, 2026

Know what happened

  • A successful capture now leaves a brief page notice with the remaining included captures and an optional early activation path.
  • The local status surface focuses on completed captures and describes a licensed browser as active rather than presenting activation as a separate feature.
  • This candidate was superseded before submission after its original notice placement proved distracting.
0.1.16
August 20, 2026

Commerce, end to end

  • The release package now contains the audited public Lemon Squeezy checkout, product, and variant identifiers without seller credentials.
  • A real Test-mode order proved license issuance, activation, restart-safe local entitlement, validation, deactivation, and signed webhook delivery.
  • The $4.99 one-time unlock is non-expiring, permits five installations, and has no subscription.
  • The capture engine remains byte-identical to the holdout-passing 0.1.13 candidate.
0.1.15
August 15, 2026

Submission hardening

  • License requests now follow Lemon Squeezy’s documented JSON-response contract while retaining form-encoded license operations.
  • Release evidence explicitly proves failed, cancelled, and best-attempt captures preserve the free count.
  • Chrome reviewer access, final privacy comparison, and submission checks are defined without placing reviewer credentials in public artifacts.
  • The capture engine remains byte-identical to the holdout-passing 0.1.13 candidate.
0.1.14
August 14, 2026

The commercial boundary

  • The first 25 successful captures are free; capture 26 opens the unlimited-unlock path.
  • A provider-neutral entitlement layer and Lemon Squeezy license adapter preserve local capture after purchase.
  • Checkout, activation, restore, validation, deactivation, and offline cached access are implemented and tested against a provider mock.
  • Public product identifiers and a live transaction proof still block paid publication.
0.1.13
August 14, 2026

Oversized pages without oversized memory

  • A bounded streaming PNG path captures very tall ordinary pages without building one enormous in-memory canvas.
  • The frozen candidate passed a fresh 20-page ordinary-web holdout at 90% A+B and 80% A.
  • The capture engine is frozen for the Version 0.1 product boundary.
0.1.12
August 13, 2026

A tested ordinary-web engine

  • Observed viewport positions and document extent replaced brittle fixed-height capture plans.
  • Interaction isolation, honest cancellation, sticky suppression, dynamic-page handling, and state restoration were hardened.
  • The development corpus reached 36 of 36 useful ordinary-page results.
  • The first frozen holdout exposed a single-image size ceiling and remained preserved as a failed 80% result.
0.1.0
August 12, 2026

One click. The whole page.

  • Initial Manifest V3 proof captured an ordinary scrolling webpage as one local PNG.
  • No screenshot upload, capture cloud, account, analytics, telemetry, editor, annotation, or sharing.
  • Failed and cancelled attempts did not consume quota.