Releases: joshduffy/readback
Release list
Readback v0.1.5
Readback now requires commit identity and live evidence before verifying a Cloudflare deployment. It applies host restrictions to every redirect, rejects credential-bearing URLs, masks recognized credentials in evidence, and reports truncated file or HTTP checks as indeterminate when unread content could contain the match. Successful GitHub Check Runs no longer remain pending because legacy statuses are empty. Output failures cannot report success.
Results include the checked condition alongside evidence. Terminal output shows concise evidence, discovery distinguishes beta and planned commands, and schema verify names the input and result schemas. The website and README explain the tool in plain English and include an actual JSON result.
Compatibility: exit codes and claim status names are unchanged. Results gain claim, the reason set gains response_truncated, and discovery JSON now uses compact summaries and named schemas. Health-only deployment checks need no Cloudflare API token; an explicitly requested Worker version check still does.
Validation includes Go checks, adversarial fixtures, before/after binary reproductions, desktop/mobile website checks, and independent Kimi K3 and GLM 5.3 correctness and code-Heaton reviews. Readback remains early software: choose required assertions and inspect the evidence before approving a release.
v0.1.4
v0.1.3
Changelog
- d654c91 docs: public plan, spec, and contributor guide
- 08003e1 chore: remove internal process documents and private references from the public tree
- 024e843 chore: scrub audit transcripts and fixture metadata; record Codex round 3 (#24)
- bd50ed4 docs: v0.1.2 and exposure round 2 (#23)
- 2cbdea6 fix(release): build with -trimpath and a reproducible mod timestamp (#22)
- 6a0a08d docs: exposure audit outcome (#21)
- 658ab50 docs: Kimi K3 exposure audit transcript (#20)
- 3bfd081 chore: scrub identifiers and local paths from the public tree (#19)
- 333f3bb docs: public flip and install verification (#18)
- 569e20b docs: v0.1.1 ledger entry (#17)
- a1eaf2b fix(verify): close completeness gaps found by the v0.1 critic (#16)
- 31e5378 docs: v0.1 release run log (#15)
- 2036cd7 chore(release): publish formula under Formula/ in the tap (#14)
- 2b07743 chore: AGENTS.md is the real file, CLAUDE.md the symlink (#13)
- 90f01ea feat: v0.1 ship surface (T11) (#12)
- 6712992 docs: release prerequisites recorded
- 2f32dbb feat(web): readbackcli.dev install worker
- 70a2d97 docs: ledger: T8 merged, T11 dispatched
- cfb20e1 feat(providers): cloudflare-workers deployment checker (T8) (#9)
- b2b4acf docs: annotation sha rule is full 40-hex only
- 3e46fff docs: T8 reproduction
- bf197f9 docs: ledger: T10 r2 merged, T8 live verified
- abd1612 fix(doctor): portable process bounding, stderr-only auth detail, honest env failures (#11)
- 555b5df docs: ledger through T9 merge; exit-code gating rule
- 2169d8e fix(verify-deploy): test imports (#10)
- bca9d6a feat(verify-deploy): single-claim deployment check (T9) (#8)
- 4972ec7 docs: T10 reproduction
- ecb003e docs: T10 round 2 prompt
- 27d5eef docs: T5 reproduction and T11 ship prompt
- a47188e docs: ledger through T7; T9 prompt uses the registry seam
- 6611954 feat(providers): github checker via gh api (T5) (#7)
- 79b3c94 docs: T8 cloudflare prompt
- 7a56ffd docs: T7 Workers versions probe recorded; cloudflare rung specified from live data
- bafc82c feat(providers): http and local checkers (T6) (#6)
- fd80b9d feat(doctor): environment and auth report (T10) (#5)
- 41da728 docs: T6 reproduction
- 0b3bccb docs: T6 round 1 fix prompt
- 78cde28 docs: T5 round 1 wiring prompt
- ba08acf chore: tighten project permissions (no gh api allow, no bypassable deny)
- c5fce09 docs: full CLAUDE.md, AGENTS.md symlink, project settings
- 3daa11e docs: T10 round 1 fix prompt
- 808a53d docs: prompts for T5 and T9
- 220ffa7 feat(verify): result model, runner, and verify command (T4) (#4)
- d0213bb docs: T4 reproduction, T4 sent back, T10 in review
- d131e4e docs: T4 round 1 fix prompt
- 8d5f32a docs: GLM review lane command after the three wrapper fixes
- 2190ba8 docs: T2 and T3 merged, T4 and T10 dispatched, GLM posture fix
- ab7dba3 feat(verify): operator assertions file and matching (T3) (#3)
- 54c28c1 docs: T3 reproduction and round 1 prompt
- 2807927 feat(verify): extract claims blocks from markdown (T2) (#2)
- 128e155 docs: T2 reproduction, T4 prompt amended, GLM fix recorded
- 3e26759 docs: T2 round 1 fix prompt
- e72f3a8 docs: T1 merged, T2 and T3 dispatched, GLM review failed
- e27a3ec feat(verify): claims schema, types, and validation (T1) (#1)
- edc7d49 docs: T1 round 1 fix prompt
- 64cae41 docs: T1 review reproduction
- 9a1de67 docs: prompts for T6 and T10
- a291d65 docs: prompts for T2, T3, T4
- 30d9ea0 docs: T1 in review
- 8bff16f docs: record orchestrator-swap consequence
- 4099bff docs: dispatch protocol with health check and stall monitor
- e8778d4 docs: record T1 launch fixes in the ledger
- b70febe docs: v0.1 orchestration ledger and T1 prompt
- 432ad9e docs: v0.1 implementation plan for verify, verify-deploy, doctor
- 4cd78af docs: record readbackcli.dev registration
- 6ad8a64 docs: confirm product name and domain candidates
- 91c9d07 docs: record provider lanes and data-sharing posture
- 2c7ffd8 docs: record typed-claims and v0.1 scope decision
- 0869d45 fix: schema titles for doctor and verify-deploy
- 0e1e73b feat: scaffold readback CLI with typed-claims plan and cross-model critiques