2.4.0 — Configurable discovery and clearer memory coverage

Configurable discovery and reliance

Version 2.4.0 adds an optional project profile for Claude Code. An adopter can
choose automatic discovery for each submitted prompt, explicit discovery only
for prompts prefixed with Busca en VA: or Validated-memory:, or leave prompt
discovery off. It can independently prefer lightweight candidate guidance or a
reviewed reliance workflow. Discovery remains bounded, lexical and fail-open;
returned candidates still require inspection and do not establish truth or
checked use. Projects without a profile keep the previous behavior.

Requested learning now has a documented path for distilling an explicitly
requested lesson, choosing the appropriate memory or curated layer, and reviewing
one selected record without changing the project profile. Capture remains
selective: discovery, task completion and cancellation do not save learning
automatically.

Resumption, transfer and recovery

Checked consultation gains a read-only resume-use report that compares a
historical checked use with the requested scope and known pending origin review.
It supports explicit task handoff and resumption without treating an earlier
observation as perpetual eligibility.

The new selected-material view for show-transfer exposes the complete retained
semantic material for one imported origin before local proposal authoring,
including dependencies, predecessors and known correction context. Transfer
validation and capture paths were consolidated to avoid duplicate acquisition
work and to harden bounded history checks. Imported material remains historical:
it does not prove live freshness, authorship, semantic equivalence or local
acceptance.

New task-lifecycle and whole-project recovery guidance covers trusted handoffs,
bounded delegation packets, fresh source inspection, single-project backup and
restore, and staged one-root-at-a-time migration. These are explicit procedures;
the plugin does not automatically transport task state through compaction or
subagents, gate every deliverable, or recover several roots whose identities were
lost together.

Safer probes and clearer status

probe now gives each configured command a 60-second deadline by default, with
--timeout accepting a finite value from greater than zero through 3600 seconds.
Timeouts record unknown, emit a warning and continue. Cleanup and reaping are
also bounded, with platform and descendant-process limits reported explicitly.
Output volume remains unbounded; the deadline is not a subprocess sandbox.

status adds five non-gating coverage lines. They count active and superseded
knowledge units, then classify active units in each evidence state as anchorless,
never recorded, partially recorded or fully recorded. Coverage means that a
matching anchor verdict exists; it does not mean that verdict is current. Existing
freshness flags and exit-code behavior are unchanged.

Compatibility and update

This is an additive release. It introduces no new consultation storage schema and
does not force an existing store upgrade. Existing evidence, supersession and
explicit-upgrade contracts remain in place.

For a Claude Code marketplace installation, refresh the marketplace, update the
plugin, then restart Claude Code:

claude plugin marketplace update validated-memory
claude plugin update validated-memory@validated-memory

If the adopter also has a temporary or local development hook for the same event,
reconcile it before enabling the installed hook so candidate delivery is not
duplicated.

Validation

The frozen release passed 1,290 local tests, GitLab prepublication CI, and
postpublication CI on GitHub and GitLab (main, v2 and v2.4.0).
An independently built wheel from the exact release commit installed cleanly
and passed CLI smoke checks; 72 focused packaging-surface tests also passed.
These checks do not establish semantic understanding or savings in ordinary use.