rayfin up silently skips schema changes

Problem statement

rayfin up deploys code but does not apply entity schema changes. Those require the separate rayfin up db apply. Nothing warns you when the entity definitions have drifted from the deployed schema, so a deploy appears to succeed while the new entity does not exist, and the failure only shows up at runtime as a query error.

Evidence. Adding the AppAdmin entity required npx rayfin up db apply --yes before npx rayfin up --yes. Running only the latter produced a clean success with an app that could not read the new entity.

Impact. A silent, deferred failure. In CI this ships a broken build with a green light.

Proposed solution

Compare the local entity definitions against the deployed schema during rayfin up and either apply automatically, prompt, or fail with a clear instruction. At minimum, print a warning naming the drifted entities. A rayfin up --with-db convenience flag would also remove the ordering trap.

Alternatives considered

No response

Additional context

No response

Start with the rayfin up and rayfin up db apply entry points, reproducing the AppAdmin example with the commands in the issue. Trace how local entity definitions and the deployed schema are handled; done should be a defined warning, prompt, automatic apply, or failure that prevents silent drift and names the affected entities.