### A later schedule adds passes, what a receiver needs rides on the bearer, and a node schedules its own one-way sending

- **Adding passes is no contradiction** ([extensions/carousel.md](extensions/carousel.md) §4.5, §6.2 step 4): along
  their chain, a later schedule of one instance that keeps every earlier entry, with at least its passes at the same
  instants sending the same symbols, extends the one before it, and may add objects. The last stands and the earlier
  are labelled `extended`. An object available stays available at the same pass, a statement that held still holds,
  and a plan listens to what it listened to and completes where it completed. A schedule that drops an object, or
  withdraws, moves or changes a pass, still sets aside every schedule of its instance (`schedule_contradicted`). A
  timeliness plan reads the same schedule, and labels it the same. A single pass's period, which is not read, may be
  given by the schedule that extends it.
- **In-band repetition** (carousel §8.1, §8.2): on an instance whose schedule stands, the publisher sends on the
  instance the group receipt, its claims from the head of their chain to the instance's last schedule, and the head
  of its origin's key log, at least once per the schedule's interval: the least period of its entries of two passes or
  more, or, where every entry has one pass, the least duration. A verifier given what a receiver acquired checks that
  it suffices: `inband_chain_incomplete`, `inband_not_scheduled` or `inband_key_log_missing` otherwise, and the
  interval as `inband_ms`. A log on the bearer still anchors nothing.
- **A node's schedule** ([extensions/cache-authority.md](extensions/cache-authority.md) §5.6, carousel §4.3): a node
  states its plan for its own cache instance in a `schedule` claim signed by its own key, which needs `schedule` from
  its operator. The verdict of cache-authority §7 now reads schedules: a publisher's by carousel §6.2 step 4, a node's
  beside its own instance, and another key's schedule of that instance is set aside
  (`cache_schedule_signer_mismatch`) and contradicts nothing. A statement of carousel §6.4 offered with a loss bound
  and an overhead is held to the schedule that stands there. A node's schedule credits nothing, and carousel's verdict
  and timeliness' plan read the publisher's schedules alone.
- **A §9 line with a ladder** (cache-authority §9): the lines of a timeliness entry derived from all three kinds of
  held-at statement read every rung of a ladder, and state its list of instants as timeliness §6.3 does.
- **Breaking:** `api:rust:wai::carousel::ClaimVerdict::Extended` and `api:rust:wai::timeliness::ClaimVerdict::Extended`: a
  schedule a later one extends is a new label, not `stands`. A match over either enum takes the new arm.
- **Breaking:** `api:rust:wai::cache_authority::ClaimVerdict::Stands` and `api:rust:wai::cache_authority::ClaimVerdict::Extended`:
  the cache verdict now reads schedules. A match over the enum takes the new arms; a schedule that was `context_mismatch`
  there now gets one of them.
- **Breaking:** `api:rust:wai::cache_authority::Inputs::held` and `api:rust:wai::cache_authority::Verdict::held`: the
  statement of carousel §6.4 the verdict holds to a schedule. A caller that builds `Inputs` field by field sets `held: None`.
