Agent Context Patch v0.4.0
Agent Context Patch v0.4.0
Release commit: 539208c
Artifact SHA-256: eb630c19ace1528e7f7c958ea6c6a0a812751f641e980937034a2cfb4debd48c
Highlights
- New workspaces now default to
context_write_policy: auto. - Codex and Claude invoke
$evolve after-failureautonomously and apply eligible low-risk context additions in the same turn. - Routine success returns one compact, non-blocking receipt;
$evolve approveis reserved for safety exceptions. - Proposal, PatchPlan, Decision, and Apply Attempt remain the audit source even when no approval turn is needed.
Compatibility and safety
- Kit Version: 0.4.0.
- Workspace Schema: reads and writes Schema 1. No migration is required.
- Auto remains limited to verified, privacy-safe, conflict-free low-risk workspace additions targeting Active Context.
- Config or domain activation, cleanup or removal, migration, instruction files, user-global promotion, and Kit updates still require exact approval. Privacy hard failures cannot be overridden.
- Missing Node.js or Commit Kernel support degrades to propose.
- Transaction failures roll back automatically. This release does not claim later user-triggered undo after a successful application.
Upgrade from v0.3.1
Run $evolve update, review the exact UpdatePlan and plan hash, then approve the replacement. The update replaces only the user-level evolve Skill and preserves a complete v0.3.1 recovery copy. It does not scan or edit workspace context, AGENTS.md, or CLAUDE.md.
Existing workspace policy remains unchanged: an existing propose workspace stays propose. To opt an existing workspace into the new behavior, explicitly change its config and refresh the adapter guidance separately. Start a new Agent task after a successful update.
Verification
- The exact release commit passed
npm teston Windows and Ubuntu in GitHub Actions. - The exact release archive passed
npm teston Windows: 146 tests, 126 passed, 20 platform skips, 0 failures. - The real immutable v0.3.1 asset upgraded to this exact archive through UpdateDryRun and UpdateApply; the installed Skill reported 0.4.0, retained the v0.3.1 backup, required a new Agent task, and a second dry-run returned NoUpdate.
- Fresh-Agent acceptance verified both recurring-failure auto application and one-off no-context-write paths.
Current limits
There is no daemon, telemetry, silent Kit upgrade, automatic workspace migration, bulk adapter or config rewrite, or durable post-success undo.