[babo-jeonguk]

Auto Compact for Claude v1.0.2 → v1.1.0, proposed for artifact review. Submitted by @babo-jeonguk.

Summary

- artifact.commit / repository.commit: 6dfdb98eb22617d2d94b7f5aefe9a421c7766d1a
- artifact.tag: v1.0.2
+ artifact.commit / repository.commit: a599a13208f401ea38ede8104149cd1ac05daaec
+ artifact.tag: v1.1.0

Release: https://github.com/babo-jeonguk/paseo-auto-compact-for-claude/releases/tag/v1.1.0

• Compact now is a durable operation. It is persisted before the RPC replies, and a worker owns dispatch, evidence and recovery. A lost reply, a plugin reload or a daemon restart no longer loses the request or sends /compact twice. Once a dispatch marker is saved, nothing is resent.
• Paseo 0.14 support. Paseo 0.14 reopens a stale plugin session before its next prompt. Until an ordinary message has done so, the plugin compacts nothing in that session, so its observer always belongs to the running plugin instance.
• Keeps the declared >=0.12.0 requirement and the 0.12 SDK compile-time contract.
• Keeps the manifest permissions, media, settings schema and UI compatibility imports unchanged.
• The stored state stays at version 1 with additive fields, so a rollback to v1.0.2 keeps working.

Submitted and published dates, categories and submitter remain unchanged. reviewedAt is left for the reviewer.

Evidence

• Before: a reload during compaction became unknown although it finished. A lost reply showed failure and made a retry look busy. On Paseo 0.14, Compact now right after a plugin reload compacted in a new observer launch, and the operation stayed unresolved.
  After: native scenarios recover an in-flight operation after reload with one model request, and return the existing operation for a retried ID. On 0.14, Compact now after a reload is refused with the reason and sends nothing. After an ordinary message, it compacts once.
• Release CI (on the tagged commit): https://github.com/babo-jeonguk/paseo-auto-compact-for-claude/actions/runs/41062167519. SDK 0.12/0.13/0.14 checks pass on Linux, macOS and Windows. Native simulation with Claude Code 2.1.306 passes all 18 scenarios on Linux and Windows for Paseo 0.12, 0.13 and 0.14.
• Install/upgrade/rollback E2E (tests/e2e): installs v1.0.2 from GitHub, updates, runs the native scenarios on that install, rolls back and forward. It passes 24/24 on Linux and Windows for Paseo 0.12, 0.13 and 0.14.
• Desktop app E2E passes 9/9 on Linux and Windows for 0.12, 0.13 and 0.14. Android app E2E passes 8/8 for 0.12, 0.13 and 0.14. On the tagged commit itself, the native matrix for 0.12/0.13/0.14 (npm run test:release) passed 18/18 each, and the Paseo 0.14 install/upgrade/rollback E2E (Linux and Windows), desktop E2E (Linux) and Android E2E passed.
• Cache retention, billing savings and summary quality are not measured. macOS native execution and the iOS app remain unverified.

Merge Danger

Door: two-way

The registry record can be reverted to v1.0.2. The state file keeps version 1 and v1.0.2 reads it after a rollback.

Blast Radius: listing

One existing record changes. Merging approves the exact v1.1.0 tag and commit after reviewer inspection. On Paseo 0.14, updating the plugin means a countdown pending in an open conversation does not run; the next reply schedules a new one.

🤖 Generated with Claude Code

[paseo-bot]

Auto Compact for Claude v1.1.0 is approved and merged, @babo-jeonguk. I updated the registry review date and retained your overview, description and interface images. Publication is queued; no action is needed from you.

Review data

• Policy: main REVIEW.md blob 3c5e763c9565b93ea33fa48c9aeb83e415c72d67. Reviewed registry head: e41fc580f5ffbc237e52a0e39cf567d464980dd4. Attribution agrees with the existing record and accepted submission #998.

• Git artifact: https://github.com/babo-jeonguk/paseo-auto-compact-for-claude.git, root plugin, tag v1.1.0 resolving to a599a13208f401ea38ede8104149cd1ac05daaec. Independently fetched both the current pin 6dfdb98eb22617d2d94b7f5aefe9a421c7766d1a and proposed pin without hooks or submodules, checked archive paths/types before confined extraction, and compared their trees. Git archive SHA-256: old 6c3b42ff31fb77d69f588da06a78e865812391dc9e5e470fe400c1ab1dc74394, new aad036917558050c220e89fd40026b9fa32d3fd84b7a72d83a5c2d1fbdb6f2b4.

• Inspected changed server entry, scheduler, durable worker, gateway, state migration/storage, observer and receipt retention, deadlines/error reporting, RPC schemas, client request correlation/presentation, overview and package metadata, with affected cache/activity/provider paths. Required entry files and local imports resolve. Generated observer source exactly matches the shipped source and declared SHA-256 ece7bf8ce5445aedb974f30472983b78c7358b8feea99d15c1ef2369d88a26e4.

• No manifest build/preparation command or installed production dependency tree. Runtime imports use included modules, Node built-ins and host libraries. The 345 development-lock entries have exact npm registry sources and integrity; esbuild/fsevents lifecycle markers are development-only. The packing script generates the local observer then runs development checks. No plugin or dependency was installed, built, imported or executed during review.

• Manual requests are persisted before acknowledgement (server/scheduler.ts); the worker checkpoints dispatch before the fixed /compact send (server/gateway.ts). Recovery observes matching native receipts and the command's completed timeline boundary without resending a marked operation. Session, activity, idle/permission, policy, cache and deadline checks guard dispatch. Paseo 0.14 stale-launch detection refuses compaction until an ordinary message resumes the session. The overview explains this update behavior.

• Purposeful access remains local state/observer files, bounded Claude transcript reads for cache metadata, cache-related settings/environment, and a locally shipped Mod added to interactive Claude launches. New completed-operation receipts are retained seven days, with cleanup constrained to plugin-owned receipt paths; current-activity attempt guards survive history cleanup. No new external destination, credential extraction, shell/eval, runtime software acquisition or unrelated destructive action found in the inspected changes. Claude still sends conversation content to its configured provider. The existing race between the final idle check and public dispatch is not eliminated.

• Registry edit: reviewedAt only, preserving the proposed pin, categories, attribution and original dates. Author overview/description take precedence; no fallback copies needed. Viewed both declared PNGs showing conversation controls/settings.

• Trusted unchanged-main online validation passed: 435 well-formed records, one changed artifact matched. Final-head registry CI passed. Author release CI passed on the exact pinned commit, including SDK checks across Linux/macOS/Windows and native simulations on Linux/Windows for Paseo 0.12/0.13/0.14.

• Limits: static artifact inspection, no independent live plugin/provider/UI execution or exhaustive dependency audit. Author E2E claims are supporting material, not independently reproduced here. Cache retention, billing savings and summary quality remain unmeasured; native macOS and iOS remain unverified. No remaining author requirement or factory-policy incompatibility identified.

• Merged as fde8afc2cb7fd51a0e06778e8f3396ee358fddcd. The Publish run is queued for deployment; the origin and public registry checks still return the previous v1.0.2 pin. Publication of v1.1.0 is not yet confirmed.