Skip to content

Agent Context Patch v0.3.0

Choose a tag to compare

View all tags
@Cherwayway Cherwayway released this 11 Jul 12:09
Immutable release. Only release title and notes can be modified.
v0.3.0
1cf55e9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Agent Context Patch v0.3.0

Release commit: 1cf55e9
Artifact SHA-256: 125eb73556e7cad114b76581629643b615c9c10ed3eed1c71fa426f851fc36ad

Highlights

  • Adds the single public $evolve update flow for explicit stable-Release discovery and upgrade.
  • Adds PowerShell and Bash update dry-run/apply adapters with exact plan approval, managed-tree hashes, complete sibling backups, verification, and automatic rollback.
  • Separates Kit Version from Workspace Schema compatibility, so valid historical Schema 1 workspaces remain usable.
  • Adds the iteration standard, privacy-minimized feedback form, immutable Release policy, and user notification guidance.

Compatibility

  • Kit Version: 0.3.0
  • Workspace Schema: reads and writes Schema 1. No workspace migration is required.
  • The update replaces only the user-level evolve skill. It does not scan or modify workspaces or AGENTS.md / CLAUDE.md.
  • Start a new Agent task after a successful update so the new skill is loaded.

First upgrade from v0.2.0

The v0.2.0 skill predates $evolve update. For this first upgrade, ask the Agent to resolve this immutable Release, verify the tag, commit, attestation, and asset digest, unpack the archive, and run the candidate Release Bootstrap in UpdateDryRun/UpdateApply mode against the installed user-level skill. After that handoff, use $evolve update for later releases.

Verification

  • Exact release commit passed the public npm test gate on Windows and Ubuntu: https://github.com/Cherwayway/agent-context-patch/actions/runs/29151987144
  • The generated archive itself passed npm test: 135 tests, 116 passed, 19 platform skips, 0 failures.
  • The real immutable v0.2.0 asset upgraded successfully to this candidate through both PowerShell and Bash; backups matched v0.2.0 and installed trees matched v0.3.0.

Current limits

There is no daemon, background polling, telemetry, silent upgrade, automatic workspace migration, downgrade, or file-level drift merge. Release notifications remain external through GitHub, and every local replacement requires an explicit reviewed plan.

Assets 4
Loading