The core database seeds a resource key that belongs to the wiki integration #46

New Issue

2026-09-21T07:18:14Z

cgalo5758 commented

2026-09-21 07:18:14 +00:00

What a contributor runs into

Each module owns its own migration stream, and an integration's rows belong to that integration's stream. The wiki site key (fedwiki_sites, the resource an entitlement rule puts a limit on) is seeded by a core migration instead, and every later core migration that touches it follows from that seed: one sets its kind, one changes the name it displays, one backfills its rules with a reduction policy so the quota sweep keeps behaving across an upgrade. The other integrations do not do this: the Discourse key is inserted and then corrected by the Discourse store's own stream, and the domains module seeds its own key. Core mentions Discourse only in a comment.

Why it costs

Core's schema names an integration a deployment may not run, so the boundary the codebase teaches is not the boundary it keeps. A contributor reading core's migrations learns the wrong rule about where an integration's rows live, and the integration cannot be removed or replaced without a core migration.

Where

The core store's resource-key seed and the three later core migrations that amend that key; the wiki store's own migration stream; the wiki sites spec, whose requirement names the migration that adds a column rather than stating who owns the key; and the test that pins the policy backfill.

Done when

The wiki store's baseline seeds its own key with its kind and its display name, core's seed keeps only the platform's keys, and the policy backfill disappears rather than moves, because a fresh install has no rules that predate the policy and the one deployment that does already carries the value in its data. The spec requirement is rewritten as a statement about key ownership, the test that pins the backfill goes, and nothing in tests, docs or the demo data refers to a migration by number. The vehicle is the squash that re-baselines one stream per module before launch; an interim migration ahead of it would only be replaced by it.

Migrated from status/issues.md at b7a0e15

## What a contributor runs into Each module owns its own migration stream, and an integration's rows belong to that integration's stream. The wiki site key (`fedwiki_sites`, the resource an entitlement rule puts a limit on) is seeded by a core migration instead, and every later core migration that touches it follows from that seed: one sets its kind, one changes the name it displays, one backfills its rules with a reduction policy so the quota sweep keeps behaving across an upgrade. The other integrations do not do this: the Discourse key is inserted and then corrected by the Discourse store's own stream, and the domains module seeds its own key. Core mentions Discourse only in a comment. ## Why it costs Core's schema names an integration a deployment may not run, so the boundary the codebase teaches is not the boundary it keeps. A contributor reading core's migrations learns the wrong rule about where an integration's rows live, and the integration cannot be removed or replaced without a core migration. ## Where The core store's resource-key seed and the three later core migrations that amend that key; the wiki store's own migration stream; the wiki sites spec, whose requirement names the migration that adds a column rather than stating who owns the key; and the test that pins the policy backfill. ## Done when The wiki store's baseline seeds its own key with its kind and its display name, core's seed keeps only the platform's keys, and the policy backfill disappears rather than moves, because a fresh install has no rules that predate the policy and the one deployment that does already carries the value in its data. The spec requirement is rewritten as a statement about key ownership, the test that pins the backfill goes, and nothing in tests, docs or the demo data refers to a migration by number. The vehicle is the squash that re-baselines one stream per module before launch; an interim migration ahead of it would only be replaced by it. Migrated from status/issues.md at b7a0e15

cgalo5758 added this to the Public launch milestone 2026-09-21 07:18:14 +00:00

cgalo5758 added the

kind

debt

area/entitlements area/fedwiki area/ops labels 2026-09-21 07:18:14 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#46