Follow-up to #3801, which removed the AI-analysis feature but deliberately left the schema alone.
policyengine_api/data/v1_models.py still defines Analysis (__tablename__ = "analysis") and the table still exists in Cloud SQL, with no remaining reader or writer. Drop it the repo way: remove the model, then uv run alembic -c alembic-v1.ini revision --autogenerate -m "drop orphaned analysis table" against a live MySQL (the Alembic v1 qualification job), with upgrade/downgrade covered as in 01e49b3a056e (the orphaned question table precedent).
Follow-up to #3801, which removed the AI-analysis feature but deliberately left the schema alone.
policyengine_api/data/v1_models.pystill definesAnalysis(__tablename__ = "analysis") and the table still exists in Cloud SQL, with no remaining reader or writer. Drop it the repo way: remove the model, thenuv run alembic -c alembic-v1.ini revision --autogenerate -m "drop orphaned analysis table"against a live MySQL (the Alembic v1 qualification job), with upgrade/downgrade covered as in 01e49b3a056e (the orphanedquestiontable precedent).