v0.2.0

Added

• The full index of the corpus is published at /documents/ on every
  deployment, as a route the platform injects. It is the address a folder
  heading has (/documents/#<folder>), which is where a folder card or a
  breadcrumb segment lands when that folder has no page of its own. See
  ADR-017.
• home.recentLimit and home.corpusIndex in site.config.json. The first
  sets how many documents the "recently updated" band lists; the second decides
  whether the home page carries a copy of the full index or links to the page.
  Both are optional and default to what the home page did before — six rows and
  an index — so an existing configuration keeps its home page unchanged.

Changed

• documents is a reserved slug. A new Drive folder or document whose name
  yields it is allocated a suffixed address instead of one the new route would
  shadow. A corpus that already publishes /documents/ keeps its address and
  ctcdocs-sync validate reports the clash, which is fixed by renaming the
  source in Drive.
• Folder anchors address /documents/ rather than the home page. Where the
  home page keeps the index, a folder card without a folder page now opens that
  page instead of scrolling within the home page; the content is the same.
• The default sidebarPrefix links "All documents" beside "Home". A project
  that passes its own prefix links the page itself.

Fixed

• ctcdocs-verify-search no longer fails on a search index it has just built.
  Pagefind's writeFiles resolves while the backend's buffered writes are
  still in flight, so the check could serve an empty pagefind-entry.json and
  report it as unparseable JSON — a failure with nothing behind it. The check
  now writes the bundle itself, and serves no bundle before every file the
  search runtime starts from is on disk and non-empty.