fix(ddocs-indexer): worker fired 13-27x/day but was structurally unable to index anything (hardcoded date prefix)

[rwnq8]

Defect

qnfo-ddocs-indexer fires 13–27×/day but has produced one row of output ever.

Evidence	Value
SELECT COUNT(*), MAX(indexed_at) FROM ddocs_index_state	n=1, indexed_at=2026-09-04T09:57:49
worker_activity_daily req24 (09-10..09-13)	10, 27, 13, 13 — firing continuously
Worker created	2026-09-04

Root cause

The scheduled handler invokes /index?limit=30 with no prefix param, so:

// handleIndex (v1.0)
const prefix = url.searchParams.get("prefix") || (env.DDOC_PREFIX || "2026-09-04") + "/";
// processObject (v1.0)
const prefix = env.DDOC_PREFIX || "2026-09-04";
if (!key.startsWith(prefix + "/")) return { key, skipped: true, reason: "wrong_prefix" };

With DDOC_PREFIX unset, the prefix is the literal string 2026-09-04/. Every run lists only that one key range, and every object uploaded after 2026-09-04 is rejected as wrong_prefix. The worker can never see a newer document — it is structurally incapable of indexing anything, permanently.

Fix

• Prefixes now come from a rolling UTC window (last 7 days) when DDOC_PREFIX is unset.
• rel is derived from the key's own leading YYYY-MM-DD/ segment instead of assuming one pinned prefix.
• An explicit ?prefix= still overrides. Comma-separated DDOC_PREFIX is supported.
• Response now reports scannedPrefixes for diagnosis; /stats reports newest.
• Content-hash dedup in ddocs_index_state is unchanged, so repeat scans of the same window stay cheap.

Deploy note

This is a source fix. It only takes effect on redeploy, and the deploy transport reads a single R2 key (r2:qnfo-canonical/qnfo-ddocs-indexer.js) — the canonical object must be refreshed from this repo before the fix is live. Same transport limitation documented in qnfo-observability/worker.js v1.1.6-single-module.

Verification after deploy

GET /stats   -> indexed > 1 and newest advancing

ddocs_index_state.indexed_at should move past 2026-09-04 on the next cron.

Co-authored-by: Chatbox chatbox@chatboxai.com