feat(archive)!: serve a stored broadcast through archive::Consumer

doc/bin/cli.md

@@ -307,8 +307,8 @@ equivalents.
 # Record every broadcast announced under `event`
 moq --connect https://relay.example.com/anon --broadcast event export archive s3://recordings
 
-# Replay a timeline recording under another name
-moq --connect https://relay.example.com/anon --broadcast event-replay.hang import archive s3://recordings/event
+# Replay one recorded broadcast under another name
+moq --connect https://relay.example.com/anon --broadcast event-replay.hang import archive s3://recordings/event/@<epoch>
 ```
 
 `export archive` records every broadcast announced at or under `--broadcast`
@@ -325,10 +325,15 @@ or stitches into an older recording. Any recording that fails ends the export.
 `--retention 1h` keeps only the last hour, a DVR, deleting older objects
 `--retention-grace` (default 30 s) after they leave the window.
 
-`import archive` republishes a timeline recording made by an older `moq` as
-live tracks, fetching spans on request. It ends where the recording ends;
-`--follow 2s` keeps polling a recording still being made. It does not yet read
-the per-track layout that `export archive` writes.
+`import archive` republishes one recorded broadcast, the `<broadcast>/@<epoch>`
+prefix `export archive` wrote, as an ordinary broadcast under a new epoch: every
+track, the catalog included, with its original groups, frames, timescale, and
+priority. Each track is live from its newest stored group and serves older
+groups from the store on request, with no max age, so the whole recording stays
+reachable. A recording still being made is followed, checked every `--refresh`
+(default 1 s), until `export archive` marks it complete; one whose export
+stopped early stays live. It refuses a prefix with no recording, or with keys
+`export archive` does not write.
 
 Store URLs are `file:///absolute/path`, `s3://bucket/prefix`,
 `gs://bucket/prefix`, or `az://container/prefix`, with credentials from the

doc/bin/hls.md

@@ -50,8 +50,17 @@ What that means for you:
 - **URLs name the publisher instance.** Every URL the multivariant playlist and DASH manifest list sits under `@<instance>`, the publisher's epoch, so every edge and every reload derive the same URLs and a CDN in front of export caches them. A restarted publisher gets URLs of its own, whose numbering starts over. The multivariant playlist and manifest switch to it at once, while a player already on the old instance keeps playing until that publisher leaves; the player then has to reload the multivariant playlist. An instance without an epoch (one that reached export over moq-lite-06 or older) gets an id each export mints, so only that export serves its URLs.
 - **Only a clean finish ends a playlist.** `EXT-X-ENDLIST` and a `static` DASH manifest mean the timeline finished. If the segment-boundary rendition's timeline fails instead, such as a publisher dropping its session, every media playlist and the DASH manifest answer HTTP 500 with `Cache-Control: no-store`, so a truncated recording never looks complete. A rendition whose own timeline fails answers the error alone and leaves the multivariant playlist and DASH manifest, so players switch to a sibling.
 
-A [`moq-archive`](https://docs.rs/moq-archive) recording replayed through its
-`Reader` is served the same way, with no second stored copy, and lists the
+A [`moq-archive`](https://docs.rs/moq-archive) recording is served the same
+way, with no second stored copy: record a broadcast, republish it, and export
+the republished broadcast.
+
+```bash
+moq --connect https://relay.example.com/anon --broadcast event export archive s3://recordings
+moq --connect https://relay.example.com/anon --broadcast event-replay.hang import archive s3://recordings/event/@<epoch>
+moq --connect https://relay.example.com/anon --broadcast event-replay.hang export hls --listen '[::]:8089'
+```
+
+The archived catalog and timelines replay as recorded, so the export lists the
 same window as a live broadcast.
 
 `--listen-tls-cert`/`--listen-tls-key` or `--listen-tls-generate` serve HTTPS,

quest/m1/api-audit/README.md

@@ -41,11 +41,9 @@ Rules every child follows:
 - Each child lists its public API and wire impact in its PR, and its Impact
   bullet says how to migrate.
 
-Already gated elsewhere, so not children: the archive `Producer` and `Reader`
-disagree on layout while both claim version 2
-([archive consumer](/quest/m1/archive/consumer.md)), and the binary-to-flate
-fold is followed by flate's removal ([compress migrate](/quest/m1/compress/migrate.md)).
-Both are in m1, so the cut waits for them. hang's
+Already gated elsewhere, so not a child: the binary-to-flate fold is followed
+by flate's removal ([compress migrate](/quest/m1/compress/migrate.md)), in m1,
+so the cut waits for it. hang's
 `Archive::replay_epoch` goes with the root `archive` section in
 [catalog HLS](/quest/m1/archive/catalog-hls.md).
 

quest/m1/archive/README.md

@@ -84,7 +84,6 @@ from a host. Each child fixes the stale docs it touches.
 
 ## Required
 
-- [Archive consumer](/quest/m1/archive/consumer.md) - `archive::Consumer` serves a stored prefix as a broadcast from its key listing, and `moq export/import archive` use the new pair
 - [Catalog HLS field](/quest/m1/archive/catalog-hls.md) - the root `archive` section is gone; an opt-in per-rendition `hls` field marks each aligned HLS segment's first group and pts and declares its nominal duration
 - [Fixed HLS target duration](/quest/m1/archive/hls-target.md) - one `EXT-X-TARGETDURATION` for the run, from the declared `hls` duration; an overrun is listed with a warning
 

quest/m1/archive/catalog-hls.md

@@ -88,7 +88,3 @@ segment is refused, and that a rendition without `hls` gets no playlist.
 Public API: `hang::catalog::Archive` is deleted, the rendition types gain an
 `hls` field in Rust and JS, and `moq-mux` gains the opt-in. Wire: the hang
 catalog format.
-
-## Required
-
-- [Archive consumer](/quest/m1/archive/consumer.md) - the old writer and reader, which read the root `archive` section, are gone first

quest/m1/compress/migrate.md

@@ -16,9 +16,8 @@ See the [epic](/quest/m1/compress/README.md) for the decisions.
 
 Decided 2026-10-20 (maintainer): the timeline is `<track>.hls` with
 `compress: true`, never `<track>.hls.z`. [Catalog HLS field](/quest/m1/archive/catalog-hls.md)
-renames it and publishes it uncompressed, and the
-[archive consumer](/quest/m1/archive/consumer.md) replaces the CLI's archive
-reader, so this quest lands after both and only sets the flag.
+renames it and publishes it uncompressed, and the archive consumer replaced
+the CLI's archive reader, so this quest lands after it and only sets the flag.
 
 - Delete the `.z` names outright, with no transition release: hangz is opt-in
   and `main` takes breaking changes. The Impact bullet says how to migrate.
@@ -61,4 +60,3 @@ Public API: removals listed above. Wire: the hang catalog loses
 ## Required
 
 - [Catalog HLS field](/quest/m1/archive/catalog-hls.md) - renames the timeline to `<track>.hls`, which this compresses
-- [Archive consumer](/quest/m1/archive/consumer.md) - replaces the CLI archive reader that reads `.z` timelines

quest/m1/release-audit/README.md

@@ -98,7 +98,6 @@ child records whether its behavior is new on main or inherited from release.
 - [JS subscription ranges](/quest/m1/subscribe-ranges/js.md) - range lists and frame offsets build on the bounds fixed here
 - [OBS video source](/quest/m2/obs-moq-video/source.md) - the decoder replacement keeps the timing and EOF behavior fixed here
 - [Compressed tracks](/quest/m1/compress/README.md) - application migration has an existing owner
-- [Archive consumer](/quest/m1/archive/consumer.md) - current producer and CLI reader still need the new-format roundtrip
 - [Measured release performance](/quest/m1/release-perf/README.md) - existing paired benchmark regressions and their confirmation runs
 - [Transport performance audit](/quest/m2/audit-perf.md) - congestion-control coverage remains outstanding
 - [Binding timestamps](/quest/m1/binding-timestamps.md) - exact timestamps across language APIs

quest/m2/README.md

@@ -181,7 +181,9 @@ lite-07; bitrate enforcement is not part of this release.
 - [QUIC on the sim](/quest/m2/quic-sim.md) - MoQ sessions and the relay run over `moq-quic` on the seeded sim, reusing its `Pair` and `Link`
 - [Seeded sim](/quest/m2/sim-seed.md) - sim tests draw every jitter from one seeded generator and replay bit-exact
 
+- [Archive time ranges](/quest/m2/archive-time-ranges.md) - a `Time(pts)` range on an archive consumer broadcast resolves from the archive's keys, however old
 - [DVR rewind](/quest/m2/archive-dvr.md) - follow-on capability after the release contract is stable
+- [An errored track end keeps its history](/quest/m2/errored-end.md) - a replayed archive ends with its source's error after serving every stored group, instead of a clean finish
 
 - [JS HLS field](/quest/m2/js-hls.md) - follow-on capability after the release contract is stable
 

quest/m2/archive-dvr.md

@@ -31,4 +31,4 @@ over missing groups, and return to live.
 ## Required
 
 - [Subscribe ranges](/quest/m1/subscribe-ranges/README.md) - the `Time(pts)` range a seek sends
-- [Archive consumer](/quest/m1/archive/consumer.md) - serves a stored broadcast and resolves time ranges from its keys
+- [Archive time ranges](/quest/m2/archive-time-ranges.md) - the archive consumer resolves time ranges from its keys

quest/m2/archive-time-ranges.md

@@ -0,0 +1,35 @@
+# [M] Archive time ranges
+
+## Goal
+
+A `Time(pts)` range on an `archive::Consumer` broadcast resolves from the
+archive's key listing, not only from the groups the consumer's cache holds:
+a start reaches the stored group containing pts, and an end stops just after
+it, however old.
+
+## Plan
+
+Decided 2026-10-23 (maintainer, on
+[moq-dev/moq#6262](https://github.com/moq-dev/moq/pull/6262)): this stays in
+m2, required by [DVR rewind](/quest/m2/archive-dvr.md), rather than blocking
+the archive consumer, which ships without time anchors.
+
+The consumer creates each track live from its newest stored group and serves
+older groups through `track::Fill`, so its cache holds almost nothing a time
+anchor can resolve against: today a `Time(pts)` start older than the newest
+group resolves to the oldest cached group instead. A `Fill` names group
+positions only, so an anchor the cache can't resolve never reaches the
+handler. [moq-dev/moq#6171](https://github.com/moq-dev/moq/pull/6171) deferred carrying the anchor to the consumer quest, which
+landed without it.
+
+- `moq-net` passes a time anchor the cache can't resolve to the
+  `track::Dynamic` handler, unresolved, in its fill.
+- The consumer resolves it from its index: every object key carries its first
+  frame's pts, so the object holding pts is one lookup, and the group within
+  it comes from the stored group timestamps.
+
+Test with the in-memory store: a start and an end older than the newest
+group, an anchor before the oldest stored object, an anchor in a gap, and an
+untimed track refusing it.
+
+Public API: `track::Fill` gains the anchor. Wire: none.

quest/m2/errored-end.md

@@ -0,0 +1,41 @@
+# [M] An errored track end keeps its history
+
+## Goal
+
+A track can end with an error and still serve the groups it holds or can fill:
+a reader arriving later gets that history, then the error, instead of either
+the error alone or a clean finish. `archive::Consumer` replays a stored
+`{"error":code}` end this way, so a replayed recording ends the way its source
+did.
+
+## Plan
+
+From [moq-dev/moq#6262](https://github.com/moq-dev/moq/pull/6262), decided by
+the maintainer 2026-10-23: the consumer replays an errored end as a clean
+finish after its newest stored group, plus a warn log, because
+`track::Producer::abort` refuses every later reader the stored history. The
+alternatives were an abort (loses history) and an abort only after the last
+group (still refuses later readers). This quest replaces the clean finish.
+
+- `moq-net`: an end that records an error alongside the final position.
+  Readers below the end read groups and fills as after `finish_at`; a reader
+  reaching the end gets the error instead of `None`. Unlike `abort`, the cache,
+  fills, and the listing stay as after a finish. Pick the API shape in the PR
+  with options and a recommendation, such as `finish_at` taking an end reason,
+  and no `finish_with_x` variant.
+- Carry it across a hop if a relay must forward it: moq-lite resets the
+  subscription with the code today, which a later subscriber never sees. Any
+  wire change goes in the next unpublished lite version and its draft.
+- `archive::Consumer` maps `End::Error(code)` to the new end and drops its
+  warn log.
+
+Test a consumer replaying an errored track: a subscriber from the oldest group
+reads every stored group and then the error; a later fetch still reads stored
+groups.
+
+Public API: a `track::Producer` end carrying an error, and what a reader
+observes at it. Wire: possibly a lite track end carrying an error code.
+
+## Related
+
+- [DVR rewind](/quest/m2/archive-dvr.md) - seeks back through an archive whose source may have ended with an error

quest/m2/performance-survey/README.md

@@ -167,9 +167,8 @@ No duplicate quest or workflow edit belongs here.
   `Unlimited`; their numbers cannot establish controller performance. Expand
   reassembly flight/reordering coverage there before proposing another index.
   [BBR study](/quest/m2/quic-bbr-study.md) owns controller behavior.
-- Archive reader internals are being replaced by the
-  [archive consumer](/quest/m1/archive/consumer.md). Do not optimize the
-  outgoing timeline reader. Benchmark the landed replacement when revisiting it.
+- The archive consumer replaced the timeline reader; benchmark it when
+  revisiting archive reads.
 
 ## Required
 

quest/m3/archive-paced-replay.md

@@ -10,7 +10,7 @@ viewer who joins late joins mid-replay.
 
 ## Plan
 
-Retargeted 2026-10-17 onto [Archive consumer](/quest/m1/archive/consumer.md),
+Retargeted 2026-10-17 onto the archive consumer,
 whose broadcast already includes the archived catalog as an ordinary track.
 
 - Decided 2026-10-08: the catalog paces on the same clock as the media, each
@@ -36,7 +36,3 @@ whose broadcast already includes the archived catalog as an ordinary track.
   current group, and that two tracks stay aligned.
 - Deferred in the 2026-09-30 audit and moved to m3 in the 2026-10-05 audit: no
   named consumer.
-
-## Required
-
-- [Archive consumer](/quest/m1/archive/consumer.md) - the stored broadcast this paces