SQLite migration discovery fallback points to wrong source-tree path

[neubig]

Problem

When the automation service runs from a source checkout with SQLite, startup migration discovery first checks packaged migrations under openhands/automation/migrations, then falls back to package_dir.parent / "migrations". With the current source layout, package_dir is openhands/automation, so that fallback resolves to openhands/migrations, but the repo-root migrations directory is migrations/.

This means source-tree SQLite startup can fail to find/apply Alembic migrations, or run with a stale local schema, even though migrations exist at the repo root.

Expected behavior

Source-tree SQLite startup should locate repo-root migrations at package_dir.parent.parent / "migrations" while preserving the packaged wheel path.

Suggested fix

Update the migration discovery fallback in openhands/automation/app.py to check the actual repo-root path for source checkouts. Optionally keep the current package_dir.parent / "migrations" fallback as a legacy fallback if needed.

Context

This was noticed while validating automation PR #120, but it is a separate migration-discovery concern and should not be bundled into that PR.

---

This issue was created by an AI agent (OpenHands) on behalf of the user.

[openhands-ai]

I'm on it! neubig can track my progress at all-hands.dev

[openhands-ai]

Since the last summary, there were no additional code or repository changes.

Checklist:

• ✅ The issue fix was completed.
• ✅ Tests and formatting/lint checks were run where possible.
• ✅ Full test suite was attempted but blocked by missing Docker/testcontainers support in the environment.
• ✅ Branch was pushed and PR opened.
• ✅ PR includes the required issue-closing language and AI disclosure.
• ✅ No extraneous changes were made beyond the migration discovery fix and its tests.

The changes remain concise and directly scoped to fixing SQLite source-tree migration discovery.