kernel_chat 0.7.0

kernel_chat 0.7.0

kernel_chat 0.7.0 develops the package from a chat-oriented continuity
incarnation into a modality-neutral, user-owned semantic operating kernel for AI
while preserving receiver-relative adoption and explicit authority boundaries.

Main changes

• Portable carrier: adapters/portable/ 3.0.0 is the canonical
  provider-neutral entry. Chat and provider-specific adapters are incarnations,
  not the kernel identity.
• Experience becomes capability: reusable differences can change the
  competence that later understands or performs materially different work.
• Semantic continuity across reentry: later consumers preserve only the
  consequential owner/fact/method/time/reason/meaning/consumer/consequence
  relations instead of treating an identifier as the whole result.
• Evolutionary integrity: mobile observation, closure convergence,
  first-losing-transformation diagnosis and consumer/discovery proof are explicit
  without adding a central controller or mandatory workflow.
• Public product convergence: README, setup, adoption and user guidance now
  describe the same modality-neutral product and expose owner/source routes.
• Security and public hygiene: SECURITY.md, immutable-SHA workflow
  dependencies, privacy/reporting boundaries and historical-state hygiene are
  part of the public source.

Compatibility

• instance schema remains kernel_chat.instance.v1;
• portable entry remains 3.0.0;
• ChatGPT and earlier conversational paths remain supported as
  adapter/compatibility surfaces;
• root package version advances to 0.7.0 without automatically changing
  installed host instructions or user-owned instance state.

Material review

Reviewed semantic source:
10755f36a7764b8694e73a35e022efa69368e961.

• CI 35519877372: success;
• validator: valid=true, errors=[], warnings=[];
• tests: 62/62;
• matrix: 8/8 Python 3.11–3.14 × Ubuntu/Windows;
• review result: no_material_blocker.

The release tag must target the exact 0.7.0 promotion commit after that
commit has its own green CI. Release publication does not migrate existing
instances, update installed host instructions, prove receiver reachability or
establish behavioral assimilation.