Wiki state and quota enforcement wait for the next poll instead of reacting to the change #45
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#45
Reference in New Issue
Block a user
What a person cannot do today
See a change made on the wiki farm reflected in the console, or have a downgrade's read-only parking take effect, without waiting for the next tick of the periodic sync. The state projection and the quota reconcile both ride that sync, so enforcement is eventually consistent by construction. The test stack shortens the interval rather than closing the gap.
What they should be able to do
Have the farm report a change as it happens (site created, status changed, deleted, usage threshold crossed) and have the console project it on arrival, with the periodic sync left as a slow safety net.
Why it matters
A member who downgrades keeps more than they are entitled to until the next tick, an out-of-band change on the farm leaves the console showing something no longer true, and the retention purge runs late for the same reason.
Where
The sync workflow in the wiki integration and the inbound webhook events table, which already exists and is already idempotent.
Done when
The farm plugin posts change events, a processor projects them immediately, and the periodic sync becomes a reconcile that expects to find nothing. The immediate per-trigger reconcile from the upgrade and downgrade paths lands with it. Blocked upstream: change webhooks are the one capability of the set requested from the farm plugin that has not shipped.
Migrated from status/issues.md at
b7a0e15