# Cuetree — current verification handoff

## Singles and filename evidence — 2026-10-16

The experimental Riff branch implements [Singles classification](/Cuetree/singles) after the
unchanged ordinary grouping policy and [filename ordinals](/Cuetree/filename-evidence) before it.
The [format owner](/Cuetree/persistence) fences synthetic personal baskets and extension evidence.
`RootSpec.book` and retained caller-supplied duration/content evidence protect library independence.
`advancePublication` accepts the optional ordinary grouping policy and reclassifies on factual
expiry; current chapter expansion survives unrelated expiry.

All 147 core and six CLI cases pass, with Kotlin style, upstream runtime provenance and independent
source-only `check assemble`. The source export consumes a separate Cuegrain checkout without Riff
or Android. Private real-library replay confirms position conservation; it is not a claim of
complete on-device scanning. The [Riff handoff](/Riff/LATEST/worklog) owns signing, device
reset/installation, remaining full-scan verification and the uncommitted branch receipt.

## Album V2 and format 10 — 2026-10-13

Implemented the imported [grouping contract](/Riff/LATEST/album-grouping) with global resolution,
partial numbering, neutral absent evidence, corroborated disc suffixes, conservative release guards,
logical-position copy resolution and linear-storage complete linkage. Catalog construction and
evidence responsibilities use separate files; no Android dependency, new wire field or migration was
introduced. The exact [format owner](/Cuetree/persistence#mvp-format) now fences these semantics.
Direct ALBM multiplicity survives encoding and consumer projection.

All 124 core and six CLI tests pass, including strict control-character JSON round trips and exact
64-bit values. Large structural/residual fixtures and cancellation pass within their documented host
scope. The executable desktop JAR is rebuilt. The
[Riff delivery](/Riff/LATEST/album-v2-delivery-261013) records integration, installations and
ongoing full device rebuilds; final device catalog counts are not inferred from the host fixture
replay.

## Staged pipeline verified — 2026-10-12

Strict discovery/acquisition barriers, retained L0 facts, completion flags and interrupted revision
restart are implemented. Current APIs and the format owner define the new behavior; a format change
requires complete index recreation, without migrations or unsupported-format recovery. The
[integration verification](/Riff/LEGACY/2026-10-15-dependency-refresh/Riff_LATEST_worklog#staged-indexing-implemented-2026-10-12)
records fresh core/CLI cases, independent source-export checks, copied fat-JAR binary/JSON checks
and disposable Android coverage. Older dated receipts below describe their original editions only.
No commit or push is performed for this step.

## Audit corrections committed and pushed — 2026-10-08

The shared semantic comparison, Android/desktop CLI/runnable-consumer integration, regression tests
and documentation exports are included in integration commit
`77bb8e9beaf7dc0a85e18d0ac8e04672f29e0ed2`, pushed to `origin/main`. Remote main and local HEAD
match, and the working tree was clean after push. The user explicitly authorized this public Git
receipt. The
[integration completion record](/Riff/LEGACY/2026-10-15-dependency-refresh/Riff_LATEST_worklog#modal-and-audit-changes-committed-and-pushed-2026-10-08)
owns the complete 47-file scope; the verification evidence below remains unchanged.

## Unchanged desktop publication fixed — 2026-10-08

Following the explicitly approved [integration audit](/Riff/LATEST/consistency-review-20261008),
core owns `Snapshot.hasSameContentAs` under [Indexing](/Cuetree/API/Indexing). It ignores
publication/record generations and transient diagnostics while preserving all other fields and
occurrence order. Android, CLI and the independent runnable consumer now use it. Binary and JSON
no-op passes keep CURRENT/PREVIOUS/generation and all catalog bytes unchanged. A first JSON request
for a binary-only cohort publishes a complete new immutable cohort. Requested-output behavior is
specified in [build](/Cuetree/build#unchanged-input).

Fresh verification passes 95 core and six CLI JVM cases, style, provenance/check and fat-JAR build.
Tests include semantic equality versus metadata/evidence/availability/order changes, repeated
binary/JSON scans, JSON upgrade, exact schema round trips, converter failure, clock rollback and
Long.MAX_VALUE exhaustion. The separate consumer passes a fresh demo, unchanged-cohort assertion,
catalog reconstruction, source resolution and root withdrawal/return. A copied fat JAR runs outside
the source tree with no classpath/source dependency; no-op comparisons verify every catalog byte.
The old cached demo remains preserved after checksum mismatch; a fresh fixture establishes current
behavior. Evidence: `status/consistency-fixes-261008` in the integration checkout. No format,
identity, parser, dependency, packaging-boundary or Git-history change was needed.

## Desktop/API compatibility — 2026-10-06

93 core and six CLI JVM tests passed without failures/errors/skips, with Kotlin style, upstream
runtime provenance, assemble/installDist and clean source-only export verification. The exported
Cuegrain checkout was selected explicitly; no Android or Riff build dependency is used. An isolated
fat JAR ran help, binary and JSON synthetic indexing with exact packaged-schema equality. The
current format 7 JSON round-trip includes metadata revision/rebuild pending, structural tables,
source evidence, nullable/zero scalars, Unicode, ordered membership and signed Long extremes.
Converter failure retains CURRENT and wrong compiler versions fail explicitly.

The CLI and runnable consumer now select `max(now, previous.generation + 1)` with checked addition,
matching the strict-generation API after clock rollback. The regression covers a future-dated store,
next-generation JSON publication and Long.MAX_VALUE exhaustion without a pointer change. The
consumer passed a fresh demo and reload, projection reconstruction, source resolution and root
withdrawal/return with preserved identities. Its old cached demo was preserved after exact-format
checksum rejection.

[Build](/Cuetree/build), [API](/Cuetree/API) and [persistence](/Cuetree/persistence) retain
authority; no format, identity or metadata-parser requirement changed. Riff's Android encoded-audio
identity remains distinct from host MockMediaID. Source changes are uncommitted in the integration
checkout based on `3232fd4`; exact commands and summaries are under `status/ai-header-261006`. The
[integration audit](/Riff/LATEST/desktop-cuetree-compatibility-20261006) records scope and
limitations.

The library retains source facts, stat reuse, hidden CUE metadata, per-field CUE priority, ordinary
grouping before chapter expansion and bounded ordered acquisition. Current metadata-rebuild headers
and crash-resume reacquisition are verified by the core suite. Earlier verification editions are
archived; no migration or compatibility reader is introduced.