Follow-up to #17. The tables landed with that promotion, but the endpoint still answered 500 because the model barrel resolved Subscriber to the framework's definition, which carries no query methods, while User resolved to the app's.
TypeError: Subscriber.where is not a function6f5a6e1 publishes both subscriber models into app/Models, so the barrel resolves them the same way it resolves User. No migration: 0000000025 already created both tables and the box has them, with the ledger recording it.
CI green on 6f5a6e1. The deployment smoke asserts the subscribe endpoint, so this deploy proves the fix or fails.