feat: API-bound function invocation — REST /fn routes + GraphQL bindings plugin (consolidates #1364 + #1365)

[pyramation]

Summary

Consolidates #1364 (express-context jwt.claims.api_id provenance + REST /fn/:alias routes) and #1365 (graphile plugin exposing API-bound functions as GraphQL mutations) into one branch, then de-duplicates the overlap and makes the whole path scope-aware. Supersedes both PRs.

Both protocols share one binding model end to end: hostname → services_public.domains → api_id → trusted jwt.claims.api_id claim → same function_api_bindings row (protocol enablement in config: { "graphql": true, "rest": { "path", "methods" } }) → plain RLS-enforced INSERT into that scope's function_invocations. No SECURITY DEFINER, no new tables; ajv payload validation intentionally deferred.

Scope-aware module resolution

An API is a global surface; a database may have function modules in multiple scopes, and bindings can live in any of them. The express-context compute loader now returns all function modules for the database (from metaschema_modules_public.function_module + function_invocation_module — no LIMIT 1, no pg_catalog discovery, no hard-coded names):

interface ComputeConfig { modules: ComputeModuleConfig[] }  // was a single module

• REST POST /fn/:alias searches every module's bindings table for (api_id, alias); exactly one match proceeds, zero → 404, cross-scope collision → 409. The INSERT targets the matched module's own invocations table. GET /fn/invocations/:id searches each distinct invocations table.
• The graphile plugin takes a modules: ComputeModuleNames[] array, loads bindings from every scope, and emits one mutation per graphql-enabled binding, inserting into that binding's module invocations table. It emits only mutations — no API→bindings reverse relation is added to the schema.
• Lookups are strict: required loader/plugin options throw when missing; 42P01 on a module's tables is treated as "module not provisioned" (loader returns undefined, routes 404); all other loader errors propagate.

Cleanup on top of the raw merge

• Use existing libraries: inflekt (toCamelCase/toPascalCase/toConstantCase) for mutation/type/enum naming; escapeIdentifier from pg replaces hand-rolled quoting in the plugin and graphql/server/src/middleware/fn.ts.
• Fixture dedup: removed the plugin's private fn_test SQL; plugin tests seed the shared __fixtures__/seed/{services,compute} fixtures (extended for payload_args derivation, JSON-Schema enum/required, JSON fallback, graphql-disabled, other-API filtering, REST enabled/disabled), so REST and GraphQL tests run against identical data including the function_invocations_api_insert WITH CHECK provenance policy.
• Lockfile: regenerated from main, reducing the feat(graphile-function-bindings): expose API-bound functions as GraphQL mutations #1365 churn from ~10k lines to +50.

Testing: targeted builds green; plugin derive + schema tests, express-context (4/4), and graphql/server-test/__tests__/fn-routes.integration.test.ts (7/7) pass locally. One plugin test (resize.invocation sub-select) hits a pre-existing local-env pgSelect failure (reading 'items') that also breaks untouched graphile-test suites locally — relying on CI (which runs the plugin suite in the pg-tests matrix) for that path.

Link to Devin session: https://app.devin.ai/sessions/3ca7b78eeff8401d9108bb174d8eb3eb
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring