@gnldev/server 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Karaca Yılmaz (https://gnl.dev)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,181 @@
+# @gnldev/server
+
+Exposes the `createGnl` registry as **auto-REST + OpenAPI + SSE**. Every endpoint bottoms out in `runDurable` → the journal, replay and the [at-most-once side-effect guarantee](../durable/README.md#what-never-charged-twice-actually-means) are inherited for free. (The durable counterpart to the common auto-REST pattern.)
+
+> Install: `pnpm add @gnldev/server` — or use it from a [repo clone](https://github.com/Karaca7/gnldev): `pnpm install && pnpm -r build`.
+
+```bash
+npm i @gnldev/server   # peer: @gnldev/durable  ·  dep: hono
+```
+
+```ts
+import { createRestApi } from '@gnldev/server';
+import { serve } from '@hono/node-server';
+import { SqliteStorage } from '@gnldev/durable/sqlite';
+
+const api = createRestApi({
+  journal: new SqliteStorage('runs.db').runs,
+  agents: { support: { model: 'anthropic/claude-opus-4-8', tools, guard, maxSteps: 8 } },
+});
+serve({ fetch: api.fetch, port: 3000 });        // on its own port
+// app.mount('/api', api)                      // inside a Hono app
+```
+
+## Binding it to a Node server
+
+`createRestApi` returns a fetch handler — callable, and carrying `.fetch`. On Node, bind it with the
+bridge on this package's own subpath:
+
+```ts
+import { createServer } from 'node:http';
+import { toNodeHandler } from '@gnldev/server/node';
+
+express().use('/api', toNodeHandler(api));                            // Express
+await fastify.register(middie); fastify.use('/api', toNodeHandler(api));   // Fastify + @fastify/middie
+koa.use(c2k((req, res, _next) => toNodeHandler(api)(req, res)));      // Koa + koa-connect
+createServer(toNodeHandler(api)).listen(3000);                        // node:http
+nestApp.use('/api', toNodeHandler(api));                              // Nest (Express or Fastify)
+```
+
+Two rules, both measured on live servers rather than reasoned about:
+
+**Bind at the middleware layer, not as a route.** On Fastify the difference is the whole story:
+middleware runs before body parsing, a route runs after it. `fastify.all('/api/*', …)` looks correct,
+passes every GET, and answers 400 to a perfectly good POST — because Fastify's built-in JSON parser
+has already drained the stream.
+
+**On Koa, declare the third parameter.** `koa-connect` switches on `fn.length`: a middleware with
+fewer than three parameters is assumed not to terminate the response, so it calls `next()` straight
+after and Koa writes its own 404 over what was already sent — measured, `ERR_HTTP_HEADERS_SENT` and
+404 on every route. Naming `next` without calling it selects the branch that waits, which is what a
+handler that owns the response needs.
+
+**Mount before whatever parses request bodies.** A parser that runs first reads the stream to the end
+and hands the result to the framework, not to us. Get it wrong and the bridge says so
+(`body_consumed_upstream`) instead of blaming your request. Your own routes keep the parser: it still
+runs for everything mounted after.
+
+## Endpoints (per agent)
+| Method | Path | Description |
+|---|---|---|
+| GET | `/agents` | List of registered agent metadata (client/playground selector) |
+| POST | `/agents/:name/run` | Durable run `{runId, prompt\|messages, threadId?, approvals?}` → `{ok, runId, text, interrupts}` |
+| POST | `/agents/:name/stream` | **SSE** streaming run (schema below) |
+| POST | `/agents/:name/resume` | `{runId, approvals?}` — the input is read from the journal |
+| GET | `/runs` · `/runs/:id` | Run summaries / journal timeline |
+| GET | `/openapi.json` | Generated schema |
+| GET | `/health` | Liveness — process is alive. No storage access. **Unauthenticated** |
+| GET | `/ready` | Readiness — can serve traffic; 503 if the journal is unreachable. **Unauthenticated** |
+
+### Health checks
+
+`/health` and `/ready` answer two different questions, and pointing the wrong probe at the wrong one
+causes the wrong action:
+
+- **`/health`** — is the process alive? It touches nothing. A failing *dependency* must not make an
+  orchestrator kill and restart a healthy process: restarting it does not reconnect your database, it
+  only discards whatever the process still had in flight. Use this for liveness probes.
+- **`/ready`** — can it serve? It reads from the journal, with a 2s budget because an unreachable
+  database usually *hangs* rather than refusing. On failure the instance leaves the load balancer while
+  staying alive to recover. Use this for readiness/traffic probes.
+
+Both are deliberately unauthenticated — probes run before any credential exists, and usually never get
+one. For the same reason they report reachability and nothing else: no agent names, no counts, no
+configuration, and never the underlying error, which for a database failure routinely carries the host,
+database and user. That detail goes to your logs.
+
+```yaml
+# Kubernetes
+livenessProbe:  { httpGet: { path: /health, port: 3000 } }
+readinessProbe: { httpGet: { path: /ready,  port: 3000 } }
+```
+
+### SSE schema (`/stream`)
+`event` + JSON `data`: `text-delta {text}` · `tool-call {toolCallId,toolName,input}` · `tool-result {...}` · `error {error}` · `interrupt {interrupts[]}` (when the stream ends) · `done {runId,finishReason,usage}`. The same schema is also used in the `@gnldev/studio` playground → [`@gnldev/client`](../client) connects to both ends.
+
+### Reconnect recovery (resumable SSE, opt-in)
+Every SSE event carries a deterministic, monotonically increasing `id:` field starting at 0. Calling the
+stream again with the same `runId` is deterministic journal replay (the model/tools do NOT actually run
+again) → fullStream produces the same chunk sequence, so the same event sequence comes out with the SAME ids.
+
+The browser's `EventSource` automatically sends the last `id:` it saw via the `Last-Event-ID` header when
+reconnecting after a dropped connection — the server reads this (or `lastEventId` in the body) and for
+events with `id <= lastEventId` it **produces them but does not write them to the client** (production is
+cheap: replay does not call the model/tools). Only events with `id > lastEventId` are sent. If `lastEventId`
+is not given, behavior is identical to before (aside from the added id).
+
+## Frontend
+For type-safe calls use [`@gnldev/client`](../client) (core) + `@gnldev/client/react` (hooks). For REST + Studio Playground in one command use [`@gnldev/cli`](../cli) `gnl dev`.
+
+## How it works
+Every call to `/run` and `/stream` names one of two things, and exactly one:
+
+- **`workKey`** — your name for a unit of work, not for a conversation. The engine derives the run's
+  id from it and returns that id in the `X-Gnl-Run-Id` header. Calling again with the same `workKey`
+  is routed to the same run: durable replay, side effects once. A `workKey` is a *business name* (the
+  invoice being issued, tonight's reconciliation batch) — keep sensitive data out of it, because it
+  is reflected in error details and shown on Studio screens. Coming from `thread_id`? There the same
+  key means *continue this conversation*; here it means *this is the same job*. A conversation is
+  `threadId`, a separate field you can send at the same time.
+- **`runId`** — a raw id you already hold (a resume, a fork, an id you stored).
+
+Sending both is a 400: two identities for one call is a question with no honest answer. Sending
+neither is also a 400. `Idempotency-Key` is accepted as a `workKey` alias — it names the work, which
+is what that header has always meant — and it is read only when the body named nothing itself.
+
+A `workKey` in the default `resource` scope needs a subject to be unique *within*: name the end user
+(`resourceId`, or an authenticated principal), or the call is refused rather than run for nobody.
+
+**How long a `workKey` stays unique:** as long as the run record lives — not a minute longer. Your
+retention window should not be shorter than the longest retry your clients can produce.
+
+**Was this call new work, or an answer you already had?** Every response to `/run` and `/stream`
+carries `X-Gnl-Idempotency-Status`: `new` when this call started the run, `replay` when the run had
+already been driven and the answer came from the journal. Nothing re-ran in the `replay` case — no
+model call, no tool, no charge. It is the header to log if you want to know how much of your traffic
+is retries, and the one to assert on if you are verifying that your client's retry logic is actually
+deduplicating.
+
+**`run_busy` (409) is a narrower condition than it looks.** It does not mean "this id has been used";
+it means the run is executing **right now**, in this process or another one. A per-run lock is taken
+before execution and renewed by a heartbeat while it lasts, and a concurrent second call — a
+double-click, two tabs, a retry racing its original — is declined instead of executing a second time.
+Three consequences:
+
+- The response carries `Retry-After`. The *same* request is correct; it is only early. Honour the
+  delay and send it again — it will replay.
+- A process that dies without releasing holds the run only until the lock's TTL expires (default
+  300 000 ms), after which a retry is admitted and replays from the journal.
+- A long run does not time itself out of its own lock: the heartbeat keeps it alive, so the TTL bounds
+  crash recovery, not run length.
+
+A run that has already **finished** does not produce this at all — it replays (see the header above).
+
+**Auth (opt-in, but no silent openness in production):** `createRestApi(config, { auth })` accepts an `AuthProvider` (the free `@gnldev/auth` `roleAuth`, or the paid `@gnldev/auth-ee`) or a backward-compatible `{read, write}` pair. If `auth` is not given, endpoints are open; but under `NODE_ENV=production` this is only possible DELIBERATELY, via `allowOpenAccess: true` — without the flag, setup throws a clear error ("auth required in production"). Outside production, a setup without auth works, with a one-time `console.warn` on the first request, so a silent fail-open cannot survive unnoticed.
+
+**This server is not for browsers.** It is a backend service your own backend calls; your users reach
+your application, and your application reaches this. Nothing here authenticates an end user, and no
+credential below is safe to ship to a client device.
+
+**Which credential your application carries:** `client`, not `admin` — see
+[@gnldev/auth](../auth/README.md) for the four classes. `admin` cancels runs, reads the whole
+organization's history and reads `/usage`; an application that runs agents needs none of that. A
+`client` credential is a whitelist (`agents:run`, `workflow:run`, `run:cancel`, plus reads), so routes
+added in later versions are refused rather than silently granted.
+
+**Every `client` request names the end user it acts for.** One application credential serves many
+users, so `resourceId` in the body (or `?resourceId=` on a read) says which one:
+
+```
+POST /agents/:name/run   { runId, prompt, threadId, resourceId }   → 400 without resourceId
+GET  /runs?resourceId=u-ayse                                       → only that user's runs
+GET  /threads?resourceId=u-ayse                                    → only that user's conversations
+GET  /runs/:id?resourceId=u-mehmet                                 → 403 if the run is someone else's
+```
+
+That id is what keeps two of your users' conversations, memories and runs apart — the memory layer
+scopes on it. Operator credentials may omit it; they work across the organization by design.
+
+## License
+
+Apache-2.0 — see [LICENSE](./LICENSE).

package/dist/edge-errors.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Code by the name of the refusal that prints it. The keys are for readers and for the failure
+ * message in the docs check; the VALUES are the contract — the same string in the HTTP body, in the
+ * SSE `error` frame, and in whatever the client library re-throws.
+ */
+export declare const EDGE_ERROR_CODES: {
+    /** 422, `resumable` — `limits` ceiling met (`server/index.ts`, `sse.ts`, `agui/route.ts`). */
+    readonly runLimitExceeded: "run_limit_exceeded";
+    /** 422, `resumable` — one tool, the same arguments, no progress (same three sites). */
+    readonly toolLoopDetected: "tool_loop_detected";
+    /** 403 — the agent is pending, changed since approval, or blocked (`requireAgentApproval`). */
+    readonly agentNotApproved: "agent_not_approved";
+    /** 403 — `opts.resourceAuth` refused this principal for this agent (the paid FGA layer). */
+    readonly resourceDenied: "resource_denied";
+    /** 402 — the organization's budget is spent; a NEW run is refused, a resume is not. */
+    readonly budgetExceeded: "budget_exceeded";
+    /** 401 — an A2A call arrived without the `x-gnl-signature`/`x-gnl-timestamp` pair. */
+    readonly a2aSignatureMissing: "a2a_signature_missing";
+    /** 401 — the A2A timestamp is outside the ±300s window (replay suspicion). */
+    readonly a2aTimestampInvalid: "a2a_timestamp_invalid";
+    /** 401 — the A2A HMAC did not verify. */
+    readonly a2aSignatureInvalid: "a2a_signature_invalid";
+    /** 500 — a body parser upstream of the handler already drained the request (`node.ts`). */
+    readonly bodyConsumedUpstream: "body_consumed_upstream";
+};
+export type EdgeErrorCode = (typeof EDGE_ERROR_CODES)[keyof typeof EDGE_ERROR_CODES];
+/**
+ * HTTP status per edge code — the docs-checker's source of truth for this family, same contract as
+ * `WIRE_ERROR_STATUS` in @gnldev/durable: routes are pinned to these numbers by their tests, docs
+ * are pinned to them by `check:errors`, and a new code without an entry fails the gate.
+ */
+export declare const EDGE_ERROR_STATUS: Record<string, number>;

package/dist/edge-errors.js

@@ -0,0 +1,71 @@
+// The error codes the HTTP EDGE puts on the wire, in one enumerable place.
+//
+// WHY THIS FILE EXISTS. `@gnldev/durable` already owns two maps — `CALLER_CONFLICT_CODES` and
+// `BLOCKED_ERROR_CODES` — and because they are exported values, `scripts/check-error-pages.mjs`
+// enumerates them and nobody has to remember anything: a new engine code with no page under
+// `docs/errors/` turns the build red in the same commit that invents it. The codes written HERE had
+// no such map. They were string literals spelled at the point of response, and the docs check knew
+// about them only through a hand-written list inside the script itself, which said so out loud:
+// "a fourth literal added at an edge tomorrow is caught by nothing".
+//
+// Measured before this file existed: the list named three codes, and the edge was printing NINE. The
+// six it did not know about — both A2A signature refusals, the timestamp one, `resource_denied`,
+// `budget_exceeded` and `body_consumed_upstream` — had shipped with no page at all. The weak spot was
+// not hypothetical and did not take until tomorrow.
+//
+// WHY IN @gnldev/server RATHER THAN @gnldev/durable. These are route-level facts: an HTTP status is
+// attached to each one, and the engine has no routes and no statuses — putting them next to
+// `RunBusyError` would say the engine produces them, and it does not. Server is also the lowest
+// package that every printer shares: `@gnldev/agui` depends on `@gnldev/server` already (it imports
+// `interruptsFromSteps`), so both edges can read the same constant.
+//
+// Deliberately its own module rather than a block inside `index.ts`: the docs check imports the
+// BUILT value, and importing `dist/index.js` would drag Hono and the whole route table into a
+// documentation script. This file imports nothing.
+//
+// ONE PRINTER IS NOT WIRED TO IT, on purpose: `@gnldev/studio`'s `node.ts` carries its own copy of
+// the `body_consumed_upstream` guard and does NOT depend on `@gnldev/server`, so it keeps the
+// literal. The code is the same string and now has a page; adding a package dependency for one
+// constant would be the more expensive of the two mistakes.
+/**
+ * Code by the name of the refusal that prints it. The keys are for readers and for the failure
+ * message in the docs check; the VALUES are the contract — the same string in the HTTP body, in the
+ * SSE `error` frame, and in whatever the client library re-throws.
+ */
+export const EDGE_ERROR_CODES = {
+    /** 422, `resumable` — `limits` ceiling met (`server/index.ts`, `sse.ts`, `agui/route.ts`). */
+    runLimitExceeded: 'run_limit_exceeded',
+    /** 422, `resumable` — one tool, the same arguments, no progress (same three sites). */
+    toolLoopDetected: 'tool_loop_detected',
+    /** 403 — the agent is pending, changed since approval, or blocked (`requireAgentApproval`). */
+    agentNotApproved: 'agent_not_approved',
+    /** 403 — `opts.resourceAuth` refused this principal for this agent (the paid FGA layer). */
+    resourceDenied: 'resource_denied',
+    /** 402 — the organization's budget is spent; a NEW run is refused, a resume is not. */
+    budgetExceeded: 'budget_exceeded',
+    /** 401 — an A2A call arrived without the `x-gnl-signature`/`x-gnl-timestamp` pair. */
+    a2aSignatureMissing: 'a2a_signature_missing',
+    /** 401 — the A2A timestamp is outside the ±300s window (replay suspicion). */
+    a2aTimestampInvalid: 'a2a_timestamp_invalid',
+    /** 401 — the A2A HMAC did not verify. */
+    a2aSignatureInvalid: 'a2a_signature_invalid',
+    /** 500 — a body parser upstream of the handler already drained the request (`node.ts`). */
+    bodyConsumedUpstream: 'body_consumed_upstream',
+};
+/**
+ * HTTP status per edge code — the docs-checker's source of truth for this family, same contract as
+ * `WIRE_ERROR_STATUS` in @gnldev/durable: routes are pinned to these numbers by their tests, docs
+ * are pinned to them by `check:errors`, and a new code without an entry fails the gate.
+ */
+export const EDGE_ERROR_STATUS = {
+    run_limit_exceeded: 422,
+    tool_loop_detected: 422,
+    agent_not_approved: 403,
+    resource_denied: 403,
+    budget_exceeded: 402,
+    a2a_signature_missing: 401,
+    a2a_timestamp_invalid: 401,
+    a2a_signature_invalid: 401,
+    body_consumed_upstream: 500,
+};
+//# sourceMappingURL=edge-errors.js.map

package/dist/edge-errors.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"edge-errors.js","sourceRoot":"","sources":["../src/edge-errors.ts"],"names":[],"mappings":"AAAA,2EAA2E;AAC3E,EAAE;AACF,8FAA8F;AAC9F,gGAAgG;AAChG,4FAA4F;AAC5F,oGAAoG;AACpG,mGAAmG;AACnG,gGAAgG;AAChG,qEAAqE;AACrE,EAAE;AACF,qGAAqG;AACrG,iGAAiG;AACjG,sGAAsG;AACtG,oDAAoD;AACpD,EAAE;AACF,oGAAoG;AACpG,4FAA4F;AAC5F,gGAAgG;AAChG,oGAAoG;AACpG,oEAAoE;AACpE,EAAE;AACF,gGAAgG;AAChG,8FAA8F;AAC9F,mDAAmD;AACnD,EAAE;AACF,mGAAmG;AACnG,8FAA8F;AAC9F,+FAA+F;AAC/F,4DAA4D;AAE5D;;;;GAIG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG;IAC9B,8FAA8F;IAC9F,gBAAgB,EAAE,oBAAoB;IACtC,uFAAuF;IACvF,gBAAgB,EAAE,oBAAoB;IACtC,+FAA+F;IAC/F,gBAAgB,EAAE,oBAAoB;IACtC,4FAA4F;IAC5F,cAAc,EAAE,iBAAiB;IACjC,uFAAuF;IACvF,cAAc,EAAE,iBAAiB;IACjC,sFAAsF;IACtF,mBAAmB,EAAE,uBAAuB;IAC5C,8EAA8E;IAC9E,mBAAmB,EAAE,uBAAuB;IAC5C,yCAAyC;IACzC,mBAAmB,EAAE,uBAAuB;IAC5C,2FAA2F;IAC3F,oBAAoB,EAAE,wBAAwB;CACtC,CAAC;AAIX;;;;GAIG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAA2B;IACvD,kBAAkB,EAAE,GAAG;IACvB,kBAAkB,EAAE,GAAG;IACvB,kBAAkB,EAAE,GAAG;IACvB,eAAe,EAAE,GAAG;IACpB,eAAe,EAAE,GAAG;IACpB,qBAAqB,EAAE,GAAG;IAC1B,qBAAqB,EAAE,GAAG;IAC1B,qBAAqB,EAAE,GAAG;IAC1B,sBAAsB,EAAE,GAAG;CAC5B,CAAC","sourcesContent":["// The error codes the HTTP EDGE puts on the wire, in one enumerable place.\n//\n// WHY THIS FILE EXISTS. `@gnldev/durable` already owns two maps — `CALLER_CONFLICT_CODES` and\n// `BLOCKED_ERROR_CODES` — and because they are exported values, `scripts/check-error-pages.mjs`\n// enumerates them and nobody has to remember anything: a new engine code with no page under\n// `docs/errors/` turns the build red in the same commit that invents it. The codes written HERE had\n// no such map. They were string literals spelled at the point of response, and the docs check knew\n// about them only through a hand-written list inside the script itself, which said so out loud:\n// \"a fourth literal added at an edge tomorrow is caught by nothing\".\n//\n// Measured before this file existed: the list named three codes, and the edge was printing NINE. The\n// six it did not know about — both A2A signature refusals, the timestamp one, `resource_denied`,\n// `budget_exceeded` and `body_consumed_upstream` — had shipped with no page at all. The weak spot was\n// not hypothetical and did not take until tomorrow.\n//\n// WHY IN @gnldev/server RATHER THAN @gnldev/durable. These are route-level facts: an HTTP status is\n// attached to each one, and the engine has no routes and no statuses — putting them next to\n// `RunBusyError` would say the engine produces them, and it does not. Server is also the lowest\n// package that every printer shares: `@gnldev/agui` depends on `@gnldev/server` already (it imports\n// `interruptsFromSteps`), so both edges can read the same constant.\n//\n// Deliberately its own module rather than a block inside `index.ts`: the docs check imports the\n// BUILT value, and importing `dist/index.js` would drag Hono and the whole route table into a\n// documentation script. This file imports nothing.\n//\n// ONE PRINTER IS NOT WIRED TO IT, on purpose: `@gnldev/studio`'s `node.ts` carries its own copy of\n// the `body_consumed_upstream` guard and does NOT depend on `@gnldev/server`, so it keeps the\n// literal. The code is the same string and now has a page; adding a package dependency for one\n// constant would be the more expensive of the two mistakes.\n\n/**\n * Code by the name of the refusal that prints it. The keys are for readers and for the failure\n * message in the docs check; the VALUES are the contract — the same string in the HTTP body, in the\n * SSE `error` frame, and in whatever the client library re-throws.\n */\nexport const EDGE_ERROR_CODES = {\n  /** 422, `resumable` — `limits` ceiling met (`server/index.ts`, `sse.ts`, `agui/route.ts`). */\n  runLimitExceeded: 'run_limit_exceeded',\n  /** 422, `resumable` — one tool, the same arguments, no progress (same three sites). */\n  toolLoopDetected: 'tool_loop_detected',\n  /** 403 — the agent is pending, changed since approval, or blocked (`requireAgentApproval`). */\n  agentNotApproved: 'agent_not_approved',\n  /** 403 — `opts.resourceAuth` refused this principal for this agent (the paid FGA layer). */\n  resourceDenied: 'resource_denied',\n  /** 402 — the organization's budget is spent; a NEW run is refused, a resume is not. */\n  budgetExceeded: 'budget_exceeded',\n  /** 401 — an A2A call arrived without the `x-gnl-signature`/`x-gnl-timestamp` pair. */\n  a2aSignatureMissing: 'a2a_signature_missing',\n  /** 401 — the A2A timestamp is outside the ±300s window (replay suspicion). */\n  a2aTimestampInvalid: 'a2a_timestamp_invalid',\n  /** 401 — the A2A HMAC did not verify. */\n  a2aSignatureInvalid: 'a2a_signature_invalid',\n  /** 500 — a body parser upstream of the handler already drained the request (`node.ts`). */\n  bodyConsumedUpstream: 'body_consumed_upstream',\n} as const;\n\nexport type EdgeErrorCode = (typeof EDGE_ERROR_CODES)[keyof typeof EDGE_ERROR_CODES];\n\n/**\n * HTTP status per edge code — the docs-checker's source of truth for this family, same contract as\n * `WIRE_ERROR_STATUS` in @gnldev/durable: routes are pinned to these numbers by their tests, docs\n * are pinned to them by `check:errors`, and a new code without an entry fails the gate.\n */\nexport const EDGE_ERROR_STATUS: Record<string, number> = {\n  run_limit_exceeded: 422,\n  tool_loop_detected: 422,\n  agent_not_approved: 403,\n  resource_denied: 403,\n  budget_exceeded: 402,\n  a2a_signature_missing: 401,\n  a2a_timestamp_invalid: 401,\n  a2a_signature_invalid: 401,\n  body_consumed_upstream: 500,\n};\n"]}

package/dist/handler.d.ts

@@ -0,0 +1,65 @@
+import type { Hono } from 'hono';
+/** One mounted route, as `{ method, path }` — see `FetchHandler.routeTable`. */
+export interface RouteInfo {
+    /** Uppercase HTTP method, or `ALL` for a method-agnostic mount. */
+    method: string;
+    /** The registered path pattern, parameters included (`/agents/:name/run`). */
+    path: string;
+}
+/**
+ * NAMED `routeTable`, not `routes`, and that is not a style choice.
+ *
+ * `routes` is Hono's OWN property: `app.route(path, app)` does `app.routes.map((r) => r.handler)`.
+ * A fetch handler is not a Hono instance and `.route()` was never the supported way to mount one —
+ * `.mount()` is — but with a `routes` array present the wrong call SUCCEEDS at boot and then throws
+ * `r.handler is not a function` on every request. Measured against Hono 4.12:
+ *
+ *   routes present  ->  boot OK, every request 500
+ *   routes absent   ->  boot throws "Cannot read properties of undefined (reading 'map')"
+ *
+ * The second is the better failure: unsupported usage should fail where it is written, not on the
+ * first request in production. Colliding with the framework's own name turned a loud boot error into
+ * a quiet one, which is a worse outcome than the introspection is worth.
+ */
+export type FetchHandler = ((request: Request, ...rest: unknown[]) => Promise<Response>) & {
+    fetch: (request: Request, ...rest: unknown[]) => Promise<Response>;
+    /**
+     * Every route this handler serves, deduplicated and sorted. Introspection only — the Hono instance
+     * itself stays hidden, and so do the handler functions.
+     *
+     * Exists so a test can ask the handler what it exposes instead of maintaining a second list by hand.
+     * Every isolation defect this package has shipped had the same shape: a rule applied to the routes
+     * someone was looking at rather than to all of them — the scoped-memory check reached 6 of 9 routes,
+     * the workflow-store refusal 2 of 3, and the third was found by someone re-reading the file. A list
+     * written by hand is a list that goes stale the next time a route is added, which is precisely when
+     * the gap appears. Reading it off the router means a new route shows up in the conformance suite
+     * without anyone remembering to add it.
+     */
+    routeTable: readonly RouteInfo[];
+};
+export declare function toFetchHandler(app: Hono): FetchHandler;
+/**
+ * Reads Hono's route table into a stable, deduplicated inventory.
+ *
+ * Hono registers one entry per handler, so a path with middleware in front of it appears several
+ * times; the conformance suite wants each `method + path` once. Sorted so a snapshot of the inventory
+ * does not churn when a route is moved within the file.
+ *
+ * `ALL` ENTRIES ARE USUALLY MIDDLEWARE. `app.use('*', …)` lands in the same table as a route, recorded
+ * as `ALL /*`, and nothing in the entry distinguishes it from a genuine `app.all('/path')` — the only
+ * observable difference is the handler's arity, which is a coincidence of how it happens to be
+ * written, not a contract. So they are kept, and a caller that DRIVES these entries has to skip them
+ * or it will request the literal path `/*`.
+ *
+ * The reason that warning is here rather than in a note: whether they appear at all depends on
+ * configuration. `@gnldev/server` emits none in any configuration, and `@gnldev/studio` emits none
+ * either until `org` or `auth` is set, at which point one appears. A suite written against a fixture
+ * that has neither turned on never learns the filter is needed, and breaks the first time someone runs
+ * it with auth on. An empty `ALL` list proves nothing about the next fixture.
+ *
+ * Each entry is frozen, not just the array. The same array is handed to every caller, so a single
+ * consumer writing `routes[0].path = …` in place would corrupt the inventory for every later reader —
+ * and the intended consumer is a test suite, which is exactly where that happens. One consequence:
+ * `routeTable.sort(…)` throws (it sorts in place); copy first — `[...routeTable].sort(…)`.
+ */
+export declare function routeInventory(app: Hono): readonly RouteInfo[];

package/dist/handler.js

@@ -0,0 +1,39 @@
+export function toFetchHandler(app) {
+    const call = (request, ...rest) => app.fetch(request, ...rest);
+    return Object.assign(call, { fetch: call, routeTable: routeInventory(app) });
+}
+/**
+ * Reads Hono's route table into a stable, deduplicated inventory.
+ *
+ * Hono registers one entry per handler, so a path with middleware in front of it appears several
+ * times; the conformance suite wants each `method + path` once. Sorted so a snapshot of the inventory
+ * does not churn when a route is moved within the file.
+ *
+ * `ALL` ENTRIES ARE USUALLY MIDDLEWARE. `app.use('*', …)` lands in the same table as a route, recorded
+ * as `ALL /*`, and nothing in the entry distinguishes it from a genuine `app.all('/path')` — the only
+ * observable difference is the handler's arity, which is a coincidence of how it happens to be
+ * written, not a contract. So they are kept, and a caller that DRIVES these entries has to skip them
+ * or it will request the literal path `/*`.
+ *
+ * The reason that warning is here rather than in a note: whether they appear at all depends on
+ * configuration. `@gnldev/server` emits none in any configuration, and `@gnldev/studio` emits none
+ * either until `org` or `auth` is set, at which point one appears. A suite written against a fixture
+ * that has neither turned on never learns the filter is needed, and breaks the first time someone runs
+ * it with auth on. An empty `ALL` list proves nothing about the next fixture.
+ *
+ * Each entry is frozen, not just the array. The same array is handed to every caller, so a single
+ * consumer writing `routes[0].path = …` in place would corrupt the inventory for every later reader —
+ * and the intended consumer is a test suite, which is exactly where that happens. One consequence:
+ * `routeTable.sort(…)` throws (it sorts in place); copy first — `[...routeTable].sort(…)`.
+ */
+export function routeInventory(app) {
+    const seen = new Map();
+    for (const r of app.routes ?? []) {
+        const method = String(r.method).toUpperCase();
+        const key = `${method} ${r.path}`;
+        if (!seen.has(key))
+            seen.set(key, Object.freeze({ method, path: r.path }));
+    }
+    return Object.freeze([...seen.values()].sort((a, b) => (a.path === b.path ? a.method.localeCompare(b.method) : a.path.localeCompare(b.path))));
+}
+//# sourceMappingURL=handler.js.map

package/dist/handler.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"handler.js","sourceRoot":"","sources":["../src/handler.ts"],"names":[],"mappings":"AA6CA,MAAM,UAAU,cAAc,CAAC,GAAS;IACtC,MAAM,IAAI,GAAG,CAAC,OAAgB,EAAE,GAAG,IAAe,EAAE,EAAE,CAAE,GAAG,CAAC,KAAa,CAAC,OAAO,EAAE,GAAG,IAAI,CAAsB,CAAC;IACjH,OAAO,MAAM,CAAC,MAAM,CAAC,IAAI,EAAE,EAAE,KAAK,EAAE,IAAI,EAAE,UAAU,EAAE,cAAc,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;AAC/E,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,UAAU,cAAc,CAAC,GAAS;IACtC,MAAM,IAAI,GAAG,IAAI,GAAG,EAAqB,CAAC;IAC1C,KAAK,MAAM,CAAC,IAAI,GAAG,CAAC,MAAM,IAAI,EAAE,EAAE,CAAC;QACjC,MAAM,MAAM,GAAG,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,WAAW,EAAE,CAAC;QAC9C,MAAM,GAAG,GAAG,GAAG,MAAM,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC;QAClC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC;YAAE,IAAI,CAAC,GAAG,CAAC,GAAG,EAAE,MAAM,CAAC,MAAM,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IAC7E,CAAC;IACD,OAAO,MAAM,CAAC,MAAM,CAAC,CAAC,GAAG,IAAI,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,aAAa,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC;AACjJ,CAAC","sourcesContent":["// What this package hands a host: a request in, a response out — not a Hono instance.\n// See @gnldev/studio/src/handler.ts for the reasoning; the shape is deliberately identical, and\n// structurally compatible, without either package depending on the other.\nimport type { Hono } from 'hono';\n\n/** One mounted route, as `{ method, path }` — see `FetchHandler.routeTable`. */\nexport interface RouteInfo {\n  /** Uppercase HTTP method, or `ALL` for a method-agnostic mount. */\n  method: string;\n  /** The registered path pattern, parameters included (`/agents/:name/run`). */\n  path: string;\n}\n\n/**\n * NAMED `routeTable`, not `routes`, and that is not a style choice.\n *\n * `routes` is Hono's OWN property: `app.route(path, app)` does `app.routes.map((r) => r.handler)`.\n * A fetch handler is not a Hono instance and `.route()` was never the supported way to mount one —\n * `.mount()` is — but with a `routes` array present the wrong call SUCCEEDS at boot and then throws\n * `r.handler is not a function` on every request. Measured against Hono 4.12:\n *\n *   routes present  ->  boot OK, every request 500\n *   routes absent   ->  boot throws \"Cannot read properties of undefined (reading 'map')\"\n *\n * The second is the better failure: unsupported usage should fail where it is written, not on the\n * first request in production. Colliding with the framework's own name turned a loud boot error into\n * a quiet one, which is a worse outcome than the introspection is worth.\n */\nexport type FetchHandler = ((request: Request, ...rest: unknown[]) => Promise<Response>) & {\n  fetch: (request: Request, ...rest: unknown[]) => Promise<Response>;\n  /**\n   * Every route this handler serves, deduplicated and sorted. Introspection only — the Hono instance\n   * itself stays hidden, and so do the handler functions.\n   *\n   * Exists so a test can ask the handler what it exposes instead of maintaining a second list by hand.\n   * Every isolation defect this package has shipped had the same shape: a rule applied to the routes\n   * someone was looking at rather than to all of them — the scoped-memory check reached 6 of 9 routes,\n   * the workflow-store refusal 2 of 3, and the third was found by someone re-reading the file. A list\n   * written by hand is a list that goes stale the next time a route is added, which is precisely when\n   * the gap appears. Reading it off the router means a new route shows up in the conformance suite\n   * without anyone remembering to add it.\n   */\n  routeTable: readonly RouteInfo[];\n}\n\nexport function toFetchHandler(app: Hono): FetchHandler {\n  const call = (request: Request, ...rest: unknown[]) => (app.fetch as any)(request, ...rest) as Promise<Response>;\n  return Object.assign(call, { fetch: call, routeTable: routeInventory(app) });\n}\n\n/**\n * Reads Hono's route table into a stable, deduplicated inventory.\n *\n * Hono registers one entry per handler, so a path with middleware in front of it appears several\n * times; the conformance suite wants each `method + path` once. Sorted so a snapshot of the inventory\n * does not churn when a route is moved within the file.\n *\n * `ALL` ENTRIES ARE USUALLY MIDDLEWARE. `app.use('*', …)` lands in the same table as a route, recorded\n * as `ALL /*`, and nothing in the entry distinguishes it from a genuine `app.all('/path')` — the only\n * observable difference is the handler's arity, which is a coincidence of how it happens to be\n * written, not a contract. So they are kept, and a caller that DRIVES these entries has to skip them\n * or it will request the literal path `/*`.\n *\n * The reason that warning is here rather than in a note: whether they appear at all depends on\n * configuration. `@gnldev/server` emits none in any configuration, and `@gnldev/studio` emits none\n * either until `org` or `auth` is set, at which point one appears. A suite written against a fixture\n * that has neither turned on never learns the filter is needed, and breaks the first time someone runs\n * it with auth on. An empty `ALL` list proves nothing about the next fixture.\n *\n * Each entry is frozen, not just the array. The same array is handed to every caller, so a single\n * consumer writing `routes[0].path = …` in place would corrupt the inventory for every later reader —\n * and the intended consumer is a test suite, which is exactly where that happens. One consequence:\n * `routeTable.sort(…)` throws (it sorts in place); copy first — `[...routeTable].sort(…)`.\n */\nexport function routeInventory(app: Hono): readonly RouteInfo[] {\n  const seen = new Map<string, RouteInfo>();\n  for (const r of app.routes ?? []) {\n    const method = String(r.method).toUpperCase();\n    const key = `${method} ${r.path}`;\n    if (!seen.has(key)) seen.set(key, Object.freeze({ method, path: r.path }));\n  }\n  return Object.freeze([...seen.values()].sort((a, b) => (a.path === b.path ? a.method.localeCompare(b.method) : a.path.localeCompare(b.path))));\n}\n"]}