Fix Vercel FastAPI entrypoint

[gitgrahamdunn]

Motivation

• Vercel expects a module that exports a FastAPI instance named app at the project root for serverless functions, and the backend was crashing because no compatible entrypoint was present.
• Provide a minimal shim that re-uses the existing application object without duplicating business logic.

Description

• Add backend/index.py which attempts to import the existing FastAPI app by trying these paths in order: from app.main import app, from main import app, from app.server import app, and from server import app.
• Use importlib.import_module to dynamically load the first successful module and bind its app into this entrypoint.
• If none of the tried module paths resolve, raise a clear ImportError that lists all attempted import targets.
• No business logic, routes, or existing modules were modified; only the minimal entrypoint file was added.

Testing

• Ran backend unit tests with cd backend && pytest -q and all tests passed: 18 passed, 2 warnings.
• Performed a dynamic import validation with Python by importing the new index module and verifying type(index.app) is FastAPI, which succeeded.

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gitplant	Ready	Preview, Comment	Feb 18, 2026 9:42pm
gitplant-backend	Ready	Preview, Comment	Feb 18, 2026 9:42pm
gitplant-oggy	Ready	Preview, Comment	Feb 18, 2026 9:42pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7a94abbd73

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid swallowing import errors from valid app module

The broad except (ImportError, AttributeError) treats any ImportError raised during import_module(_module_path) as a missing module path, so if app.main exists but one of its own imports fails (for example, a missing dependency or typo in app.main), the real exception is suppressed and replaced with the generic "Could not import FastAPI app" error. This makes production failures much harder to diagnose and can also cause the loop to try unintended fallbacks; only missing-target-module cases should be swallowed while other import failures should be re-raised.

Useful? React with 👍 / 👎.