Agent Context Patch v0.5.5

Changelog

All notable changes to Agent Context Patch are recorded here. The project uses
semantic versions for the Kit independently from the Workspace Schema version.

[Unreleased]

[0.5.5] - 2026-08-12

Added

• A Schema-1-compatible acp-rule lineage convention for new or
  human-reviewed Active Context rules, with source-proposal and subsumption
  identity.
• Bounded Agent-owned effectiveness states for material use, loaded-only
  evidence, relevant misses, non-applicability, and unknown coverage.
• Fresh-Agent semantic-review and paired rule-impact acceptance, including an
  unrelated negative case and canonical input-digest binding.

Changed

• $evolve weekly and $evolve review-context now use explicitly available,
  content-safe task evidence to schedule retention, routing, rewrite, or cleanup
  review without telemetry, a raw usage ledger, or automatic deletion.
• Prepared the next Kit patch without changing Workspace Schema 1, adding a
  public command, or moving project meaning into the deterministic runtime.

[0.5.4] - 2026-07-29

Added

• A Claude Code marketplace adapter that discovers the immutable-Release
  installer without silently editing a workspace.
• A seven-day discoverability experiment with channel-specific landing paths,
  privacy-minimized evidence records, daily GitHub snapshots, and a real
  fail-to-pass terminal demo asset.
• A focused comparison with Claude Code Auto Memory in English and Chinese.
• A deterministic release-preparation command that binds the named archive and
  SHA-256 checksum to one exact commit.

Changed

• Prepared Kit Version 0.5.4 without changing Workspace Schema 1 or the runtime
  write-authority boundary.
• Made package.json the source of truth for synchronized public Kit Version
  surfaces.

[0.5.3] - 2026-07-26

Added

• An Agent-owned behavior-shape review contract that compares responsibility,
  trigger, execution path, intended effect, and observable verification across
  different implementation nouns.
• A reusable cross-domain review fixture plus positive and negative
  fresh-context acceptance: one repeated execution-path family consolidates,
  while superficially similar accessibility, privacy, idempotency, and timing
  failures remain separate.

Changed

• $evolve after-failure reads only related applied-proposal summaries when
  Active Context suggests a recurring responsibility or failure shape.
• $evolve review-context now uses summary-first shortlisting before deep
  proposal reads and requires subsumption evidence, preserved domain details,
  counterexamples, behavior loss, and net active-context change.
• $evolve weekly may surface semantic-generalization candidates but cannot
  merge them. Semantic replacement remains approval-required, with no new
  runtime heuristic, public command, background scan, or Workspace Schema
  change.

[0.5.2] - 2026-07-26

Fixed

• Lifecycle reconciliation now performs bounded post-application passes so one
  call cannot report settled when its own exact application has already made
  an earlier sibling proposal stale.
• Coordinator results are independent of proposal filename order while
  unrelated approval-waiting proposals remain non-blocking.

Agent Context Patch v0.5.4

What changed

• Adds a Claude Code marketplace adapter that resolves the existing immutable-Release installer without silently editing workspace instructions.
• Adds a real fail-to-pass terminal demo, a focused comparison with Claude Code Auto Memory in English and Chinese, and a privacy-minimized seven-day discoverability experiment.
• Synchronizes public Kit Version surfaces from package.json and adds a commit-bound release archive/checksum preparation command.

Compatibility and boundaries

• Kit Version: 0.5.4.
• Exact source revision: 16fa2231db81f8f183575a39cca35a629476e600.
• Supported Workspace Schema: read/write 1 through 1; no migration is required.
• No new runtime command, background process, telemetry, hosted service, automatic global-instruction edit, or change to runtime write authority.
• Marketplace submission and the seven-day external distribution clock remain separate maintainer actions; publishing this Release does not start the experiment.

Integrity and verification

• Archive: agent-context-patch-v0.5.4.zip.
• SHA-256: 65d8ae3b4030bc1eea4adf56db0518d203fdf960f2e06e2bb75f23c8dfc160c0 (also attached as .sha256).
• GitHub Actions run 30469708714 passed on Windows and Ubuntu for the exact release commit.
• The extracted release archive passed the repository's complete npm test gate.
• A real v0.5.3 release asset was upgraded to this candidate through exact dry-run approval; the installed tree matched v0.5.4, the workspace stayed unchanged, and a second dry-run reported no update.
• Fault injection after preserving v0.5.3 caused the candidate activation to fail, automatically restored the exact v0.5.3 tree, left the workspace unchanged, and reproduced the same retry plan hash.

Upgrade and manual action

Use the existing release-based $evolve update flow from v0.5.3: review UpdateDryRun, then apply only the exact returned plan hash. Restart the Agent task after a successful skill replacement so it loads v0.5.4. The update replaces only the installed skill and does not scan or rewrite workspaces.

v0.5.3 - Agent-owned semantic generalization

What changed

• Generalizes repeated narrow failures by Agent-owned behavior shape: responsibility, trigger, reachable execution path, intended effect, and observable verification.
• Uses summary-first, bounded evidence loading before opening full records.
• Requires subsumed rule/proposal IDs, preserved domain details, counterexamples, behavior-loss analysis, net context reduction, and explicit human approval.
• Adds fresh-context positive and negative acceptance cases with schema validation and canonical-LF digest binding.

Compatibility and boundaries

• Workspace Schema remains v1.
• No new public command, runtime similarity threshold, embeddings/vector database, background/global scan, or semantic auto-merge.
• Semantic replacements remain proposal-only until explicitly approved.

Verification

• GitHub Actions: Windows and Ubuntu passed for both push and pull-request runs.
• Exact merge-commit archive: 198 tests, 178 passed, 20 expected Windows skips, 0 failed.
• Upgrade validation is performed from the published v0.5.2 asset to this release asset before completion.

Upgrade

Use the existing release-based updater from v0.5.2. Run UpdateDryRun first, then apply the exact returned plan hash.

Agent Context Patch v0.5.2

What changed

• Lifecycle reconciliation now reaches a bounded post-application fixed point before returning, independent of proposal filename order.
• Applied Coordinator evidence now carries explicit post-application verification; the Outcome Interface rejects older or incomplete evidence instead of publishing a false success receipt.
• Unrelated approval work remains actionable, and semantic ordering, merging, or rewriting stays Agent-owned.

Compatibility and upgrade

• Kit Version: 0.5.2
• Supported Workspace Schema: 1 (unchanged; no workspace migration)
• Public commands and installer authority are unchanged.
• Upgrade explicitly with $evolve update; the plan preserves a recovery copy and requires approval before replacing the installed skill.

Known boundary

The fixed point covers Coordinator-owned writes in the current call. External concurrent writers still rely on the existing hashes, locks, CAS audit writes, and fail-closed recovery path.

Full changelog: v0.5.1...v0.5.2

Agent Context Patch v0.5.1

Agent Context Patch v0.5.1

Release commit: d6369ed
Artifact SHA-256: 5ca894a22f975accd9c0ccfbbca5da38e72d5f531dd8c9556f5ff65bbd79cf5c

Highlights

• Makes high-signal repaired tasks observable across detect, propose, and apply through one shared Evolution Outcome v1 interface.
• Validates exact lifecycle evidence and fails closed instead of reporting impossible or privacy-unsafe success.
• Aligns Codex and Claude delivery checkpoints while keeping ordinary one-off work silent.
• Completes Issue #7 without adding a daemon, telemetry, public command, durable receipt source, or Workspace Schema migration.

Compatibility

• Kit Version: 0.5.1.
• Workspace Schema: reads and writes Schema 1. No workspace migration is required.
• Existing commands and installer contracts remain compatible.
• The update replaces only the user-level evolve skill; it does not scan or modify workspaces or instruction files.
• Start a new Agent task after a successful update so the new skill is loaded.

Upgrade from v0.5.0

Run $evolve update, review the exact UpdatePlan and plan hash, then approve the candidate replacement. The tested path preserves a complete v0.5.0 recovery copy and leaves the workspace untouched.

Verification

• PR #10 passed npm test on Windows and Ubuntu.
• The exact merge commit d6369ed passed main-branch npm test on Windows and Ubuntu.
• The exact release archive passed npm test: 189 tests, 169 passed, 20 expected platform skips, 0 failures on Windows.
• The real immutable v0.5.0 asset passed release and asset attestation verification.
• The real v0.5.0 skill upgraded to this exact candidate through UpdateDryRun and UpdateApply; the installed skill reported 0.5.1, retained the v0.5.0 backup, a second dry-run returned NoUpdate, and the isolated workspace remained untouched.
• Fresh-Agent positive and negative acceptance passed for high-signal delivery and silent one-off behavior.

Current limits

Issue #8 (existing-workspace policy and adapter drift diagnosis) and Issue #9 (semantic tighten review) remain separate accepted follow-up work. This release does not add automatic tightening, background scanning, telemetry, silent rewrites, batching, or weaker hash and approval gates.

Agent Context Patch v0.5.0

Agent Context Patch v0.5.0

Release commit: 7831b49
Artifact SHA-256: 651cabdf4f12eeebf41701605a2e7cc54597b7765afb16bc26620ae23d0e43ef

Highlights

• Adds a deterministic Lifecycle Coordinator around the existing Commit Kernel.
• Resumes an interrupted eligible auto proposal or exact approved proposal only while every target still matches the persisted beforeHash state.
• Fails closed for mixed targets, semantic drift, and targets matching afterHash without an applied audit; matching bytes never fabricate provenance.
• Allows one narrow never-applied approved -> superseded transition only after a real stale conflict and a valid named replacement.
• Promotes proposal parsing and validation into production and protects proposal audit writes with an ownership lock, source-hash CAS, exact-source retry, and post-rename idempotence.

Compatibility and safety

• Kit Version: 0.5.0.
• Workspace Schema: reads and writes Schema 1. No migration is required.
• The Commit Kernel public interface and existing plan-hash, approval-hash, privacy, path, config, rollback, and before-hash protections remain unchanged.
• Reconciliation returns content-safe IDs, statuses, actions, reasons, and relative targets; it does not return proposal prose, target content, PatchPlan content, or absolute paths.
• Current approval-only proposals remain non-blocking, while stale or unsafe lifecycle states remain blocking.
• There is no new public command, daemon, startup scan, installer scan, update scan, sidecar receipt, or background polling.

Upgrade from v0.4.0

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.4.0 recovery copy. It does not scan or edit workspace context, AGENTS.md, or CLAUDE.md. Start a new Agent task after a successful update.

Existing Schema 1 workspaces remain compatible and are not migrated or rewritten merely to refresh Kit metadata.

Verification

• The exact release commit passed npm test on Windows and Ubuntu in GitHub Actions.
• The exact prefixed release archive passed npm test on Windows: 162 tests, 142 passed, 20 platform skips, 0 failures.
• A real immutable v0.4.0 asset upgraded to this exact archive through UpdateDryRun and UpdateApply; the installed Skill reported 0.5.0, retained the complete v0.4.0 backup, left the workspace untouched, required a new Agent task, and a second dry-run returned NoUpdate.
• Standards and Issue #5 specification reviews completed with no remaining findings.

Current limits

Issue #4 remains open. This release repairs lifecycle consistency for interrupted auto work and stale approval-waiting plans, but it does not yet add end-of-task detect / propose / apply observability, existing-workspace policy or adapter drift diagnosis, a concise semantic review surface for tighten, automatic tighten, or durable post-success undo. tighten continues to require human approval.

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-failure autonomously and apply eligible low-risk context additions in the same turn.
• Routine success returns one compact, non-blocking receipt; $evolve approve is 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 test on Windows and Ubuntu in GitHub Actions.
• The exact release archive passed npm test on 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.

Agent Context Patch v0.3.1

Agent Context Patch v0.3.1

Release commit: 1cf5d95
Artifact SHA-256: ccd657ccf5784f2c0dc954dfd73210deae0d2607114e9a395028bfcdfaf99c9b

Highlights

• Adds an experimental, on-demand personal multi-repository dogfooding Playbook without adding a public command.
• Adds this repository's own valid Schema 1 dogfood context.
• Adds fresh-context positive and negative acceptance cases so repeated verification failures evolve while one-off work stays out of durable context.
• Keeps Proposal, PatchPlan, Decision, Apply Attempt, cleanup, promotion, and approval semantics delegated to the canonical v1 protocol.

Compatibility

• Kit Version: 0.3.1.
• 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.
• The personal Playbook is experimental owner dogfooding guidance and loads only when explicitly requested.
• Start a new Agent task after a successful update so the new skill is loaded.

Upgrade from v0.3.0

Run $evolve update, review the exact UpdatePlan and plan hash, then approve the candidate replacement. The tested path preserves a complete v0.3.0 recovery copy and leaves the workspace untouched.

Verification

• PR #3 passed npm test on Windows and Ubuntu.
• Exact release archive passed npm test: 139 tests, 120 passed, 19 platform skips, 0 failures on Windows.
• The real immutable v0.3.0 asset upgraded to this exact candidate through UpdateDryRun and UpdateApply; the installed Skill reported 0.3.1, retained the v0.3.0 backup, and a second dry-run returned NoUpdate.
• A fresh-context Agent correctly classified the positive recurrence and negative one-off acceptance cases with no lifecycle contradiction.

Current limits

The Playbook is an owner experiment, not a validated external-user default. There is no daemon, telemetry, automatic promotion, silent upgrade, or automatic workspace migration. Review the 30-day personal evidence before expanding the public command or core abstraction surface.

Agent Context Patch v0.3.0

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.

Agent Context Patch v0.2.0

Initial Agent-first release with Workspace Schema 1, proposal-first context patches, deterministic commit safety, exact approvals, migration backups, and Windows/Ubuntu verification.

Artifact SHA-256: 9c5884f2c1882a04ae64058e9e5a9c2172676a0deb89170100e6c4346cf503c7

This GitHub-enforced immutable baseline is the supported source for future upgrade-contract testing.

One-time upgrade handoff: this v0.2.0 skill predates $evolve update. When a newer stable Release is available, ask your Agent to resolve releases/latest, verify that Release is immutable plus its tag, commit, and asset digest, then run the candidate Release Bootstrap in UpdateDryRun/UpdateApply mode. After that first upgrade, use $evolve update.