Lumen upgrade rollback lacks automatic migration detection

Lumen's upgrade routine does not automatically detect partially applied migrations, leaving developers to decide whether to re‑run pending migrations or keep the existing database state. The framework provides no built‑in command to revert the migration stack, so rollback relies on manually restoring composer.lock and reinstalling vendor files, which may reinstall outdated packages. Additionally, clearing the bootstrap cache after a failed upgrade can reintroduce stale configuration if the cache predates the upgrade, and changes to service provider registration in Lumen 9 may conflict with older bootstrapping code, creating uncertainty about runtime behavior.

Which migration entries can be safely re‑executed without risking duplicate tables? How can developers verify that the bootstrap cache reflects the current codebase before rollback? What precautions prevent service provider conflicts when restoring composer.lock after an upgrade failure?