docs: bring every markdown file up to date with the code
The docs had drifted in ways that would mislead: DATA-MODEL documented a localStorage shape the code stopped using (completedAt, no ignored store), INGESTION claimed three Game8 templates when five are known, ARCHITECTURE still listed the whole client and time.ts as unbuilt, and the review-quarantine skill described a pipeline that does not exist yet without saying so. Adds the parser roster and the six date formats as tables, documents the subpath/base-href and offline behaviour, and records the new product surface (first-run picker, ignore, offline, credit) as PRD features. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
co-authored by
Claude Opus 5
parent
f2cf9ba0cb
commit
692b5a83d5
@@ -5,6 +5,11 @@ description: Work through the quarantined-event queue — triage held events by
|
||||
|
||||
# Reviewing the quarantine queue
|
||||
|
||||
> **Not built yet.** The quarantine table, the `/review` route and the ingest scheduler are specified
|
||||
> in `docs/INGESTION.md` but do not exist in the tree. Today the closest equivalent is the conflict
|
||||
> list `bun run build:feed` prints when two sources disagree. Use this skill once the pipeline lands;
|
||||
> until then, treat it as the spec for what that review flow should do.
|
||||
|
||||
Held events are candidates the pipeline declined to publish. Working the queue is both a data task
|
||||
(get these events onto the calendar) and a diagnostic one (**a growing queue means something
|
||||
upstream broke**).
|
||||
|
||||
Reference in New Issue
Block a user