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.