ContextLattice v3.19.1 - Sessions That Actually End

ContextLattice v3.19.1: Sessions That Actually End

An agent run should not become a ghost because the command that finished it disagreed with the lifecycle contract. ContextLattice v3.19.1 makes terminal state exact from the CLI through the session ledger, rollup, agent state, and proof timeline.

The CLI remains the primary interface. HTTP remains the integration fallback.

What changed

• contextlattice_agent_session complete and fail accept flag-only --summary input without a slice-bounds panic.
• Terminal CLI commands emit the canonical session.completed and session.failed event types.
• Gateway ingestion canonicalizes legacy session.complete, session.fail, agent.session.complete, and agent.session.fail aliases before applying lifecycle state.
• A completed run now reports completed at the event, session, and rollup layers while agent lifecycle state reports done.
• Focused regressions cover both CLI terminal commands and all four compatibility aliases.

What did not change

• Agent Packet delta negotiation, exact reconstruction, and full-packet fallback.
• Local and shared proof-timeline behavior.
• Entitlement, workspace, storage, retention, and rollback boundaries.
• Quickstart requirements or third-party agent installation policy.

Verification

The corrected CLI completed a fresh live session without stderr. The completion event, persisted session, and rollup all reached completed; agent lifecycle reached done; and the resulting proof timeline remained contract-valid. Full Go suites passed independently in private, public, and public-paid lanes before merge.

Rollback

Returning to v3.19.0 restores the prior binary and is not recommended because it reintroduces the CLI lifecycle defects. Operators pinned to v3.19.0 can still post the canonical session.completed or session.failed event explicitly until upgrading.