test(db): run the MCP and OAuth suites on the real database module

They reset through resetDatabase and seed through the ORM factories
instead of the SQLite snapshot mock, so they run in the Postgres lane as
well. The OAuth service they drove by hand over a second ORM on the
SQLite handle is now the container's own, called in a request context.

The MCP audit cases wait for the mcp.tool_call row: the transport writes
it without awaiting it, so on Postgres it can land after the response.
This commit is contained in:
Maurice
2026-11-17 17:44:13 +01:00
parent 927fcab67f
commit 6e7336b8d7
6 changed files with 215 additions and 264 deletions
@@ -4,12 +4,9 @@
"tests/integration/legacy-upgrade-v205.test.ts",
"tests/integration/legacy-upgrade-v242.test.ts",
"tests/integration/legacy-upgrade-v244.test.ts",
"tests/integration/mcp.test.ts",
"tests/integration/memories-immich.test.ts",
"tests/integration/memories-synology.test.ts",
"tests/integration/memories-unified.test.ts",
"tests/integration/oauth-authorize.test.ts",
"tests/integration/oauth.test.ts",
"tests/integration/scheduler-gate.test.ts",
"tests/integration/security.test.ts",
"tests/integration/settings.test.ts",