# Lixity v0.8.0

Released 10 November 2026. Lixity brings its multilingual public presence and
local manuscript workspace into a shared visual design, with new exploratory
analysis descriptors and clearer runtime progress.

## Public website and reading workspace

- Seven equivalent static landing pages with native language navigation,
  reciprocal language metadata and localized product introductions. Technical
  documentation remains in English.
- A stronger ultramarine identity, manuscript surfaces, consistent controls
  and navigation across Pages, the local app and exported reading websites.
- Improved light/dark badge contrast, narrow-screen tables and headings,
  reader control typography and reading/context panel alignment.
- Regenerated public examples and media. The Effi Briest example retains its
  existing 1,770,000-byte limit by excluding an inactive editor from read-only
  report bundles, without reducing the published chapter count.

## Exploratory analysis

- Sensory cue densities for seven languages, linked to literal evidence and
  contextual reader tools; cue/filter ratios remain unknown for zero denominators.
- Morphology-based verb and descriptive vocabulary MATTR subsets.
- Sentence-length variation, rolling means and compact chapter timelines.

These are review aids, not validated immersion, pacing or literary-quality
scores. See [Methods](https://mfahsold.github.io/lixity/METHODS.md) and [Stability](https://mfahsold.github.io/lixity/STABILITY.md) for
formulas, sparse-data behavior and interpretation limits.

## Operations and fixes

- Managed Linux stop/restart handles a process disappearing while its procfs
  identity is being read. Live processes with unreadable identity still report
  unknown rather than being treated as stopped.
- Structured event logging and JSON output improve pipeline and service lifecycle
  observability. Speech progress is clearer in CLI and browser status polling.
- Qwen reference-voice handling and reader/table presentation corrections.
- Public analytics and documentation clarify data boundaries; a staged IndexNow
  ownership file supports explicit notifications without promising indexing.

## Upgrade

```sh
uv tool upgrade lixity
```

For a pinned installation, use `uv tool install --python 3.12 --managed-python lixity==0.8.0`. Restart an existing local service explicitly after upgrading;
installing the package does not update an already running process. No new
required runtime dependencies are introduced.

## Project compatibility and recovery

Valid settings for currently supported engines remain readable in their original
audio schemas. Project-wide pronunciations use schema `/2`, Coqui profiles use
`/3`, and saved external provider profiles use `/4`. Lixity v0.7.7 cannot read
those newer settings.
Before saving an external provider to an existing project, use the explicit
`audio-migrate --to-schema-4` preview and apply with the reviewed snapshot and a
new backup outside the project. The same procedure is available in voice
profiles. Keep separate backups of manuscripts, voice references and research;
the audio migration ZIP contains root configuration files, not those assets.

When testing recovery on a project copy, preserve the current configuration and
restore files listed in the ZIP's `manifest.json`. If the manifest does not list
`lixity.toml`, it did not exist before migration; after preserving any later
changes, remove the migration-created file from the recovery copy so that it no
longer overrides `pyproject.toml`. Verify the recovered project with a compatible
application version. Restored Piper settings require an older version that can
render them; the Qwen replacement is not an equivalent voice.

See the [usage guide](https://github.com/mfahsold/lixity/blob/main/docs/USAGE.md)
for exact migration, audio export and recovery instructions, and the
[stability guide](https://github.com/mfahsold/lixity/blob/main/docs/STABILITY.md)
for measurement limitations.