fix: keep historical work stable across metadata changes

[f0rr0]

Old work could reappear as a new daily entry when the repository advanced: its fingerprint included the current branch head, and publication replaced its source date with the publication time.

Fingerprint owned work independently of mutable branch heads and PR metadata, and publish using the original activity date and time. Actual commit, fact, and outcome changes still update work; existing closed-day snapshots stay frozen. Remove the redundant projection fields.

The cleanup migration was generated with bun run db:generate --custom, including its filename, journal entry, and schema snapshot. It removes later canonical copies only when an identical original snapshot exists on the actual work day. The history guard is suspended and restored inside the migration transaction so the repair also works after the duplicate day closes. A read-only production check matched one erroneous row.

Validation:

• 291 tests, typecheck, lint, and both Knip modes pass. A targeted replay of the affected historical record reproduced the old fingerprint churn and confirmed stable fingerprints with unchanged display facts after the fix.
• Applied all 26 migrations to an empty PostgreSQL 17 database using bun run db:migrate; rerunning changed nothing. Drizzle consistency checks pass and generation reports no schema drift.
• Tested an existing-data upgrade with the duplicate day closed: only the duplicate was removed, original and differing facts survived, and history protection was restored. Both Drizzle and direct cleanup reruns were unchanged.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
f0rr0-github-io	Ready	Preview	Sep 28, 2026 1:41pm UTC