ContextLattice v3.17.0 - Public Core, Commercial Clarity

v3.17.0 makes the product boundary explicit: the open-source core is complete,
while commercial product facts come from one versioned, public-safe contract
instead of duplicated claims spread across code and documentation.

What changed

• config/commercial_truth.v1.json is the canonical commercial truth for
  release identity, stable feature IDs, plan names, pricing, limits, and
  protected-route eligibility. Generated public documentation, dashboard data,
  and gateway contracts now derive from that source.
• The OSS core remains complete for local memory, retrieval, sessions, compact
  Agent Packets, graph workflows, Context Passports, Context Mesh, policy
  learning, and inactive Skill Foundry exports.
• The macOS DMG, Linux bundle, and Windows MSI embed the deterministic payload
  from the exact tagged public commit. Installation is self-contained: it
  verifies bundled identity and checksums instead of cloning or pulling a
  repository.
• Adoption remains CLI-first. contextlattice context, resume, remember,
  finish, correct, and doctor are the normal operator path; dashboard,
  HTTP, and MCP surfaces remain companions.
• Tiny output budgets now retain session_id and agent_id, so a clipped pack
  preserves the identity needed to continue the same agent session.

Commercial boundary

Embedded paid billing and entitlement implementation code has been removed from
the public tree and public installers. The public repository retains only the
public-safe product contract and generated descriptions needed to explain the
boundary; paid purchasing, issuance, and protected runtime operations remain
separate from the OSS core.

Public installer assets

• ContextLattice-macOS-universal.dmg
• ContextLattice-linux-bootstrap.tar.gz
• ContextLattice-windows-x64.msi

Stable releases use vX.Y.Z. Manual release-workflow reruns may also target the
matching vX.Y.Z-public alias when both tags resolve to the same public commit.