@sealant/sdk-next 0.0.0-next.0 → 0.39.0-next.682

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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,366 @@
+# @sealant/sdk
+
+The fluent public SDK for Sealant — **create a workspace, run a harness, replay the record.**
+
+```ts
+import { Sealant, opencode } from "@sealant/sdk";
+
+const sealant = new Sealant({ baseUrl: "http://localhost:8080" });
+
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: opencode(),
+});
+
+const run = await workspace.harness.run("Round invoice totals once, after applying the discount.");
+
+await run.record.replay();
+```
+
+## Design
+
+- **Plain-Promise facade over an Effect core.** The default export is ordinary `async`/`await`. The
+  Effect-native core is reachable via the `@sealant/sdk/effect` subpath for consumers that are
+  Effect end-to-end: the contract-derived client as a service, one operation effect per endpoint,
+  and the typed contract errors on the failure channel (no squashing) —
+
+  ```ts
+  import { Effect } from "effect";
+  import { getRunOp, resolveInternalConfig, sealantApiClientLayer } from "@sealant/sdk/effect";
+
+  const layer = sealantApiClientLayer(resolveInternalConfig({ baseUrl: "http://localhost:8080" }));
+
+  const status = getRunOp("run_123").pipe(
+    Effect.map((run) => run.status),
+    Effect.catchTag("RunNotFoundError", () => Effect.succeed("gone" as const)),
+    Effect.provide(layer),
+  );
+  ```
+
+- **Decoupled public types.** The types in [`src/types.ts`](src/types.ts) are hand-written and kept
+  independent of the Effect-core and `@sealant/telemetry` internal shapes, so the public surface
+  stays stable across internal change. The whole surface is typed now, including operations not yet
+  implemented (those reject with `SealantNotImplementedError`).
+- **Harness-neutral.** `opencode()`, `codex()`, `claudeCode()`, and `customHarness()` are thin
+  client values describing how to invoke a harness one-shot.
+
+## Deterministic exec
+
+Run a command in the workspace with no agent in the loop — recorded into a run record like any other
+process:
+
+```ts
+const check = await workspace.exec(["pnpm", "test"], { cwd: "/workspace/repo" });
+check.exitCode; // the check datum — a NONZERO exit RESOLVES (that's the point)
+check.stdout; // full stdout, decoded
+check.run.record; // the durable evidence
+
+// A causal proof is three execs with three recorded exit codes:
+const base = await workspace.exec(["pnpm", "test"]); // fails
+// ...apply the fix...
+const head = await workspace.exec(["pnpm", "test"]); // passes
+```
+
+`exec()` rejects only when the execution machinery itself broke (workspace gone, transport dropped)
+— i.e. when the exit code cannot be trusted. The underlying endpoint
+(`POST /v1/workspaces/:id/exec`) accepts an ordered **list** of commands recorded as one check run;
+the SDK surface starts with the single-command form.
+
+## Typed record events
+
+Timeline reads are discriminated by `kind` — switch on it and `data` narrows to the event's typed
+payload (all 12 recorded kinds: process, io, file, network, runtime, and loss events):
+
+```ts
+for await (const entry of run.record.timeline()) {
+  if (entry.kind === "networkSourceObserved") {
+    entry.data.host; // typed — the raw material of a "sources the agent opened" trail
+    entry.data.status;
+  }
+}
+```
+
+Forward compatibility is a case, not an error: kinds newer than your SDK version (and payloads that
+fail their schema) arrive as `{ kind: "unknown", rawKind, data }` with everything preserved. Wire
+conventions carry through: uint64 fields are decimal strings, protocol enums are numbers.
+
+## Connected-account credentials
+
+Attach the caller's connected Claude / Codex / GitHub accounts to a workspace so the harness
+authenticates as that identity instead of running unauthenticated:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: claudeCode(),
+  credentials: { claude: true, github: "bot-account" },
+});
+```
+
+`true` means "my default account"; a string names a specific connected account. `profile` names a
+profile whose bundled per-provider bindings apply first, and any explicit `claude`/`codex`/`github`
+field wins over the profile's binding for that provider. Only account references cross the SDK
+surface — secret material never does; the control plane resolves references to encrypted credentials
+and injects them at launch.
+
+## Workspace tools and services
+
+Choose a supported operating-system family — `fedora` (the default), `arch`, `nix`, or `ubuntu` —
+request portable package names, and opt into services that need runtime support rather than a
+package install:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: codex(),
+  os: "arch",
+  packages: ["pnpm", "python", "uv", "mise", "github-cli", "lazygit", "bat"],
+  services: { docker: true },
+  credentials: { codex: true, github: true },
+});
+```
+
+`services.docker` installs the Docker client in the image and starts a disposable, workspace-scoped
+rootless daemon at launch. The workspace receives `DOCKER_HOST`; Sealant never mounts the host
+Docker socket. On Kubernetes the daemon is a sidecar of a user-namespaced workspace Pod and the
+operator has to enable it (`workspaces.docker.enabled`); an install that cannot serve it refuses
+`create` with the stable code `workspace-docker-unsupported` (HTTP 422) — map that code to explain
+the gap beside your Docker switch instead of surfacing a launch failure later. GitHub credentials
+provide both `GH_TOKEN` and `GITHUB_TOKEN` to the workspace.
+
+## Workspace environment variables
+
+Ordinary (non-secret) configuration set on the workspace at creation and inherited by every process
+the platform starts inside it — the harness, later shells, exec'd commands, and their descendants:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: codex(),
+  env: { APP_MODE: "review", FEATURE_FLAGS: "checkout,invoices" },
+});
+```
+
+The contract, stated plainly:
+
+- **Not for secrets.** Values are persisted verbatim in the durable workspace spec and are returned
+  by workspace-details APIs to authorized clients for the life of that record. Use `credentials` for
+  connected-account material. There is no partial support: secret-looking names — containing
+  `TOKEN`, `SECRET`, `PASSWORD`, `PASSWD`, `CREDENTIAL`, or `APIKEY` (as a substring, so
+  `TOKENIZER_PATH` counts), ending in `_KEY`, or exactly `KEY` — are rejected at create, because the
+  workspace runtime's secret filter would silently drop them before any process could see them. A
+  loud rejection beats a variable that never arrives.
+- **Validated, client-side and server-side, with the same policy.** Names are
+  `[A-Za-z_][A-Za-z0-9_]*` (max 128 chars); values are any UTF-8 up to 4 KiB (empty and multiline
+  included, NUL excluded); at most 128 entries and 32 KiB total per workspace. Platform-owned names
+  (`SEALANT_*`, `HOME`, `PATH`, `TERM`, `DOCKER_HOST`, proxy variables, loader/shell/
+  runtime-injection controls like `LD_*`, `BASH_ENV`, `NODE_OPTIONS`, `PYTHONPATH`, and Git/SSH
+  config controls) are rejected. The policy is exported (`parseWorkspaceEnv`,
+  `findWorkspaceEnvReservedRule`, `formatWorkspaceEnvIssue`, `WORKSPACE_ENV_*` constants) so your
+  own settings surface can validate with the platform's exact rules.
+- **Fixed at creation.** A live workspace is never mutated; a platform-side restart reuses the
+  stored spec. Caller values can never override platform controls or injected connected-account
+  credentials.
+- **No nested-container injection.** Docker Compose or `docker run` inside the workspace can use the
+  values for interpolation, but child containers receive only what the Compose file or the command
+  explicitly passes (`environment`, `env_file`, `-e`). Docker runtime only.
+
+## Secret environment variables
+
+The half of a real `.env` that `env` deliberately refuses — API keys, database URLs with passwords —
+goes through the **transient secret channel**:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: codex(),
+  env: { APP_MODE: "review" },
+  secretEnv: {
+    DATABASE_URL: "postgres://app:s3cret@db.internal/billing",
+    STRIPE_API_KEY: "sk_live_…",
+  },
+});
+```
+
+What the platform guarantees for `secretEnv`, and how it differs from `env`:
+
+- **Same grammar and size bounds** (`parseWorkspaceSecretEnv`, exported), and the same
+  platform-owned names are reserved — but secret-shaped names are exactly what belongs here.
+  Connected-account names (`GITHUB_TOKEN`, `CLAUDE_CODE_OAUTH_TOKEN`, `GH_TOKEN`) stay reserved:
+  attach those through `credentials`.
+- **Never persisted in the clear.** The map rides the create request beside the spec, is sealed with
+  the install's credential key on the build job, is decrypted by the worker just before launch, and
+  the sealed row is cleared once the launch settles. It is never in the blueprint, the attempt
+  snapshot, `WorkspaceDetails`, or any read API.
+- **Never in `docker run` argv or container env.** The worker stages a `0600` file the workspace
+  daemon reads once at boot and removes it the moment the workspace is ready. `docker inspect` shows
+  a file path, not values.
+- **Inherited by every process the platform starts in the workspace**, winning over `env` and
+  container env for the same name — the harness, later shells, exec'd commands, Services.
+- **Masked in captured output.** Every value seeds the daemon's redactor regardless of its name, so
+  a `DATABASE_URL` a process echoes is recorded as `***REDACTED***`, like a token.
+- **Fixed at creation.** A platform-side _restart_ of the workspace runs **without** secret env (the
+  sealed copy is gone by design); create a new workspace to re-supply it. Docker runtime only;
+  nested containers started by Compose or `docker run` inside the workspace still receive only what
+  you explicitly pass.
+
+Not covered, and worth saying plainly: a process that _deliberately_ writes a secret to a file in
+the repository or to a mount is producing ordinary workspace state, and the redactor masks captured
+I/O, not files.
+
+## Capture-sourced workspaces
+
+A `capture` source (sealantd ADR-0015) mounts nothing and clones nothing. The workspace daemon
+registers with a session channel, fetches the worktree's head plan, materialises it onto the
+executor's own disk, claims the lease, and ships captures back over the channel — so a session can
+run where no host path exists (a Cloudflare sandbox, a MicroVM) and outlive any one executor:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  source: {
+    kind: "capture",
+    endpoint: "https://mend.example.com/session/s1",
+    worktreeId: "wt_1",
+    token: sessionToken, // the channel credential; secret
+    harnessHome: "/workspace/harness-home",
+  },
+  harness: claudeCode(),
+});
+```
+
+- `token` is lifted out of the blueprint and rides the request top level as `captureToken`. The
+  control plane seals it beside `secretEnv` and delivers it through the same boot file, as
+  `SEALANT_CAPTURE_TOKEN`; it is never in the spec, `WorkspaceDetails`, argv, or container env.
+- The channel address and worktree id reach the daemon as `SEALANT_CAPTURE_ENDPOINT` and
+  `SEALANT_CAPTURE_WORKTREE_ID`, with `SEALANT_WORKSPACE_SOURCE=capture`.
+- `worktreeId` is optional. A standby executor launched ahead of any worktree omits it;
+  `SEALANT_CAPTURE_WORKTREE_ID` stays unset and the daemon takes the worktree from the channel's
+  plan answer.
+- `harnessHome` is optional. It names an absolute, normalized directory on the executor's own
+  filesystem. When a captured head contains a `harness/` subtree, cold materialization restores it
+  there. The option does not create or relocate `HOME`, choose an agent state directory, or route
+  harness writes. Configure the harness to write there and, for an empty chain, create the directory
+  before the daemon watcher starts. The daemon then captures that existing directory and keeps using
+  the same path after a standby claim or capture replan. Omitting the option keeps the legacy
+  behavior and captures no harness subtree.
+- `transport` is optional. Without it the daemon dials `endpoint` and every object URL over HTTPS
+  with a certificate the public roots verify, and refuses to boot otherwise. Set
+  `transport.plaintext: true` only when the executor and the channel share a private network;
+  `transport.channelCaPem` and `transport.objectCaPem` name a private CA for each path. The control
+  plane refuses a plain-HTTP endpoint beyond loopback that `plaintext` does not account for, and an
+  endpoint outside the operator's `SEALANT_CAPTURE_ALLOWED_ENDPOINTS`.
+- `harnessHome` is not a host mount. It cannot overlap the workspace working directory, the daemon
+  control directory, or an extra mount target. No mount allowlist applies to the harness root. On
+  Kubernetes the workspace root is an `emptyDir`; on Cloudflare the sandbox is kept alive while the
+  lease is live and a stop sends SIGTERM so the daemon can flush.
+- Harness files receive the existing capture policy. This option does not add automatic credential
+  discovery or change which daemon credentials are excluded from captures.
+- **No restart in place**: the credential is discarded once the launch settles, so `restart()` is
+  refused; create a replacement workspace with a fresh token.
+
+## Dotfiles and shell
+
+Bring your own environment: a login shell and dotfiles applied before the workspace accepts work.
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: codex(),
+  shell: "zsh",
+  dotfiles: {
+    // A repo the platform clones and applies (chezmoi/stow layouts detected, else copied):
+    repository: { url: "github.com/acme/dotfiles" },
+    // And/or caller-resolved archives — a checkout cloned host-side with your own ssh identity,
+    // or a scanned selection of home files, sent as gzipped tars (max 4, ~4MB decoded each):
+    archives: [{ data: tarGzBase64, manager: "copy", bootstrap: false }],
+  },
+});
+```
+
+`shell` installs the shell package and switches the login shell, so `.zshrc`/`.fishrc` actually take
+effect. The `repository` applies first, then each archive in order, so local selections override
+repo files. A failing apply fails the launch loudly rather than handing the agent a half-prepared
+home. Managed OS families only — with `baseImage`, `dotfiles` and non-bash `shell` are rejected
+client-side with the platform's reasoning.
+
+## Custom base images
+
+Instead of a managed OS family, a workspace image can be built from any image reference you already
+trust:
+
+```ts
+const workspace = await sealant.workspaces.create({
+  repository: "github.com/acme/billing-service",
+  harness: codex(),
+  baseImage: "node:22-bookworm",
+});
+```
+
+Distro package installs are skipped entirely — the build overlays only the `sealantd` supervisor
+(PID 1), the harness CLIs (installed with `npm`), and a fully static `socat` (the control-socket
+relay), all copied in as static binaries. This is the **base-image contract**, checked at build time
+with readable failures:
+
+- **Any Linux base, `amd64`/`arm64`**, with a **POSIX shell** at `/bin/sh`. Shells beyond that are
+  not assumed: the workspace login shell is `/bin/sh`, and `defaultShell` selection is not supported
+  with `baseImage`.
+- **Node.js + npm** at or above the harness CLIs' floor (the CLIs are installed with
+  `npm install -g` and run on the base's node).
+- **git**, for clone-, mount- and capture-sourced workspaces.
+
+`packages` still works: names pass through **verbatim** (no portable-name resolution) to the base's
+own package manager — `apt`, `apk`, `dnf`, or `pacman`, autodetected — and the build fails with a
+readable error when the base has none. Dotfiles are not supported with `baseImage`. `baseImage` and
+`os` are mutually exclusive.
+
+## Inference on connected accounts
+
+Run short, tool-calling inference loops on the caller's own subscription — server-side, through the
+official agent SDKs (never raw model-API calls on stored credentials), with the tool loop executed
+on YOUR side:
+
+```ts
+let response = await sealant.inference.respond({
+  prompt: "Compile a review brief from this run record.",
+  tools: [
+    {
+      name: "get_timeline",
+      inputSchema: { type: "object", properties: { runId: { type: "string" } } },
+    },
+  ],
+  responseFormat: { type: "json", schema: briefSchema },
+  credentials: { claude: true },
+});
+
+while (response.turn.type === "toolCalls") {
+  const toolResults = await Promise.all(
+    response.turn.calls.map(async (call) => ({
+      toolCallId: call.toolCallId,
+      content: await runTool(call.name, call.input),
+    })),
+  );
+  response = await sealant.inference.respond({ sessionId: response.sessionId, toolResults });
+}
+
+response.turn.json; // schema-constrained result
+```
+
+Only account references cross the surface — the control plane resolves and decrypts server-side and
+invokes the official Claude Agent SDK with the account's own subscription token. Claude accounts
+only for now (Codex inference is a stated follow-up); sessions are held in memory by the control
+plane and expire after a few idle minutes, so handle a 404 on continuation by restarting the
+exchange.
+
+## Status
+
+The core loop is real: `workspaces.create()`/`get()`/`list()`, `ready()`, blocking `harness.run()`
+and non-blocking `harness.start()` (run execution happens server-side; the SDK is a thin HTTP
+client), deterministic `workspace.exec()`, `inference.respond()` (connected-account inference with a
+caller-executed tool loop), `runs.get()`, and the record read surface — `replay()`, `timeline()`
+(typed, kind-discriminated entries), `scrollback()`, `commands()`, `transcript()`, `stream()`
+(poll-backed), `loss()`, `summary()`, plus captured `changes` (files + diff) settled by
+`run()`/`wait()`. The Effect-native core ships at `@sealant/sdk/effect`.
+
+Still typed stubs pending their read models / endpoints: `artifacts.get()` and the time-travel folds
+`fileTreeAt()`/`processTreeAt()` (Phase 1), and `harness.session()` + workspace lifecycle
+`stop()`/`restart()`/`expire()` (Phase 3).

package/dist/client.d.ts

@@ -0,0 +1,65 @@
+import type { AccessTokensNamespace, ConnectedAccountsNamespace, CreateOptions, InferenceNamespace, ListOptions, Run, SshKeysNamespace, Workspace, WorkspaceCreateState, WorkspaceSshNamespace, SealantConfig, UsersNamespace } from "./types.js";
+export declare class Sealant {
+    #private;
+    constructor(config: SealantConfig);
+    /** The configured control-plane base URL. */
+    get baseUrl(): string;
+    /** Workspace lifecycle: create, fetch, and list live environments. */
+    readonly workspaces: {
+        create: (options: CreateOptions) => Promise<Workspace>;
+        get: (id: string) => Promise<Workspace>;
+        /**
+         * The owner's workspace a `create({ idempotencyKey })` made, or `null`: what a caller that
+         * lost a create's answer uses to find the executor it started.
+         */
+        findByIdempotencyKey: (idempotencyKey: string) => Promise<Workspace | null>;
+        /**
+         * What became of the create with this idempotency key: `pending` (started, not committed),
+         * `found` (committed: `workspaceId`, `runId`, `launchId`), `cancelled`, or `none` (nothing has
+         * reached the control plane — as of now only; use `cancelCreate` for an answer that stays
+         * true).
+         */
+        createState: (idempotencyKey: string) => Promise<WorkspaceCreateState>;
+        /**
+         * Make sure the create with this idempotency key never launches: a pending or unknown key is
+         * cancelled for good (a delayed original request with it is refused, `create-cancelled`). A
+         * create that already committed answers `found` — stop that workspace instead.
+         */
+        cancelCreate: (idempotencyKey: string) => Promise<WorkspaceCreateState>;
+        list: (options?: ListOptions | undefined) => Promise<readonly Workspace[]>;
+    };
+    /**
+     * Inference on connected accounts — server-side via the official agent SDKs, never raw model-API
+     * calls. Tool calls park server-side; execute them here and `respond()` with the results.
+     */
+    readonly inference: InferenceNamespace;
+    /**
+     * Scoped bearer tokens for the session surface — `session:read` / `session:input` /
+     * `workspace:exec`. The returned secret is shown once; hand it to a client as its `apiKey` and
+     * the session endpoints enforce exactly those scopes (a read-stream token can stream but is
+     * rejected for input and exec).
+     */
+    /** Identity rows for products that own their own login (one client per user afterwards). */
+    readonly users: UsersNamespace;
+    /** This client's owner's Claude / Codex / GitHub accounts. Secrets go in; none come out. */
+    readonly connectedAccounts: ConnectedAccountsNamespace;
+    /**
+     * Where workspace SSH connects for this deployment — how an editor (VS Code Remote-SSH) or
+     * plain `ssh` reaches a workspace. Destination: `<usernamePrefix>-<workspaceId>@<host>:<port>`;
+     * the gateway authorizes each connection from the offered key's owning account.
+     */
+    readonly workspaceSsh: WorkspaceSshNamespace;
+    /**
+     * The owner's SSH public keys — what the workspace SSH gateway resolves a connection to.
+     * `ensure` is idempotent: re-offering the same key returns the existing row.
+     */
+    readonly sshKeys: SshKeysNamespace;
+    readonly accessTokens: AccessTokensNamespace;
+    /** Runs by id — so a record can be replayed long after its workspace is gone. */
+    readonly runs: {
+        get: (runId: string) => Promise<Run>;
+    };
+    /** Release resources held by the client (the Effect runtime scope: DB pool, daemon connections). */
+    close(): Promise<void>;
+    [Symbol.asyncDispose](): Promise<void>;
+}