v0.6.24

Release Notes - v0.6.24

Summary

• Context mode now carries source material through a complete assimilation lifecycle and can finalize the run without leaving stale active state.
• Curators can compile extracted knowledge into an atomic, linked, human-editable Wiki in one rollback-safe transaction.
• Release readiness now has explicit regression coverage for deleting raw inputs after curation, plus archived evidence for the resolved context incidents.

Added

• Added the context finalize lifecycle command and the supporting state transitions so successful assimilation runs can be closed deterministically instead of remaining active. (1a7e820)
• Added transaction coverage, command coverage, and task-level evidence proving the repaired context lifecycle works across the supported execution path. (a649732)
• Added generated CLI reference coverage for the new context finalization surface so installed users can discover the complete lifecycle from the public command documentation. (b9c6694)
• Added a dedicated raw-deletion release-readiness regression that proves curated Wiki knowledge remains searchable after the original downloaded source files are removed. (12cdf58)
• Added context extraction apply ... --synthesize-wiki, which compiles extracted claims, entities, edges, aliases, and conflicts into linked Wiki pages and indexes in the same transaction. (c116fea)
• Added stable atomic-knowledge blocks, source provenance blocks, entity-to-page links, append-only Wiki logging, and source-count summaries for maintainable long-lived context. (c116fea)

Improved

• Recorded the v0.6.23 hosted publication evidence on the owning release task, preserving an auditable starting boundary for this patch plan. (3328e5c)
• Preserved the verified context lifecycle result through the first protected-main closure packet, including focused tests, full-suite coverage, smoke, typecheck, formatting, routing, CLI help, and doctor evidence. (ff8ed12)
• Recorded a separate verification checkpoint for the generated CLI reference so public documentation freshness is traceable independently of implementation evidence. (076add8)
• Normalized formatting in promoted context incident records so runtime and bundled policy copies remain deterministic and pass repository formatting gates. (fffb80f)
• Preserved hosted verification for the formatting correction, preventing generated incident-policy drift from being silently folded into release preparation. (b115cd2)
• Synchronized promoted context incidents between the repository policy and bundled installation assets so installed projects receive the same operational guidance. (0af31a1)
• Recorded the first focused verification checkpoint for the split raw-deletion regression, separating release-readiness proof from broader context test setup. (48009fb)
• Recorded the final protected-main verification checkpoint for the split regression after integration, keeping the release plan tied to the landed test evidence. (4ebb471)
• Preserved the atomic Wiki compiler's local evidence through its initial closure packet: synthesis and transaction tests, 115 context tests, a downloaded-source end-to-end run, and the full project suite. (deca6a1)
• Preserved existing Wiki epistemic status, visibility, aliases, conflicts, custom frontmatter, and human prose when applying partial compiler updates. (2dcc4da)
• Merged duplicate page declarations deterministically and rejected conflicting scalar declarations after review, while keeping the synthesis implementation within repository size limits. (7c73f7c)

Fixed

• Synchronized the workflow recovery snapshot with the 0.6.24 repository expectation so post-release recovery cannot restore a stale CLI version contract. (release verification)
• Updated the top-level CLI help snapshot to include the shipped context finalize-task command, closing the documentation-contract gap found by the release prepublish suite. (release verification)
• Fixed context-runner completion so successful runs no longer retain stale lock or active-run state, and made finalization idempotent for safe retries. (1a7e820)
• Fixed raw-source cleanup coverage by moving the deletion scenario into its own release-readiness test, eliminating coupling to unrelated assimilation fixtures. (12cdf58)
• Fixed the context compiler's partial-update behavior so it no longer overwrites existing page metadata or creates duplicate atoms for stable knowledge identifiers. (2dcc4da)
• Archived the two resolved context incidents with their merge commits, regression tests, and mitigation evidence instead of leaving them as active release blockers. (56bff8b)
• Cleared the active incident registries only after 27 context regressions, incident checks, asset parity, routing, doctor, formatting, and smoke verification passed. (d9804ac)
• Corrected the archived raw-deletion evidence to cite the shipped release-readiness.raw-deletion.test.ts file rather than a nonexistent test path. (010550f)
• Preserved the corrected incident archive through hosted review and final closure, leaving the v0.6.24 release gate empty and auditable. (9de8944)

Upgrade Notes

• No breaking changes are introduced by this patch release.
• The published package set moves from 0.6.23 to 0.6.24.
• Existing context directories remain compatible; synthesized Wiki updates preserve human-authored prose and supported frontmatter fields.
• To compile extracted context into the Wiki, use context extraction apply <run-id> --synthesize-wiki after reviewing the extraction artifacts.
• branch_pr publication remains protected: merge the release candidate into main, then publish from the exact merged release SHA.

Verification

• Release notes cover every commit in the frozen v0.6.24 release plan generated from v0.6.23 at base commit 9de894461a781549fd1044d588037870e5532acc.
• The context work passed focused synthesis and transaction tests, 115 context tests before review, 1,930 full-project tests after review, and a downloaded-source end-to-end assimilation run with idempotent re-application and successful curated-only search after raw deletion.
• Release parity, incident clearance, documentation freshness, routing policy, doctor, full-fast CI, hosted pull-request checks, GitHub tag/release state, and npm package parity are required before final closure.
• Publication targets agentplane, @agentplaneorg/core, and @agentplaneorg/recipes at exactly 0.6.24.