@entifix/service-shell 0.1.0-0

package/dist/auth/require-service-crossing.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/auth/require-service-crossing.ts"],"sourcesContent":["import { timingSafeEqual } from 'node:crypto';\n\nimport { HttpServerRequest, HttpServerResponse } from '@effect/platform';\nimport { type Permission, ServiceCrossingPolicyTag } from '@entifix/authz';\nimport { Context, Effect } from 'effect';\n\n/**\n * The header carrying the crossing secret.\n *\n * ⚠️ **Deliberately not `x-service-token`.** That header is config-service's\n * fleet lookup, and the two secrets are not comparable: one grants a\n * configuration *read*, this one a tenant-data *write* for any organization the\n * caller names. Sharing the header name is how a proxy configured to forward the\n * fleet token ends up presenting it to a route that writes stock, and how a\n * copy-pasted value looks right while being the wrong secret entirely\n * ([ADR 0023](../../../../../../docs/adr/0023-service-to-service-tenant-crossing.md)).\n */\nexport const CROSSING_TOKEN_HEADER = 'x-crossing-token';\n\n/**\n * The header naming the organization the caller is acting for.\n *\n * It rides beside the token rather than inside the request body because\n * entities are organization-agnostic by rule — no `organizationId` member, no\n * tenant filter — so there is nowhere in an entity envelope for it to live. A\n * header also serves the crossings that carry no body at all (releasing a hold,\n * converting one), which a body field would have needed a second convention for.\n *\n * On its own it grants **nothing**: it is only read after the token has proved\n * the caller is the fleet, so the input the caller controls is never the input\n * that authorizes.\n */\nexport const ORGANIZATION_HEADER = 'x-organization-id';\n\n/**\n * The crossing secret this service expects, provided at the composition root\n * from its own configuration.\n *\n * A `Context.Tag` rather than an environment read, which is the difference from\n * {@link requireServiceToken}: the value is a per-service secret held in\n * config-service as an `is_secret` row, so it arrives through the same boot\n * fetch as `mongo.uri` and can be rotated without redeploying a container.\n */\nexport class ServiceCrossingTokenTag extends Context.Tag(\n  'ServiceCrossingTokenTag',\n)<ServiceCrossingTokenTag, string>() {}\n\n/** Constant-time comparison, so the secret cannot be recovered byte by byte. */\nconst matches = (provided: string | undefined, expected: string): boolean => {\n  if (provided === undefined) return false;\n  const left = Buffer.from(provided);\n  const right = Buffer.from(expected);\n  // `timingSafeEqual` throws on a length mismatch, so lengths are compared\n  // first — the length of a shared secret is not what protects it.\n  return left.length === right.length && timingSafeEqual(left, right);\n};\n\nconst unauthenticated = HttpServerResponse.json(\n  { error: 'unauthenticated', code: 'unauthenticated' },\n  { status: 401 },\n);\n\nconst forbidden = (permission: Permission) =>\n  HttpServerResponse.json(\n    { error: 'forbidden', code: 'forbidden', permission },\n    { status: 403 },\n  );\n\nconst organizationRequired = HttpServerResponse.json(\n  {\n    error: 'the crossing must name an organization',\n    code: 'invalidRequest',\n    detail: `${ORGANIZATION_HEADER} is required`,\n  },\n  { status: 400 },\n);\n\n/**\n * Guard a **service-to-service** tenant crossing: the second — and only other —\n * way a request resolves the organization it acts for.\n *\n * The first is {@link requireOrganization}, which reads the session's\n * `activeOrganizationId` and is the only *user-facing* resolution. This one\n * exists because a platform-plane caller sometimes acts for an organization the\n * principal is not a member of: checkout reserving a vendor's stock, where the\n * organization comes from the **item** and a buyer's session carries none — and\n * never will, since making a buyer a member of every vendor they buy from would\n * be a far worse breach than the problem it solved.\n *\n * There is no third path, no fallback and no operator branch. A request\n * satisfying neither guard simply never reaches a tenant handle\n * ([ADR 0023](../../../../../../docs/adr/0023-service-to-service-tenant-crossing.md);\n * ADR 0012's operator crossing is a *different* mechanism — a person choosing an\n * organization, which needs a human's permission, a time box and a `Crossing`\n * record).\n *\n * ⚠️ **This guard reads no cookie and no `Authorization` header, and that is\n * the design.** A route guarded here accepts the crossing token and nothing\n * else: two accepted credentials on one route means the weaker one is the\n * security level. It matters concretely — `super-admin` holds `*:*:*`, which\n * matches every crossing permission, so a route that also took a session would\n * be reachable by an operator's browser tab.\n *\n * Three checks, in this order, so nothing is revealed before fleet membership is\n * proven:\n *\n * 1. the token, compared in constant time → `401`;\n * 2. the permission, against `ServiceCrossingPolicyTag` → `403`. The token\n *    proves the caller is the fleet; it does not say what the caller may do, and\n *    fleet membership is not a capability;\n * 3. the organization header, non-blank → `400`.\n *\n * **The recorded residual** (ADR 0023, not argued away here): a shared secret\n * means any process holding it can name any organization. What bounds it is the\n * permission above, the fact that only the slices needing it are configured with\n * the key, and the request log. What would remove it is an RS256 service token\n * carrying a scope claim, which is named work rather than a gap nobody noticed.\n */\nexport const requireServiceCrossing =\n  (permission: Permission) =>\n  <A, E, R>(use: (organizationId: string) => Effect.Effect<A, E, R>) =>\n    // The return type is inferred rather than written out, for the reason\n    // `requireServiceToken` records: `HttpServerResponse.json` contributes an\n    // `HttpBodyError` to the failure channel, and spelling the type out while\n    // omitting it is what makes the declaration emit fail invisibly.\n    Effect.gen(function* () {\n      const request = yield* HttpServerRequest.HttpServerRequest;\n      const expected = yield* ServiceCrossingTokenTag;\n\n      if (!matches(request.headers[CROSSING_TOKEN_HEADER], expected)) {\n        return yield* unauthenticated;\n      }\n\n      const crossing = yield* ServiceCrossingPolicyTag;\n      if (!crossing.allows(permission)) {\n        return yield* forbidden(permission);\n      }\n\n      const organizationId = request.headers[ORGANIZATION_HEADER]?.trim();\n      if (organizationId === undefined || organizationId === '') {\n        return yield* organizationRequired;\n      }\n\n      return yield* use(organizationId);\n    });\n\n/**\n * The same fleet check, for a participant that has **no organization to name**.\n *\n * ⚠️ **A platform-plane store is the whole difference.** `requireServiceCrossing`\n * above ends with an organization header because it is about to resolve a tenant\n * database handle from it, and a blank one there would read some other vendor's\n * storage. order-service names one database at boot, so there is no handle to\n * choose — and demanding a header nothing consumes would be theatre that a\n * caller learns to satisfy with any value.\n *\n * What is unchanged, and is the part that matters: the token proves the caller\n * is the fleet, the host's `ServiceCrossingPolicy` says what the fleet may do,\n * and **no session is accepted**. A saga step is not a person's act — the buyer\n * behind a checkout holds no grant over the order the coordinator is writing on\n * their behalf, and accepting their session here would make the weaker\n * credential the security level ([ADR 0052](../../../../../../docs/adr/0052-the-checkout-saga.md)).\n *\n * The recorded residual carries over verbatim: a shared secret means any process\n * holding it can act, bounded by the permission and by which slices are\n * configured with the key.\n */\nexport const requireCrossing =\n  (permission: Permission) =>\n  <A, E, R>(route: Effect.Effect<A, E, R>) =>\n    Effect.gen(function* () {\n      const request = yield* HttpServerRequest.HttpServerRequest;\n      const expected = yield* ServiceCrossingTokenTag;\n\n      if (!matches(request.headers[CROSSING_TOKEN_HEADER], expected)) {\n        return yield* unauthenticated;\n      }\n\n      const crossing = yield* ServiceCrossingPolicyTag;\n      if (!crossing.allows(permission)) {\n        return yield* forbidden(permission);\n      }\n\n      return yield* route;\n    });\n"],"names":["timingSafeEqual","HttpServerRequest","HttpServerResponse","ServiceCrossingPolicyTag","Context","Effect","CROSSING_TOKEN_HEADER","ORGANIZATION_HEADER","ServiceCrossingTokenTag","Tag","matches","provided","expected","undefined","left","Buffer","from","right","length","unauthenticated","json","error","code","status","forbidden","permission","organizationRequired","detail","requireServiceCrossing","use","gen","request","headers","crossing","allows","organizationId","trim","requireCrossing","route"],"mappings":"AAAA,SAASA,eAAe,QAAQ,cAAc;AAE9C,SAASC,iBAAiB,EAAEC,kBAAkB,QAAQ,mBAAmB;AACzE,SAA0BC,wBAAwB,QAAQ,iBAAiB;AAC3E,SAASC,OAAO,EAAEC,MAAM,QAAQ,SAAS;AAEzC;;;;;;;;;;CAUC,GACD,OAAO,MAAMC,wBAAwB,mBAAmB;AAExD;;;;;;;;;;;;CAYC,GACD,OAAO,MAAMC,sBAAsB,oBAAoB;AAEvD;;;;;;;;CAQC,GACD,OAAO,MAAMC,gCAAgCJ,QAAQK,GAAG,CACtD;AACoC;AAEtC,8EAA8E,GAC9E,MAAMC,UAAU,CAACC,UAA8BC;IAC7C,IAAID,aAAaE,WAAW,OAAO;IACnC,MAAMC,OAAOC,OAAOC,IAAI,CAACL;IACzB,MAAMM,QAAQF,OAAOC,IAAI,CAACJ;IAC1B,yEAAyE;IACzE,iEAAiE;IACjE,OAAOE,KAAKI,MAAM,KAAKD,MAAMC,MAAM,IAAIlB,gBAAgBc,MAAMG;AAC/D;AAEA,MAAME,kBAAkBjB,mBAAmBkB,IAAI,CAC7C;IAAEC,OAAO;IAAmBC,MAAM;AAAkB,GACpD;IAAEC,QAAQ;AAAI;AAGhB,MAAMC,YAAY,CAACC,aACjBvB,mBAAmBkB,IAAI,CACrB;QAAEC,OAAO;QAAaC,MAAM;QAAaG;IAAW,GACpD;QAAEF,QAAQ;IAAI;AAGlB,MAAMG,uBAAuBxB,mBAAmBkB,IAAI,CAClD;IACEC,OAAO;IACPC,MAAM;IACNK,QAAQ,GAAGpB,oBAAoB,YAAY,CAAC;AAC9C,GACA;IAAEgB,QAAQ;AAAI;AAGhB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwCC,GACD,OAAO,MAAMK,yBACX,CAACH,aACD,CAAUI,MACR,sEAAsE;QACtE,0EAA0E;QAC1E,0EAA0E;QAC1E,iEAAiE;QACjExB,OAAOyB,GAAG,CAAC;gBAacC;YAZvB,MAAMA,UAAU,OAAO9B,kBAAkBA,iBAAiB;YAC1D,MAAMW,WAAW,OAAOJ;YAExB,IAAI,CAACE,QAAQqB,QAAQC,OAAO,CAAC1B,sBAAsB,EAAEM,WAAW;gBAC9D,OAAO,OAAOO;YAChB;YAEA,MAAMc,WAAW,OAAO9B;YACxB,IAAI,CAAC8B,SAASC,MAAM,CAACT,aAAa;gBAChC,OAAO,OAAOD,UAAUC;YAC1B;YAEA,MAAMU,kBAAiBJ,uCAAAA,QAAQC,OAAO,CAACzB,oBAAoB,qBAApCwB,qCAAsCK,IAAI;YACjE,IAAID,mBAAmBtB,aAAasB,mBAAmB,IAAI;gBACzD,OAAO,OAAOT;YAChB;YAEA,OAAO,OAAOG,IAAIM;QACpB,GAAG;AAEP;;;;;;;;;;;;;;;;;;;;CAoBC,GACD,OAAO,MAAME,kBACX,CAACZ,aACD,CAAUa,QACRjC,OAAOyB,GAAG,CAAC;YACT,MAAMC,UAAU,OAAO9B,kBAAkBA,iBAAiB;YAC1D,MAAMW,WAAW,OAAOJ;YAExB,IAAI,CAACE,QAAQqB,QAAQC,OAAO,CAAC1B,sBAAsB,EAAEM,WAAW;gBAC9D,OAAO,OAAOO;YAChB;YAEA,MAAMc,WAAW,OAAO9B;YACxB,IAAI,CAAC8B,SAASC,MAAM,CAACT,aAAa;gBAChC,OAAO,OAAOD,UAAUC;YAC1B;YAEA,OAAO,OAAOa;QAChB,GAAG"}

package/dist/auth/service-token.d.ts

@@ -0,0 +1,37 @@
+import { HttpServerRequest, HttpServerResponse } from '@effect/platform';
+import { Effect } from 'effect';
+/** The header a caller of config-service's fleet lookup presents. */
+export declare const SERVICE_TOKEN_HEADER = "x-service-token";
+/**
+ * Local-dev default, so `pnpm run back-office:dev` stays zero-config. Same
+ * convention as the seeded `jwt.secret`: obviously a placeholder, replaced per
+ * environment through `CONFIG_SERVICE_TOKEN`.
+ */
+export declare const DEV_SERVICE_TOKEN = "dev-config-service-token-change-me";
+/**
+ * The expected token, read from the environment on each call rather than captured
+ * at module load — so a test can set it without re-importing the module.
+ */
+export declare const serviceToken: () => string;
+/**
+ * Guards config-service's fleet configuration lookup.
+ *
+ * `GET /api/config/:service` hands out `jwt.secret`, `mongo.uri`, `redis.uri` and
+ * `rabbitmq.uri` in plaintext, because that is exactly what a booting service
+ * needs — the values cannot be redacted here without breaking the boot the route
+ * exists to serve. So the route is gated on a shared token instead, which closes
+ * the drive-by read that being merely "cluster-internal" did not.
+ *
+ * This is deliberately **not** service identity: every caller presents the same
+ * token, so it proves fleet membership and nothing more. Per-service credentials,
+ * with the response scoped to the service that asked, are separate work; this is
+ * the cheap step that stops the port from being self-serve.
+ *
+ * It lives here beside {@link loadRemoteConfiguration}, the client half of the
+ * same protocol, so the header and the token cannot drift apart.
+ *
+ * Health endpoints are **not** guarded — a probe must answer without credentials,
+ * or a readiness check becomes an authentication problem.
+ */
+export declare const requireServiceToken: <A, E, R>(route: Effect.Effect<A, E, R>) => Effect.Effect<HttpServerResponse.HttpServerResponse | A, import("@effect/platform/HttpBody").HttpBodyError | E, HttpServerRequest.HttpServerRequest | R>;
+//# sourceMappingURL=service-token.d.ts.map

package/dist/auth/service-token.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"service-token.d.ts","sourceRoot":"","sources":["../../src/auth/service-token.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,iBAAiB,EAAE,kBAAkB,EAAE,MAAM,kBAAkB,CAAC;AACzE,OAAO,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AAEhC,qEAAqE;AACrE,eAAO,MAAM,oBAAoB,oBAAoB,CAAC;AAEtD;;;;GAIG;AACH,eAAO,MAAM,iBAAiB,uCAAuC,CAAC;AAEtE;;;GAGG;AACH,eAAO,MAAM,YAAY,QAAO,MACuB,CAAC;AAYxD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,mBAAmB,GAAI,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,OAAO,MAAM,CAAC,MAAM,CAAC,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC,6JAiBtE,CAAC"}

package/dist/auth/service-token.js

@@ -0,0 +1,62 @@
+import { timingSafeEqual } from 'node:crypto';
+import { HttpServerRequest, HttpServerResponse } from '@effect/platform';
+import { Effect } from 'effect';
+/** The header a caller of config-service's fleet lookup presents. */ export const SERVICE_TOKEN_HEADER = 'x-service-token';
+/**
+ * Local-dev default, so `pnpm run back-office:dev` stays zero-config. Same
+ * convention as the seeded `jwt.secret`: obviously a placeholder, replaced per
+ * environment through `CONFIG_SERVICE_TOKEN`.
+ */ export const DEV_SERVICE_TOKEN = 'dev-config-service-token-change-me';
+/**
+ * The expected token, read from the environment on each call rather than captured
+ * at module load — so a test can set it without re-importing the module.
+ */ export const serviceToken = ()=>{
+    var _process_env_CONFIG_SERVICE_TOKEN;
+    return (_process_env_CONFIG_SERVICE_TOKEN = process.env.CONFIG_SERVICE_TOKEN) != null ? _process_env_CONFIG_SERVICE_TOKEN : DEV_SERVICE_TOKEN;
+};
+/** Constant-time comparison, so the token cannot be recovered byte by byte. */ const matches = (provided)=>{
+    if (provided === undefined) return false;
+    const left = Buffer.from(provided);
+    const right = Buffer.from(serviceToken());
+    // `timingSafeEqual` throws on a length mismatch, so the lengths are compared
+    // first — the length of a shared secret is not what protects it.
+    return left.length === right.length && timingSafeEqual(left, right);
+};
+/**
+ * Guards config-service's fleet configuration lookup.
+ *
+ * `GET /api/config/:service` hands out `jwt.secret`, `mongo.uri`, `redis.uri` and
+ * `rabbitmq.uri` in plaintext, because that is exactly what a booting service
+ * needs — the values cannot be redacted here without breaking the boot the route
+ * exists to serve. So the route is gated on a shared token instead, which closes
+ * the drive-by read that being merely "cluster-internal" did not.
+ *
+ * This is deliberately **not** service identity: every caller presents the same
+ * token, so it proves fleet membership and nothing more. Per-service credentials,
+ * with the response scoped to the service that asked, are separate work; this is
+ * the cheap step that stops the port from being self-serve.
+ *
+ * It lives here beside {@link loadRemoteConfiguration}, the client half of the
+ * same protocol, so the header and the token cannot drift apart.
+ *
+ * Health endpoints are **not** guarded — a probe must answer without credentials,
+ * or a readiness check becomes an authentication problem.
+ */ export const requireServiceToken = (route)=>// The return type is inferred rather than written out: `HttpServerResponse.json`
+    // contributes an `HttpBodyError` to the failure channel, and spelling the type
+    // out while omitting it is what makes `tsc` refuse the declaration emit — which
+    // `@nx/js:swc` hides, leaving a green build with no `.d.ts` and a TS6305
+    // cascade in every consumer. `requirePrincipal` infers for the same reason.
+    Effect.gen(function*() {
+        const request = yield* HttpServerRequest.HttpServerRequest;
+        if (!matches(request.headers[SERVICE_TOKEN_HEADER])) {
+            return yield* HttpServerResponse.json({
+                error: 'unauthenticated',
+                code: 'unauthenticated'
+            }, {
+                status: 401
+            });
+        }
+        return yield* route;
+    });
+
+//# sourceMappingURL=service-token.js.map

package/dist/auth/service-token.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/auth/service-token.ts"],"sourcesContent":["import { timingSafeEqual } from 'node:crypto';\n\nimport { HttpServerRequest, HttpServerResponse } from '@effect/platform';\nimport { Effect } from 'effect';\n\n/** The header a caller of config-service's fleet lookup presents. */\nexport const SERVICE_TOKEN_HEADER = 'x-service-token';\n\n/**\n * Local-dev default, so `pnpm run back-office:dev` stays zero-config. Same\n * convention as the seeded `jwt.secret`: obviously a placeholder, replaced per\n * environment through `CONFIG_SERVICE_TOKEN`.\n */\nexport const DEV_SERVICE_TOKEN = 'dev-config-service-token-change-me';\n\n/**\n * The expected token, read from the environment on each call rather than captured\n * at module load — so a test can set it without re-importing the module.\n */\nexport const serviceToken = (): string =>\n  process.env.CONFIG_SERVICE_TOKEN ?? DEV_SERVICE_TOKEN;\n\n/** Constant-time comparison, so the token cannot be recovered byte by byte. */\nconst matches = (provided: string | undefined): boolean => {\n  if (provided === undefined) return false;\n  const left = Buffer.from(provided);\n  const right = Buffer.from(serviceToken());\n  // `timingSafeEqual` throws on a length mismatch, so the lengths are compared\n  // first — the length of a shared secret is not what protects it.\n  return left.length === right.length && timingSafeEqual(left, right);\n};\n\n/**\n * Guards config-service's fleet configuration lookup.\n *\n * `GET /api/config/:service` hands out `jwt.secret`, `mongo.uri`, `redis.uri` and\n * `rabbitmq.uri` in plaintext, because that is exactly what a booting service\n * needs — the values cannot be redacted here without breaking the boot the route\n * exists to serve. So the route is gated on a shared token instead, which closes\n * the drive-by read that being merely \"cluster-internal\" did not.\n *\n * This is deliberately **not** service identity: every caller presents the same\n * token, so it proves fleet membership and nothing more. Per-service credentials,\n * with the response scoped to the service that asked, are separate work; this is\n * the cheap step that stops the port from being self-serve.\n *\n * It lives here beside {@link loadRemoteConfiguration}, the client half of the\n * same protocol, so the header and the token cannot drift apart.\n *\n * Health endpoints are **not** guarded — a probe must answer without credentials,\n * or a readiness check becomes an authentication problem.\n */\nexport const requireServiceToken = <A, E, R>(route: Effect.Effect<A, E, R>) =>\n  // The return type is inferred rather than written out: `HttpServerResponse.json`\n  // contributes an `HttpBodyError` to the failure channel, and spelling the type\n  // out while omitting it is what makes `tsc` refuse the declaration emit — which\n  // `@nx/js:swc` hides, leaving a green build with no `.d.ts` and a TS6305\n  // cascade in every consumer. `requirePrincipal` infers for the same reason.\n  Effect.gen(function* () {\n    const request = yield* HttpServerRequest.HttpServerRequest;\n\n    if (!matches(request.headers[SERVICE_TOKEN_HEADER])) {\n      return yield* HttpServerResponse.json(\n        { error: 'unauthenticated', code: 'unauthenticated' },\n        { status: 401 },\n      );\n    }\n\n    return yield* route;\n  });\n"],"names":["timingSafeEqual","HttpServerRequest","HttpServerResponse","Effect","SERVICE_TOKEN_HEADER","DEV_SERVICE_TOKEN","serviceToken","process","env","CONFIG_SERVICE_TOKEN","matches","provided","undefined","left","Buffer","from","right","length","requireServiceToken","route","gen","request","headers","json","error","code","status"],"mappings":"AAAA,SAASA,eAAe,QAAQ,cAAc;AAE9C,SAASC,iBAAiB,EAAEC,kBAAkB,QAAQ,mBAAmB;AACzE,SAASC,MAAM,QAAQ,SAAS;AAEhC,mEAAmE,GACnE,OAAO,MAAMC,uBAAuB,kBAAkB;AAEtD;;;;CAIC,GACD,OAAO,MAAMC,oBAAoB,qCAAqC;AAEtE;;;CAGC,GACD,OAAO,MAAMC,eAAe;QAC1BC;YAAAA,oCAAAA,QAAQC,GAAG,CAACC,oBAAoB,YAAhCF,oCAAoCF;EAAkB;AAExD,6EAA6E,GAC7E,MAAMK,UAAU,CAACC;IACf,IAAIA,aAAaC,WAAW,OAAO;IACnC,MAAMC,OAAOC,OAAOC,IAAI,CAACJ;IACzB,MAAMK,QAAQF,OAAOC,IAAI,CAACT;IAC1B,6EAA6E;IAC7E,iEAAiE;IACjE,OAAOO,KAAKI,MAAM,KAAKD,MAAMC,MAAM,IAAIjB,gBAAgBa,MAAMG;AAC/D;AAEA;;;;;;;;;;;;;;;;;;;CAmBC,GACD,OAAO,MAAME,sBAAsB,CAAUC,QAC3C,iFAAiF;IACjF,+EAA+E;IAC/E,gFAAgF;IAChF,yEAAyE;IACzE,4EAA4E;IAC5EhB,OAAOiB,GAAG,CAAC;QACT,MAAMC,UAAU,OAAOpB,kBAAkBA,iBAAiB;QAE1D,IAAI,CAACS,QAAQW,QAAQC,OAAO,CAAClB,qBAAqB,GAAG;YACnD,OAAO,OAAOF,mBAAmBqB,IAAI,CACnC;gBAAEC,OAAO;gBAAmBC,MAAM;YAAkB,GACpD;gBAAEC,QAAQ;YAAI;QAElB;QAEA,OAAO,OAAOP;IAChB,GAAG"}

package/dist/entity-metadata-route.d.ts

@@ -0,0 +1,25 @@
+import { HttpServerRequest, HttpServerResponse } from '@effect/platform';
+import { PolicyDecisionTag } from '@entifix/authz';
+import { type Entity, type EntityConstructor } from '@entifix/core';
+import { Effect } from 'effect';
+/**
+ * `GET /api/<entity>/$metadata` — what this caller may do with one entity.
+ *
+ * Mounted **per entity, at a literal path**, not as a `/api/:entity/$metadata`
+ * wildcard. `HttpRouter` resolves through `find-my-way-ts`, where a static
+ * segment beats a parametric one and there is no backtracking once the
+ * parametric branch has matched: alongside an existing `/api/<entity>/:id`, a
+ * wildcard `$metadata` route never runs at all — the by-id handler wins with
+ * `id === "$metadata"`, misses, and answers its own `404`. The endpoint would
+ * read as "this entity has no metadata" while appearing mounted. A literal wins
+ * regardless of registration order, which is why the base exports a route for
+ * one entity and each service registers it for each of its own
+ * ([ADR 0026](../../../../../docs/adr/0026-the-use-case-descriptor-and-served-entity-metadata.md)).
+ *
+ * Deliberately **not** behind `requireOrganization`, even on a tenant-plane
+ * service: the document describes the model, not tenant data, and resolving a
+ * database handle here would leave a vendor with no active organization unable
+ * to see their own affordances.
+ */
+export declare const entityMetadataRoute: <TEntity extends Entity>(entityConstructor: EntityConstructor<TEntity>) => Effect.Effect<HttpServerResponse.HttpServerResponse, import("@effect/platform/HttpBody").HttpBodyError, PolicyDecisionTag | import("@entifix/business").TokenServiceTag | HttpServerRequest.HttpServerRequest>;
+//# sourceMappingURL=entity-metadata-route.d.ts.map

package/dist/entity-metadata-route.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"entity-metadata-route.d.ts","sourceRoot":"","sources":["../src/entity-metadata-route.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,iBAAiB,EAAE,kBAAkB,EAAE,MAAM,kBAAkB,CAAC;AACzE,OAAO,EAKL,iBAAiB,EAClB,MAAM,gBAAgB,CAAC;AACxB,OAAO,EAEL,KAAK,MAAM,EAEX,KAAK,iBAAiB,EAIvB,MAAM,eAAe,CAAC;AACvB,OAAO,EAAE,MAAM,EAAE,MAAM,QAAQ,CAAC;AAIhC;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,mBAAmB,GAAI,OAAO,SAAS,MAAM,EACxD,mBAAmB,iBAAiB,CAAC,OAAO,CAAC,mNA0D5C,CAAC"}

package/dist/entity-metadata-route.js

@@ -0,0 +1,89 @@
+import { createHash } from 'node:crypto';
+import { HttpServerRequest, HttpServerResponse } from '@effect/platform';
+import { parsePermission, permissionForEntity, permissionForUseCase, PolicyDecisionTag } from '@entifix/authz';
+import { describeEntityUseCases, ENTITY_ACTIONS, extractMetaEntity, makeEntityMetadataEnvelope } from '@entifix/core';
+import { Effect } from 'effect';
+import { requirePrincipal } from './auth/index.js';
+/**
+ * `GET /api/<entity>/$metadata` — what this caller may do with one entity.
+ *
+ * Mounted **per entity, at a literal path**, not as a `/api/:entity/$metadata`
+ * wildcard. `HttpRouter` resolves through `find-my-way-ts`, where a static
+ * segment beats a parametric one and there is no backtracking once the
+ * parametric branch has matched: alongside an existing `/api/<entity>/:id`, a
+ * wildcard `$metadata` route never runs at all — the by-id handler wins with
+ * `id === "$metadata"`, misses, and answers its own `404`. The endpoint would
+ * read as "this entity has no metadata" while appearing mounted. A literal wins
+ * regardless of registration order, which is why the base exports a route for
+ * one entity and each service registers it for each of its own
+ * ([ADR 0026](../../../../../docs/adr/0026-the-use-case-descriptor-and-served-entity-metadata.md)).
+ *
+ * Deliberately **not** behind `requireOrganization`, even on a tenant-plane
+ * service: the document describes the model, not tenant data, and resolving a
+ * database handle here would leave a vendor with no active organization unable
+ * to see their own affordances.
+ */ export const entityMetadataRoute = (entityConstructor)=>requirePrincipal((principal)=>Effect.gen(function*() {
+            const policy = yield* PolicyDecisionTag;
+            const allows = (permission)=>{
+                const { resource, action } = parsePermission(permission);
+                return policy.decide({
+                    subject: {
+                        roles: principal.roles
+                    },
+                    resource,
+                    action
+                });
+            };
+            // SECURITY BOUNDARY. The document names domains, entity keys and verbs —
+            // it is a map of the model — so an entity the caller may not read answers
+            // exactly as one this service does not host. A `403` here would make the
+            // endpoint an oracle: walk it and learn the shape of everything you are
+            // not allowed to see. Same category as `redactConfiguration`, not
+            // diagnostics polish.
+            if (!allows(permissionForEntity(entityConstructor, 'read'))) {
+                return yield* notFound(entityConstructor);
+            }
+            const document = {
+                actions: ENTITY_ACTIONS.filter((action)=>allows(permissionForEntity(entityConstructor, action))),
+                useCases: describeEntityUseCases(entityConstructor).filter((descriptor)=>allows(permissionForUseCase(entityConstructor, descriptor.key)))
+            };
+            // The ETag hashes the *computed* document, not the descriptor set the
+            // deployment declares. Two principals with different grants get different
+            // documents from the same model, so a hash of the model would `304` one
+            // caller onto another's affordances. Hashing the permission set instead
+            // would read `ROLE_PERMISSIONS` directly and go around `PolicyDecisionTag`,
+            // so an injected ABAC policy could change affordances without changing the
+            // tag. Computing first costs a metadata read and a handful of pure
+            // `decide` calls — no IO.
+            const body = JSON.stringify(makeEntityMetadataEnvelope(entityConstructor, document));
+            const etag = `"${createHash('sha256').update(body).digest('hex')}"`;
+            const request = yield* HttpServerRequest.HttpServerRequest;
+            if (request.headers['if-none-match'] === etag) {
+                return HttpServerResponse.empty({
+                    status: 304
+                }).pipe(HttpServerResponse.setHeaders(cacheHeaders(etag)));
+            }
+            return HttpServerResponse.text(body, {
+                contentType: 'application/json',
+                headers: cacheHeaders(etag)
+            });
+        }));
+/**
+ * The response varies by principal, so it must never land in a shared cache.
+ * `Vary` names **both** credential carriers because the shell reads the access
+ * token from the `entifix_at` cookie *or* an `Authorization: Bearer` header, and a
+ * cache keyed on only one of them would serve across the other.
+ */ const cacheHeaders = (etag)=>({
+        etag,
+        'cache-control': 'private, no-cache',
+        vary: 'Cookie, Authorization'
+    });
+/** Indistinguishable from the `404` a service gives for an entity it does not host. */ const notFound = (entityConstructor)=>HttpServerResponse.json({
+        message: 'not found',
+        code: 'notFound',
+        entity: extractMetaEntity(entityConstructor).key
+    }, {
+        status: 404
+    });
+
+//# sourceMappingURL=entity-metadata-route.js.map

package/dist/entity-metadata-route.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/entity-metadata-route.ts"],"sourcesContent":["import { createHash } from 'node:crypto';\n\nimport { HttpServerRequest, HttpServerResponse } from '@effect/platform';\nimport {\n  parsePermission,\n  type Permission,\n  permissionForEntity,\n  permissionForUseCase,\n  PolicyDecisionTag,\n} from '@entifix/authz';\nimport {\n  describeEntityUseCases,\n  type Entity,\n  ENTITY_ACTIONS,\n  type EntityConstructor,\n  type EntityMetadataDocument,\n  extractMetaEntity,\n  makeEntityMetadataEnvelope,\n} from '@entifix/core';\nimport { Effect } from 'effect';\n\nimport { requirePrincipal } from './auth/index.js';\n\n/**\n * `GET /api/<entity>/$metadata` — what this caller may do with one entity.\n *\n * Mounted **per entity, at a literal path**, not as a `/api/:entity/$metadata`\n * wildcard. `HttpRouter` resolves through `find-my-way-ts`, where a static\n * segment beats a parametric one and there is no backtracking once the\n * parametric branch has matched: alongside an existing `/api/<entity>/:id`, a\n * wildcard `$metadata` route never runs at all — the by-id handler wins with\n * `id === \"$metadata\"`, misses, and answers its own `404`. The endpoint would\n * read as \"this entity has no metadata\" while appearing mounted. A literal wins\n * regardless of registration order, which is why the base exports a route for\n * one entity and each service registers it for each of its own\n * ([ADR 0026](../../../../../docs/adr/0026-the-use-case-descriptor-and-served-entity-metadata.md)).\n *\n * Deliberately **not** behind `requireOrganization`, even on a tenant-plane\n * service: the document describes the model, not tenant data, and resolving a\n * database handle here would leave a vendor with no active organization unable\n * to see their own affordances.\n */\nexport const entityMetadataRoute = <TEntity extends Entity>(\n  entityConstructor: EntityConstructor<TEntity>,\n) =>\n  requirePrincipal(principal =>\n    Effect.gen(function* () {\n      const policy = yield* PolicyDecisionTag;\n      const allows = (permission: Permission): boolean => {\n        const { resource, action } = parsePermission(permission);\n        return policy.decide({\n          subject: { roles: principal.roles },\n          resource,\n          action,\n        });\n      };\n\n      // SECURITY BOUNDARY. The document names domains, entity keys and verbs —\n      // it is a map of the model — so an entity the caller may not read answers\n      // exactly as one this service does not host. A `403` here would make the\n      // endpoint an oracle: walk it and learn the shape of everything you are\n      // not allowed to see. Same category as `redactConfiguration`, not\n      // diagnostics polish.\n      if (!allows(permissionForEntity(entityConstructor, 'read'))) {\n        return yield* notFound(entityConstructor);\n      }\n\n      const document: EntityMetadataDocument = {\n        actions: ENTITY_ACTIONS.filter(action =>\n          allows(permissionForEntity(entityConstructor, action)),\n        ),\n        useCases: describeEntityUseCases(entityConstructor).filter(descriptor =>\n          allows(permissionForUseCase(entityConstructor, descriptor.key)),\n        ),\n      };\n\n      // The ETag hashes the *computed* document, not the descriptor set the\n      // deployment declares. Two principals with different grants get different\n      // documents from the same model, so a hash of the model would `304` one\n      // caller onto another's affordances. Hashing the permission set instead\n      // would read `ROLE_PERMISSIONS` directly and go around `PolicyDecisionTag`,\n      // so an injected ABAC policy could change affordances without changing the\n      // tag. Computing first costs a metadata read and a handful of pure\n      // `decide` calls — no IO.\n      const body = JSON.stringify(\n        makeEntityMetadataEnvelope(entityConstructor, document),\n      );\n      const etag = `\"${createHash('sha256').update(body).digest('hex')}\"`;\n\n      const request = yield* HttpServerRequest.HttpServerRequest;\n      if (request.headers['if-none-match'] === etag) {\n        return HttpServerResponse.empty({ status: 304 }).pipe(\n          HttpServerResponse.setHeaders(cacheHeaders(etag)),\n        );\n      }\n\n      return HttpServerResponse.text(body, {\n        contentType: 'application/json',\n        headers: cacheHeaders(etag),\n      });\n    }),\n  );\n\n/**\n * The response varies by principal, so it must never land in a shared cache.\n * `Vary` names **both** credential carriers because the shell reads the access\n * token from the `entifix_at` cookie *or* an `Authorization: Bearer` header, and a\n * cache keyed on only one of them would serve across the other.\n */\nconst cacheHeaders = (etag: string) => ({\n  etag,\n  'cache-control': 'private, no-cache',\n  vary: 'Cookie, Authorization',\n});\n\n/** Indistinguishable from the `404` a service gives for an entity it does not host. */\nconst notFound = <TEntity extends Entity>(\n  entityConstructor: EntityConstructor<TEntity>,\n) =>\n  HttpServerResponse.json(\n    {\n      message: 'not found',\n      code: 'notFound',\n      entity: extractMetaEntity(entityConstructor).key,\n    },\n    { status: 404 },\n  );\n"],"names":["createHash","HttpServerRequest","HttpServerResponse","parsePermission","permissionForEntity","permissionForUseCase","PolicyDecisionTag","describeEntityUseCases","ENTITY_ACTIONS","extractMetaEntity","makeEntityMetadataEnvelope","Effect","requirePrincipal","entityMetadataRoute","entityConstructor","principal","gen","policy","allows","permission","resource","action","decide","subject","roles","notFound","document","actions","filter","useCases","descriptor","key","body","JSON","stringify","etag","update","digest","request","headers","empty","status","pipe","setHeaders","cacheHeaders","text","contentType","vary","json","message","code","entity"],"mappings":"AAAA,SAASA,UAAU,QAAQ,cAAc;AAEzC,SAASC,iBAAiB,EAAEC,kBAAkB,QAAQ,mBAAmB;AACzE,SACEC,eAAe,EAEfC,mBAAmB,EACnBC,oBAAoB,EACpBC,iBAAiB,QACZ,iBAAiB;AACxB,SACEC,sBAAsB,EAEtBC,cAAc,EAGdC,iBAAiB,EACjBC,0BAA0B,QACrB,gBAAgB;AACvB,SAASC,MAAM,QAAQ,SAAS;AAEhC,SAASC,gBAAgB,QAAQ,kBAAkB;AAEnD;;;;;;;;;;;;;;;;;;CAkBC,GACD,OAAO,MAAMC,sBAAsB,CACjCC,oBAEAF,iBAAiBG,CAAAA,YACfJ,OAAOK,GAAG,CAAC;YACT,MAAMC,SAAS,OAAOX;YACtB,MAAMY,SAAS,CAACC;gBACd,MAAM,EAAEC,QAAQ,EAAEC,MAAM,EAAE,GAAGlB,gBAAgBgB;gBAC7C,OAAOF,OAAOK,MAAM,CAAC;oBACnBC,SAAS;wBAAEC,OAAOT,UAAUS,KAAK;oBAAC;oBAClCJ;oBACAC;gBACF;YACF;YAEA,yEAAyE;YACzE,0EAA0E;YAC1E,yEAAyE;YACzE,wEAAwE;YACxE,kEAAkE;YAClE,sBAAsB;YACtB,IAAI,CAACH,OAAOd,oBAAoBU,mBAAmB,UAAU;gBAC3D,OAAO,OAAOW,SAASX;YACzB;YAEA,MAAMY,WAAmC;gBACvCC,SAASnB,eAAeoB,MAAM,CAACP,CAAAA,SAC7BH,OAAOd,oBAAoBU,mBAAmBO;gBAEhDQ,UAAUtB,uBAAuBO,mBAAmBc,MAAM,CAACE,CAAAA,aACzDZ,OAAOb,qBAAqBS,mBAAmBgB,WAAWC,GAAG;YAEjE;YAEA,sEAAsE;YACtE,0EAA0E;YAC1E,wEAAwE;YACxE,wEAAwE;YACxE,4EAA4E;YAC5E,2EAA2E;YAC3E,mEAAmE;YACnE,0BAA0B;YAC1B,MAAMC,OAAOC,KAAKC,SAAS,CACzBxB,2BAA2BI,mBAAmBY;YAEhD,MAAMS,OAAO,CAAC,CAAC,EAAEnC,WAAW,UAAUoC,MAAM,CAACJ,MAAMK,MAAM,CAAC,OAAO,CAAC,CAAC;YAEnE,MAAMC,UAAU,OAAOrC,kBAAkBA,iBAAiB;YAC1D,IAAIqC,QAAQC,OAAO,CAAC,gBAAgB,KAAKJ,MAAM;gBAC7C,OAAOjC,mBAAmBsC,KAAK,CAAC;oBAAEC,QAAQ;gBAAI,GAAGC,IAAI,CACnDxC,mBAAmByC,UAAU,CAACC,aAAaT;YAE/C;YAEA,OAAOjC,mBAAmB2C,IAAI,CAACb,MAAM;gBACnCc,aAAa;gBACbP,SAASK,aAAaT;YACxB;QACF,IACA;AAEJ;;;;;CAKC,GACD,MAAMS,eAAe,CAACT,OAAkB,CAAA;QACtCA;QACA,iBAAiB;QACjBY,MAAM;IACR,CAAA;AAEA,qFAAqF,GACrF,MAAMtB,WAAW,CACfX,oBAEAZ,mBAAmB8C,IAAI,CACrB;QACEC,SAAS;QACTC,MAAM;QACNC,QAAQ1C,kBAAkBK,mBAAmBiB,GAAG;IAClD,GACA;QAAEU,QAAQ;IAAI"}

package/dist/health-routes.d.ts

@@ -0,0 +1,24 @@
+import { HttpRouter } from '@effect/platform';
+import { HealthRegistryTag, ShutdownRegistryTag } from '@entifix/business';
+/**
+ * Mount the probe endpoints on a router.
+ *
+ * - `GET /api/health` — the original endpoint, unchanged. Kept because
+ *   Playwright's `readyPath` and existing tooling point at it.
+ * - `GET /api/health/live` — **liveness**. Answers from the process alone: no
+ *   datastore, no config-service, no session. This is deliberate and load
+ *   bearing. A liveness probe that checks dependencies turns a Mongo blip into
+ *   "Kubernetes restarts every replica", which is an outage the probe caused.
+ * - `GET /api/health/ready` — **readiness**: `200` when every registered probe
+ *   passes, `503 {status:'degraded', failing:[…]}` otherwise. Kubernetes pulls
+ *   a not-ready pod out of the load balancer without killing it, which is what
+ *   a reconnecting client wants. A process that has begun terminating answers
+ *   `503 {status:'terminating'}` instead, **before** any probe runs: nothing is
+ *   failing, and running the probes would ask a closing pool a question whose
+ *   answer changes nothing.
+ *
+ * The failing list carries probe **names** only — never a URI, host, or driver
+ * message. This endpoint answers anyone who can reach the port.
+ */
+export declare const withHealthRoutes: <E, R>(router: HttpRouter.HttpRouter<E, R>, serviceName: string) => HttpRouter.HttpRouter<import("@effect/platform/HttpBody").HttpBodyError | E, HealthRegistryTag | ShutdownRegistryTag | R>;
+//# sourceMappingURL=health-routes.d.ts.map

package/dist/health-routes.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"health-routes.d.ts","sourceRoot":"","sources":["../src/health-routes.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAsB,MAAM,kBAAkB,CAAC;AAElE,OAAO,EAAE,iBAAiB,EAAE,mBAAmB,EAAE,MAAM,mBAAmB,CAAC;AAgB3E;;;;;;;;;;;;;;;;;;;GAmBG;AAIH,eAAO,MAAM,gBAAgB,GAAI,CAAC,EAAE,CAAC,EACnC,QAAQ,UAAU,CAAC,UAAU,CAAC,CAAC,EAAE,CAAC,CAAC,EACnC,aAAa,MAAM,8HAsDpB,CAAC"}

package/dist/health-routes.js

@@ -0,0 +1,81 @@
+import { HttpRouter, HttpServerResponse } from '@effect/platform';
+import { HealthRegistryTag, ShutdownRegistryTag } from '@entifix/business';
+import { Effect, Ref } from 'effect';
+/**
+ * How long a readiness result is reused. These endpoints are unauthenticated by
+ * necessity (a probe cannot hold a session), so without a cache every request
+ * would reach Mongo — a cheap lever for anyone who can reach the port, and
+ * noise in the datastore's own metrics.
+ */ const READY_CACHE_MS = 1000;
+/**
+ * Mount the probe endpoints on a router.
+ *
+ * - `GET /api/health` — the original endpoint, unchanged. Kept because
+ *   Playwright's `readyPath` and existing tooling point at it.
+ * - `GET /api/health/live` — **liveness**. Answers from the process alone: no
+ *   datastore, no config-service, no session. This is deliberate and load
+ *   bearing. A liveness probe that checks dependencies turns a Mongo blip into
+ *   "Kubernetes restarts every replica", which is an outage the probe caused.
+ * - `GET /api/health/ready` — **readiness**: `200` when every registered probe
+ *   passes, `503 {status:'degraded', failing:[…]}` otherwise. Kubernetes pulls
+ *   a not-ready pod out of the load balancer without killing it, which is what
+ *   a reconnecting client wants. A process that has begun terminating answers
+ *   `503 {status:'terminating'}` instead, **before** any probe runs: nothing is
+ *   failing, and running the probes would ask a closing pool a question whose
+ *   answer changes nothing.
+ *
+ * The failing list carries probe **names** only — never a URI, host, or driver
+ * message. This endpoint answers anyone who can reach the port.
+ */ // The return type is inferred rather than annotated: `HttpServerResponse.json`
+// widens the router's error channel with `HttpBodyError`, and spelling that out
+// here would only duplicate what the platform types already say.
+export const withHealthRoutes = (router, serviceName)=>{
+    // One cache per server instance (the e2e mock profile boots services
+    // in-process, so a module-level cache would leak across them).
+    const cache = Ref.unsafeMake(null);
+    const cachedReport = Effect.gen(function*() {
+        const now = Date.now();
+        const entry = yield* Ref.get(cache);
+        if (entry !== null && now - entry.at < READY_CACHE_MS) return entry.report;
+        const registry = yield* HealthRegistryTag;
+        const report = yield* registry.report;
+        yield* Ref.set(cache, {
+            at: now,
+            report
+        });
+        return report;
+    });
+    return router.pipe(HttpRouter.get('/api/health', HttpServerResponse.json({
+        status: 'ok',
+        service: serviceName
+    })), HttpRouter.get('/api/health/live', HttpServerResponse.json({
+        status: 'live',
+        service: serviceName
+    })), HttpRouter.get('/api/health/ready', Effect.gen(function*() {
+        const shutdown = yield* ShutdownRegistryTag;
+        // Ahead of the cache, deliberately: a report cached a moment before the
+        // signal landed would go on answering `200` for up to READY_CACHE_MS,
+        // which is precisely the window a rolling restart lives in.
+        if (yield* shutdown.terminating) {
+            return yield* HttpServerResponse.json({
+                status: 'terminating',
+                service: serviceName
+            }, {
+                status: 503
+            });
+        }
+        const report = yield* cachedReport;
+        return yield* HttpServerResponse.json(report.ready ? {
+            status: 'ready',
+            service: serviceName
+        } : {
+            status: 'degraded',
+            service: serviceName,
+            failing: report.failing
+        }, {
+            status: report.ready ? 200 : 503
+        });
+    })));
+};
+
+//# sourceMappingURL=health-routes.js.map

package/dist/health-routes.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/health-routes.ts"],"sourcesContent":["import { HttpRouter, HttpServerResponse } from '@effect/platform';\nimport type { HealthReport } from '@entifix/business';\nimport { HealthRegistryTag, ShutdownRegistryTag } from '@entifix/business';\nimport { Effect, Ref } from 'effect';\n\n/**\n * How long a readiness result is reused. These endpoints are unauthenticated by\n * necessity (a probe cannot hold a session), so without a cache every request\n * would reach Mongo — a cheap lever for anyone who can reach the port, and\n * noise in the datastore's own metrics.\n */\nconst READY_CACHE_MS = 1_000;\n\ninterface CacheEntry {\n  readonly at: number;\n  readonly report: HealthReport;\n}\n\n/**\n * Mount the probe endpoints on a router.\n *\n * - `GET /api/health` — the original endpoint, unchanged. Kept because\n *   Playwright's `readyPath` and existing tooling point at it.\n * - `GET /api/health/live` — **liveness**. Answers from the process alone: no\n *   datastore, no config-service, no session. This is deliberate and load\n *   bearing. A liveness probe that checks dependencies turns a Mongo blip into\n *   \"Kubernetes restarts every replica\", which is an outage the probe caused.\n * - `GET /api/health/ready` — **readiness**: `200` when every registered probe\n *   passes, `503 {status:'degraded', failing:[…]}` otherwise. Kubernetes pulls\n *   a not-ready pod out of the load balancer without killing it, which is what\n *   a reconnecting client wants. A process that has begun terminating answers\n *   `503 {status:'terminating'}` instead, **before** any probe runs: nothing is\n *   failing, and running the probes would ask a closing pool a question whose\n *   answer changes nothing.\n *\n * The failing list carries probe **names** only — never a URI, host, or driver\n * message. This endpoint answers anyone who can reach the port.\n */\n// The return type is inferred rather than annotated: `HttpServerResponse.json`\n// widens the router's error channel with `HttpBodyError`, and spelling that out\n// here would only duplicate what the platform types already say.\nexport const withHealthRoutes = <E, R>(\n  router: HttpRouter.HttpRouter<E, R>,\n  serviceName: string,\n) => {\n  // One cache per server instance (the e2e mock profile boots services\n  // in-process, so a module-level cache would leak across them).\n  const cache = Ref.unsafeMake<CacheEntry | null>(null);\n\n  const cachedReport = Effect.gen(function* () {\n    const now = Date.now();\n    const entry = yield* Ref.get(cache);\n    if (entry !== null && now - entry.at < READY_CACHE_MS) return entry.report;\n\n    const registry = yield* HealthRegistryTag;\n    const report = yield* registry.report;\n    yield* Ref.set(cache, { at: now, report });\n    return report;\n  });\n\n  return router.pipe(\n    HttpRouter.get(\n      '/api/health',\n      HttpServerResponse.json({ status: 'ok', service: serviceName }),\n    ),\n    HttpRouter.get(\n      '/api/health/live',\n      HttpServerResponse.json({ status: 'live', service: serviceName }),\n    ),\n    HttpRouter.get(\n      '/api/health/ready',\n      Effect.gen(function* () {\n        const shutdown = yield* ShutdownRegistryTag;\n        // Ahead of the cache, deliberately: a report cached a moment before the\n        // signal landed would go on answering `200` for up to READY_CACHE_MS,\n        // which is precisely the window a rolling restart lives in.\n        if (yield* shutdown.terminating) {\n          return yield* HttpServerResponse.json(\n            { status: 'terminating', service: serviceName },\n            { status: 503 },\n          );\n        }\n\n        const report = yield* cachedReport;\n        return yield* HttpServerResponse.json(\n          report.ready\n            ? { status: 'ready', service: serviceName }\n            : {\n                status: 'degraded',\n                service: serviceName,\n                failing: report.failing,\n              },\n          { status: report.ready ? 200 : 503 },\n        );\n      }),\n    ),\n  );\n};\n"],"names":["HttpRouter","HttpServerResponse","HealthRegistryTag","ShutdownRegistryTag","Effect","Ref","READY_CACHE_MS","withHealthRoutes","router","serviceName","cache","unsafeMake","cachedReport","gen","now","Date","entry","get","at","report","registry","set","pipe","json","status","service","shutdown","terminating","ready","failing"],"mappings":"AAAA,SAASA,UAAU,EAAEC,kBAAkB,QAAQ,mBAAmB;AAElE,SAASC,iBAAiB,EAAEC,mBAAmB,QAAQ,oBAAoB;AAC3E,SAASC,MAAM,EAAEC,GAAG,QAAQ,SAAS;AAErC;;;;;CAKC,GACD,MAAMC,iBAAiB;AAOvB;;;;;;;;;;;;;;;;;;;CAmBC,GACD,+EAA+E;AAC/E,gFAAgF;AAChF,iEAAiE;AACjE,OAAO,MAAMC,mBAAmB,CAC9BC,QACAC;IAEA,qEAAqE;IACrE,+DAA+D;IAC/D,MAAMC,QAAQL,IAAIM,UAAU,CAAoB;IAEhD,MAAMC,eAAeR,OAAOS,GAAG,CAAC;QAC9B,MAAMC,MAAMC,KAAKD,GAAG;QACpB,MAAME,QAAQ,OAAOX,IAAIY,GAAG,CAACP;QAC7B,IAAIM,UAAU,QAAQF,MAAME,MAAME,EAAE,GAAGZ,gBAAgB,OAAOU,MAAMG,MAAM;QAE1E,MAAMC,WAAW,OAAOlB;QACxB,MAAMiB,SAAS,OAAOC,SAASD,MAAM;QACrC,OAAOd,IAAIgB,GAAG,CAACX,OAAO;YAAEQ,IAAIJ;YAAKK;QAAO;QACxC,OAAOA;IACT;IAEA,OAAOX,OAAOc,IAAI,CAChBtB,WAAWiB,GAAG,CACZ,eACAhB,mBAAmBsB,IAAI,CAAC;QAAEC,QAAQ;QAAMC,SAAShB;IAAY,KAE/DT,WAAWiB,GAAG,CACZ,oBACAhB,mBAAmBsB,IAAI,CAAC;QAAEC,QAAQ;QAAQC,SAAShB;IAAY,KAEjET,WAAWiB,GAAG,CACZ,qBACAb,OAAOS,GAAG,CAAC;QACT,MAAMa,WAAW,OAAOvB;QACxB,wEAAwE;QACxE,sEAAsE;QACtE,4DAA4D;QAC5D,IAAI,OAAOuB,SAASC,WAAW,EAAE;YAC/B,OAAO,OAAO1B,mBAAmBsB,IAAI,CACnC;gBAAEC,QAAQ;gBAAeC,SAAShB;YAAY,GAC9C;gBAAEe,QAAQ;YAAI;QAElB;QAEA,MAAML,SAAS,OAAOP;QACtB,OAAO,OAAOX,mBAAmBsB,IAAI,CACnCJ,OAAOS,KAAK,GACR;YAAEJ,QAAQ;YAASC,SAAShB;QAAY,IACxC;YACEe,QAAQ;YACRC,SAAShB;YACToB,SAASV,OAAOU,OAAO;QACzB,GACJ;YAAEL,QAAQL,OAAOS,KAAK,GAAG,MAAM;QAAI;IAEvC;AAGN,EAAE"}

package/dist/index.d.ts

@@ -0,0 +1,12 @@
+export * from './auth/index.js';
+export * from './entity-metadata-route.js';
+export * from './health-routes.js';
+export * from './load-remote-configuration.js';
+export * from './make-service.js';
+export * from './observability.js';
+export * from './redact-configuration.js';
+export * from './serve-test-service.js';
+export * from './service-description-route.js';
+export * from './sse.js';
+export * from './wait-for-http.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,iBAAiB,CAAC;AAChC,cAAc,4BAA4B,CAAC;AAC3C,cAAc,oBAAoB,CAAC;AACnC,cAAc,gCAAgC,CAAC;AAC/C,cAAc,mBAAmB,CAAC;AAClC,cAAc,oBAAoB,CAAC;AACnC,cAAc,2BAA2B,CAAC;AAC1C,cAAc,yBAAyB,CAAC;AACxC,cAAc,gCAAgC,CAAC;AAC/C,cAAc,UAAU,CAAC;AACzB,cAAc,oBAAoB,CAAC"}

package/dist/index.js

@@ -0,0 +1,13 @@
+export * from './auth/index.js';
+export * from './entity-metadata-route.js';
+export * from './health-routes.js';
+export * from './load-remote-configuration.js';
+export * from './make-service.js';
+export * from './observability.js';
+export * from './redact-configuration.js';
+export * from './serve-test-service.js';
+export * from './service-description-route.js';
+export * from './sse.js';
+export * from './wait-for-http.js';
+
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/index.ts"],"sourcesContent":["export * from './auth/index.js';\nexport * from './entity-metadata-route.js';\nexport * from './health-routes.js';\nexport * from './load-remote-configuration.js';\nexport * from './make-service.js';\nexport * from './observability.js';\nexport * from './redact-configuration.js';\nexport * from './serve-test-service.js';\nexport * from './service-description-route.js';\nexport * from './sse.js';\nexport * from './wait-for-http.js';\n"],"names":[],"mappings":"AAAA,cAAc,kBAAkB;AAChC,cAAc,6BAA6B;AAC3C,cAAc,qBAAqB;AACnC,cAAc,iCAAiC;AAC/C,cAAc,oBAAoB;AAClC,cAAc,qBAAqB;AACnC,cAAc,4BAA4B;AAC1C,cAAc,0BAA0B;AACxC,cAAc,iCAAiC;AAC/C,cAAc,WAAW;AACzB,cAAc,qBAAqB"}

package/dist/load-remote-configuration.d.ts

@@ -0,0 +1,77 @@
+import { ConfigurationClientInMemory, ConfigurationPlain, EntifixConnError } from '@entifix/core';
+import { Context, Effect, Schedule } from 'effect';
+declare const LoadedConfigurationTag_base: Context.TagClass<LoadedConfigurationTag, "LoadedConfigurationTag", ConfigurationPlain>;
+/**
+ * DI tag carrying the raw {@link ConfigurationPlain} a service loaded at boot,
+ * so a `GET /api/config` introspection route can expose it (redacted).
+ */
+export declare class LoadedConfigurationTag extends LoadedConfigurationTag_base {
+}
+/**
+ * Default boot-fetch retry policy: 20 attempts spaced 1s apart (~20s window).
+ *
+ * A dependent service `dev` target `dependsOn config-service:dev`, but Nx
+ * considers a *continuous* dependency "ready" the moment its process starts —
+ * not when its HTTP server is listening and its table is seeded. So a fast
+ * backend can fire its boot fetch before config-service answers and, without a
+ * retry, would crash with `fetch failed` (connection refused). Retrying a
+ * bounded window lets the fleet come up in any order.
+ */
+export declare const defaultConfigRetrySchedule: Schedule.Schedule<unknown, unknown>;
+/**
+ * Deadline for a single boot-fetch attempt.
+ *
+ * **The retry above only helps if an attempt can fail.** `fetch` has no timeout
+ * of its own, so a connection that is accepted but never answered — a previous
+ * listener dying mid-flight, a half-open socket — leaves it waiting forever.
+ * The schedule never sees a failure, never retries, and the service hangs in its
+ * boot layer with its port bound and nothing served: measured twice on
+ * 2026-08-14, on auth-service and then marketplace-service, recovered only by a
+ * full `dev:reset` ([#84](https://github.com/r10c-technologies/r10c/issues/84)).
+ *
+ * So an attempt is deadlined, for the same reason a readiness probe is: a check
+ * that hangs is a check that failed. The ordinary race this retry was written
+ * for — config-service not listening yet — still fails instantly with
+ * `ECONNREFUSED` and costs nothing, so this bounds the pathological case only:
+ * 20 retries × (5s deadline + 1s spacing) ≈ 2 minutes before the service exits
+ * loudly instead of hanging silently.
+ */
+export declare const defaultConfigAttemptTimeoutMs = 5000;
+/** Options for {@link loadRemoteConfiguration}. */
+export interface LoadRemoteConfigurationOptions {
+    /**
+     * Retry policy for the boot fetch. Defaults to
+     * {@link defaultConfigRetrySchedule}. Pass `Schedule.stop` to fail fast (a
+     * single attempt, no retry) — used by tests and callers that want the error
+     * immediately.
+     */
+    readonly retrySchedule?: Schedule.Schedule<unknown, unknown>;
+    /**
+     * Deadline for one attempt, in milliseconds. Defaults to
+     * {@link defaultConfigAttemptTimeoutMs}. There is deliberately no way to
+     * disable it — an attempt that cannot time out is the bug this exists for.
+     */
+    readonly attemptTimeoutMs?: number;
+}
+/**
+ * Fetches a service's configuration from the central config-service
+ * (`GET {configApiUrl}/api/config/{service}`) and returns it as a
+ * {@link ConfigurationPlain}. Backends call this at boot to resolve their own
+ * parameters (e.g. `mongo.uri`) instead of hardcoding them.
+ *
+ * Uses Node's global `fetch` (same transport approach as the REST client); any
+ * network/parse/non-2xx failure becomes an {@link EntifixConnError}. Each
+ * attempt is deadlined ({@link defaultConfigAttemptTimeoutMs}) and the fetch is
+ * retried on a bounded schedule ({@link defaultConfigRetrySchedule}), so a
+ * dependent that boots before config-service is HTTP-ready waits it out — and
+ * one that reaches a socket nobody is answering gives up rather than hanging.
+ */
+export declare const loadRemoteConfiguration: (configApiUrl: string, service: string, options?: LoadRemoteConfigurationOptions) => Effect.Effect<ConfigurationPlain, EntifixConnError>;
+/**
+ * Convenience: load the remote configuration and wrap it in a
+ * {@link ConfigurationClientInMemory} ready to satisfy `ConfigurationRepositoryTag`
+ * and to read the service's own parameters via `.in(group).getString(key)`.
+ */
+export declare const loadRemoteConfigurationClient: (configApiUrl: string, service: string, options?: LoadRemoteConfigurationOptions) => Effect.Effect<ConfigurationClientInMemory, EntifixConnError>;
+export {};
+//# sourceMappingURL=load-remote-configuration.d.ts.map

package/dist/load-remote-configuration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"load-remote-configuration.d.ts","sourceRoot":"","sources":["../src/load-remote-configuration.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,kBAAkB,EAClB,gBAAgB,EACjB,MAAM,eAAe,CAAC;AACvB,OAAO,EAAE,OAAO,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,QAAQ,CAAC;;AAInD;;;GAGG;AACH,qBAAa,sBAAuB,SAAQ,2BAEG;CAAG;AAElD;;;;;;;;;GASG;AACH,eAAO,MAAM,0BAA0B,EAAE,QAAQ,CAAC,QAAQ,CAAC,OAAO,EAAE,OAAO,CACJ,CAAC;AAExE;;;;;;;;;;;;;;;;;GAiBG;AACH,eAAO,MAAM,6BAA6B,OAAQ,CAAC;AAEnD,mDAAmD;AACnD,MAAM,WAAW,8BAA8B;IAC7C;;;;;OAKG;IACH,QAAQ,CAAC,aAAa,CAAC,EAAE,QAAQ,CAAC,QAAQ,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC;IAC7D;;;;OAIG;IACH,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAC;CACpC;AAED;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,uBAAuB,GAClC,cAAc,MAAM,EACpB,SAAS,MAAM,EACf,UAAS,8BAAmC,KAC3C,MAAM,CAAC,MAAM,CAAC,kBAAkB,EAAE,gBAAgB,CAwCpD,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,6BAA6B,GACxC,cAAc,MAAM,EACpB,SAAS,MAAM,EACf,UAAS,8BAAmC,KAC3C,MAAM,CAAC,MAAM,CAAC,2BAA2B,EAAE,gBAAgB,CAG3D,CAAC"}

package/dist/load-remote-configuration.js

@@ -0,0 +1,87 @@
+import { ConfigurationClientInMemory, EntifixConnError } from '@entifix/core';
+import { Context, Effect, Schedule } from 'effect';
+import { SERVICE_TOKEN_HEADER, serviceToken } from './auth/service-token.js';
+/**
+ * DI tag carrying the raw {@link ConfigurationPlain} a service loaded at boot,
+ * so a `GET /api/config` introspection route can expose it (redacted).
+ */ export class LoadedConfigurationTag extends Context.Tag('LoadedConfigurationTag')() {
+}
+/**
+ * Default boot-fetch retry policy: 20 attempts spaced 1s apart (~20s window).
+ *
+ * A dependent service `dev` target `dependsOn config-service:dev`, but Nx
+ * considers a *continuous* dependency "ready" the moment its process starts —
+ * not when its HTTP server is listening and its table is seeded. So a fast
+ * backend can fire its boot fetch before config-service answers and, without a
+ * retry, would crash with `fetch failed` (connection refused). Retrying a
+ * bounded window lets the fleet come up in any order.
+ */ export const defaultConfigRetrySchedule = Schedule.intersect(Schedule.spaced('1 seconds'), Schedule.recurs(20));
+/**
+ * Deadline for a single boot-fetch attempt.
+ *
+ * **The retry above only helps if an attempt can fail.** `fetch` has no timeout
+ * of its own, so a connection that is accepted but never answered — a previous
+ * listener dying mid-flight, a half-open socket — leaves it waiting forever.
+ * The schedule never sees a failure, never retries, and the service hangs in its
+ * boot layer with its port bound and nothing served: measured twice on
+ * 2026-08-14, on auth-service and then marketplace-service, recovered only by a
+ * full `dev:reset` ([#84](https://github.com/r10c-technologies/r10c/issues/84)).
+ *
+ * So an attempt is deadlined, for the same reason a readiness probe is: a check
+ * that hangs is a check that failed. The ordinary race this retry was written
+ * for — config-service not listening yet — still fails instantly with
+ * `ECONNREFUSED` and costs nothing, so this bounds the pathological case only:
+ * 20 retries × (5s deadline + 1s spacing) ≈ 2 minutes before the service exits
+ * loudly instead of hanging silently.
+ */ export const defaultConfigAttemptTimeoutMs = 5000;
+/**
+ * Fetches a service's configuration from the central config-service
+ * (`GET {configApiUrl}/api/config/{service}`) and returns it as a
+ * {@link ConfigurationPlain}. Backends call this at boot to resolve their own
+ * parameters (e.g. `mongo.uri`) instead of hardcoding them.
+ *
+ * Uses Node's global `fetch` (same transport approach as the REST client); any
+ * network/parse/non-2xx failure becomes an {@link EntifixConnError}. Each
+ * attempt is deadlined ({@link defaultConfigAttemptTimeoutMs}) and the fetch is
+ * retried on a bounded schedule ({@link defaultConfigRetrySchedule}), so a
+ * dependent that boots before config-service is HTTP-ready waits it out — and
+ * one that reaches a socket nobody is answering gives up rather than hanging.
+ */ export const loadRemoteConfiguration = (configApiUrl, service, options = {})=>{
+    var _options_attemptTimeoutMs, _options_retrySchedule;
+    const url = `${configApiUrl.replace(/\/+$/, '')}/api/config/${service}`;
+    const attemptTimeoutMs = (_options_attemptTimeoutMs = options.attemptTimeoutMs) != null ? _options_attemptTimeoutMs : defaultConfigAttemptTimeoutMs;
+    const fetchOnce = Effect.tryPromise({
+        try: async ()=>{
+            const response = await fetch(url, {
+                cache: 'no-store',
+                headers: {
+                    [SERVICE_TOKEN_HEADER]: serviceToken()
+                },
+                signal: AbortSignal.timeout(attemptTimeoutMs)
+            }).catch((error)=>{
+                // Rewritten because the raw abort says `This operation was aborted`,
+                // which reads like a bug in the caller rather than a silent peer.
+                if (error instanceof Error && error.name === 'TimeoutError') {
+                    throw new Error(`config-service did not answer within ${attemptTimeoutMs}ms at ${url}`);
+                }
+                throw error;
+            });
+            if (!response.ok) {
+                throw new Error(`config-service responded ${response.status} for ${url}`);
+            }
+            return await response.json();
+        },
+        catch: (error)=>new EntifixConnError(`Failed to load configuration for "${service}" from config-service`, error, {
+                url,
+                service
+            })
+    });
+    return Effect.retry(fetchOnce, (_options_retrySchedule = options.retrySchedule) != null ? _options_retrySchedule : defaultConfigRetrySchedule);
+};
+/**
+ * Convenience: load the remote configuration and wrap it in a
+ * {@link ConfigurationClientInMemory} ready to satisfy `ConfigurationRepositoryTag`
+ * and to read the service's own parameters via `.in(group).getString(key)`.
+ */ export const loadRemoteConfigurationClient = (configApiUrl, service, options = {})=>loadRemoteConfiguration(configApiUrl, service, options).pipe(Effect.map((plain)=>new ConfigurationClientInMemory(plain)));
+
+//# sourceMappingURL=load-remote-configuration.js.map