Ledger

WEB-033

DB CMS: posts/faqs/media/settings/platforms/status/incidents, publication state machine, revalidation outbox triggers, public api.* readers + pgTAP

← Ledger

donestatus · web-db

1✓ tests passed / failed

4.00Mtokens · 10 min

0evidence files

Evidence

From logs/evidence/WEB-033/. Click a thumbnail for the full image.

No evidence files in logs/evidence/WEB-033/.

Tests

pass pgTAP all (55): + CMS visibility, state machine, settings validation, outbox delivery · 117.8 s · raw log$ node packages/db/scripts/sb.mjs db reset && pnpm db:test

Notes

2026-10-04 14:23 UTC · Migration 20261004140400_cms: posts (news/devlog/patch_notes/event/legal, slug rules, cover media, release_version), faqs, media_assets, site_settings singleton (stage, primary CTA, https-only socials allow-list, steam, maintenance, banner, route flags incl. roadmap/events/systemRequirements/accounts/rankings, servers_live, signups_open), platform_availability (4 × in_development), service_status (website, accounts + game servers not_launched), incidents + updates, revalidation_outbox with trigger-based tag queueing (posts/faqs/media only when public/scheduled — bug found by the test: status tables also have a 'state' column), transition_post state machine (reason for publishing), settings/platform/status/incident RPCs (reason + audit), claim/ack outbox (staff or job_worker via JWT role), api readers (site_settings, list_posts, get_post, list_faqs, list_media, status_overview). pgTAP 050_cms 17 checks.