release: promote v0.8.0 optional backfill times to production #9

Merged
Grok merged 4 commits from dev into main 2026-11-06 02:19:00 +00:00
Member

Promote preview-verified #8 (optional published_at/created_at/run times, additive migration, VERSION 0.8.0) from dev to main.

Preview checks (Nov 5 2026 evening America/Los_Angeles): health OK; VERSION 0.8.0; omit→current LA edition; published_at=2026-10-23→that edition; naive DT→422; dedupe preserves published_at; migrate idempotent; preview ntfy left disabled/unchanged. Production notifications left unchanged per Brandon.

Authorized: Brandon Ops chat Nov 5 18:13 PST.

Promote preview-verified #8 (optional published_at/created_at/run times, additive migration, VERSION 0.8.0) from dev to main. Preview checks (Nov 5 2026 evening America/Los_Angeles): health OK; VERSION 0.8.0; omit→current LA edition; published_at=2026-10-23→that edition; naive DT→422; dedupe preserves published_at; migrate idempotent; preview ntfy left disabled/unchanged. Production notifications left unchanged per Brandon. Authorized: Brandon Ops chat Nov 5 18:13 PST.
ingest_post (MCP and the /api/internal/ingest fallback) takes an
optional published_at. add_comment takes an optional created_at, and
record_ingest_run takes optional started_at and finished_at. When the
new fields are omitted, behavior is unchanged: every time is the
server's write time.

Accepted values: YYYY-MM-DD, read as 00:00 on that date in
America/Los_Angeles, or an ISO 8601 date-time with Z or a UTC offset.
Midnight exists on every Los Angeles date (DST switches at 02:00), so
a date-only value is never ambiguous. A date-time without an offset is
rejected rather than guessed: in America/Los_Angeles the 01:00-02:00
hour on the fall-back date happens twice and the 02:00-03:00 hour on
the spring-forward date never happens. Stored values are UTC
YYYY-MM-DDTHH:MM:SSZ with fractional seconds truncated, the same shape
as server times, so text order stays chronological order.

Bounds: no earlier than 2026-09-17 00:00 America/Los_Angeles, the date
the service contract was locked, since no edition can predate the
service; no later than now plus 5 minutes, which absorbs caller clock
drift. A date-only value for today's Los Angeles date is accepted and
tomorrow's is rejected. A comment may not be timed before its post's
published_at, because archive "last update" assumes a comment is never
older than its post. started_at may not follow finished_at; when only
one is sent, both take that value (v1 rows already had the two equal).

Storage: posts gain published_at. Edition grouping, the most recent
edition date, archive from/to, archive and edition sort,
list_recent_posts, and the post and archive pages now read
published_at instead of ingested_at. ingested_at stays the true server
write time. Comments and ingest_runs gain recorded_at for the true
write time while created_at / started_at / finished_at carry the
supplied time. migrate() runs at connect inside BEGIN IMMEDIATE. It
adds the columns when they are missing, fills them from the column
that held the same instant (published_at from ingested_at, recorded_at
from created_at or finished_at), and creates idx_posts_published_at.
Existing rows keep their edition date and their order. The migration
only adds data and can run any number of times.

Dedupe never rewrites a stored row, so a duplicate ingest_post returns
the stored published_at and ignores the supplied one. Responses now
include published_at (ingest_post, posts, archive, list_recent_posts),
created_at (add_comment), and started_at / finished_at
(record_ingest_run).

/api/internal/ingest used to return 500 on a payload that failed
validation. It now returns 422 with "field: reason" and does not echo
the input. MCP keeps its invalid_argument shape.

ntfy is unchanged. It still keys its quiet clock, burst, and labels on
ingested_at, so a backfill burst with ntfy enabled sends one notice
labeled with the backfill day.

Rejected alternatives:
- Overwriting ingested_at with the supplied time. That loses the real
  write time and would make ntfy treat backfilled rows as long quiet.
- Reading naive date-times as Los Angeles time. That is ambiguous
  across DST.
- Noon for date-only values. Midnight is the edition-day start and is
  always unambiguous.
- An open lower bound. That allows typo years like 2016.

Version 0.8.0.
The README MCP section gets a Backfill times table covering
published_at, created_at, and started_at / finished_at. It gives the
accepted formats, the America/Los_Angeles reading of date-only values,
the bounds, the separate server write times, the dedupe rule, and the
422 REST error shape. design.md is not edited. The schema and edition
definitions in design.md 4.1-4.4 and 4.8 need a docs-owner update to
name published_at and recorded_at.
Brandon confirmed the new time fields are optional and an omitted one
means the current day. This pins that down: with the server clock at
2026-11-06T01:30:00Z (17:30 PST on Nov 5), a post, comment, and run
filed without times store that instant and appear in the 2026-11-05
edition, not the UTC date 2026-11-06. No application change was needed;
edition dates already convert stored UTC to America/Los_Angeles.
Grok merged commit f6613452fc into main 2026-11-06 02:19:00 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ai-collab/agent-news-aggregator!9
No description provided.