# Version 1.8.1 — dated fresh-session titles

This patch keeps the adaptive restart policy from v1.8.0 and adds a portable
human-readable naming rule for clients that can create or rename conversations.

## Behavior

- There is no fixed restart interval. Adaptive mode assesses after accepted
  milestones and context-pressure signals. Two compactions trigger assessment;
  daily mode adds a 24-hour assessment trigger. Neither forces a restart.
- Every fresh conversation keeps one stable task title and appends its own
  ` | started DD-MM` date. The source conversation receives its own verified
  start date when available.
- Formatting removes an existing start suffix before adding the current one, so
  retries and later handoffs do not stack dates.
- The registry preserves the full timestamp and timezone. Session ID, goal ID and
  checkpoint digest remain the identity and transfer evidence.
- Unsupported title creation or rename is reported but does not block an
  otherwise safe handoff. No universal title, session or archive API is claimed.

## Verification boundary

Repository validators and deterministic contract tests verify the documented
fields, idempotent suffix rule, identity boundary, README diagram and synchronized
manifests. They do not create, rename or archive a real client conversation.
Native behavior still requires adapter and client readback.

## Rollback

The rollback anchor is the published `v1.8.0` tag at commit
`13a5a6842678fff39b9c9f35040ddb9ba9d1ea8f`. Pin that tag and use its existing
session-restart contract. Do not rewrite the historical release record.