FreshCtx 0.16.0

FreshCtx 0.16.0 qualifies the existing protected-action boundary across lifecycle paths without changing runtime semantics.

Qualification evidence

• Repeated invocation revalidates and blocks a later attempt after declared evidence changes.
• A real LangGraph interrupt/checkpoint/resume path revalidates immediately before the resumed action and blocks stale reasoning with zero action executions.
• Nested protected boundaries revalidate independently; a stale inner action never starts.
• Shared observations across multiple reasoning paths retain the existing memoized graph behavior.
• Existing allow, warn, block, refresh, replan, and require-approval policy outcomes remain unchanged.
• The documented monotonic-version strategy detects an A→B→A source change before action.

Validation

• Protected CI passed on Python 3.10, 3.11, 3.12, and 3.13.
• Framework conformance, MCP Guard, A2A Guard, package, quality, and Windows onboarding jobs passed.
• The official wheel and source archive were built from merged commit 7a89d6de342b88de6fbfd84a6857b911dbcad6d8 and passed installation and metadata checks.
• The isolated-build setuptools minimum is now 83 following a build-environment security advisory. FreshCtx has no new runtime dependency.

Compatibility and scope

No public API, schema, freshness state, policy, adapter, audit event, or runtime semantic changed from 0.15.0. FreshCtx reports and records the decision at the protected boundary. Applications and frameworks continue to own downstream execution, retry, resume, authorization, transactions, recovery, and idempotency.

Install:

python -m pip install freshctx==0.16.0

See docs/RELEASE_0_16_0_QUALIFICATION.md for the full acceptance record and limitations.