Files
0pt/src/http/siax-error-response.ts
T
Simon AxelssonandClaude Sonnet 5 07b13bd833 feat(data-os): Source Registry Postgres persistence + full HTTP route surface
Replaces the in-memory (per-instance, not even per-process-shared) Maps in
SourceService/SourceRegistryService with real Postgres persistence, and adds
the register/query/describe/health/rights/provenance/freshness HTTP routes
that never existed (grep for SourceRegistryService in app/ previously
returned nothing).

- sql/002_source_registry.sql: opt_sources, opt_source_rights,
  opt_source_provenance, opt_source_health_checks, opt_source_freshness.
  Numbered 002 (not 006) because 004's opt_source_rate_policies already
  forward-references opt_sources, which no sql/ file defined until now —
  fixes 004's pre-existing broken migration ordering (opt_datasets remains
  a separate, unrelated, still-open gap in 004, flagged not fixed).
- src/repositories/*: SourceRepository / SourceRegistryRepository seams,
  each with an in-memory implementation (business logic extracted verbatim)
  and a Postgres implementation, chosen via resolveStoreMode — production
  still fails hard with no DATABASE_URL (Master-DoD §3), but a configured
  production now actually works instead of always being blocked.
- SourceService / SourceRegistryService: storage moved behind the
  repository seam; getHealth/getFreshness are now async and tenant-scoped
  at the accessor itself (needed once they're reachable directly over HTTP,
  not only after an earlier caller's tenant check).
- src/services/source-registry.ts: shared singleton instances for the
  sources/* route group, fixing the "each route module owned its own
  private registry" defect (source-rate-policies and .../query previously
  couldn't see a source registered via POST /api/0pt/sources).
- New routes: POST/GET /api/0pt/sources, GET /api/0pt/sources/[id],
  GET+PUT .../rights, GET+PUT .../provenance, GET+POST .../health,
  GET .../freshness.
- Business logic unchanged: fail-closed purpose gate, cross-tenant
  NOT_FOUND (no existence oracle, §50), bounded 100-row health history.

Tested against a real Postgres container (not mocked) —
tests/p0/source-registry-postgres.realinfra.test.ts, env-gated on
SOURCE_REGISTRY_TEST_DATABASE_URL, skips honestly when unset. All 249
pre-existing P0 tests + 7 new realinfra tests pass; also smoke-tested the
full HTTP route surface end-to-end against next dev + live Postgres.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-01 20:42:41 +02:00

26 lines
1.3 KiB
TypeScript

/**
* src/http/siax-error-response.ts
* =================================
* Maps a thrown error to a NextResponse for the source-registry routes
* (app/api/0pt/sources/*). SourceRegistryService throws real `SiaxError`
* instances (src/platform/errors.ts) with a pinned `.httpStatus`/`.code` —
* this honors that mapping directly instead of re-deriving status codes from
* regex-matching `error.message`, the ad-hoc pattern most other 0pt routes
* use (app/api/0pt/documents/[documentId]/extraction/route.ts etc.) because
* their services still throw plain `Error`. SourceService/SourceRegistryService's
* lower-level plain Errors ("already exists", "not found") still fall back
* to that same regex convention here, for consistency with the rest of the
* repo's error surface.
*/
import { NextResponse } from "next/server";
import { SiaxError } from "../platform/errors";
export function siaxErrorResponse(error: unknown): NextResponse {
if (error instanceof SiaxError) {
return NextResponse.json(error.toJSON(), { status: error.httpStatus });
}
const message = error instanceof Error ? error.message : "Unknown error";
const status = /already exists/i.test(message) ? 409 : /not found/i.test(message) ? 404 : 400;
return NextResponse.json({ error: message }, { status });
}