agenticreplay 0.1.0 → 0.1.2

package/packages/cli/dist/upstream.js

@@ -0,0 +1,41 @@
+import { unusableOrigin } from '@agenticreplay/proxy';
+import { gatewayHeaders, readConfig, resolveUpstream, sameOrigin } from './config.js';
+export async function upstreamPlan(args, env = process.env) {
+    const config = await readConfig(env);
+    const upstream = await resolveUpstream(args, env);
+    // Refused here, because here is where all three sources meet: `--upstream-*`,
+    // `AGENTICREPLAY_UPSTREAM_*`, and the gateway from the config file. `agenticreplay setup` refuses one on the way
+    // in, but a config written before it did, a hand-edited one, an environment variable and a flag
+    // all still arrive unchecked — and on the record path an origin is not only sent, it is
+    // *printed*: `distinctOrigins` renders it on the recording line, and an origin `doFetch` cannot
+    // parse comes back inside undici's TypeError, which the proxy hands to the agent as a 500 body.
+    // Neither sink can be made safe by scrubbing alone, because `recordableOrigin` answers with a
+    // value for a scheme-less URL whose username parses as the protocol. Refusing closes both.
+    for (const [dialect, origin] of Object.entries(upstream ?? {})) {
+        const problem = unusableOrigin(origin);
+        if (problem === undefined)
+            continue;
+        throw new Error(`the upstream for ${dialect} is not an origin agenticreplay can use: ${problem}` +
+            '\n  give it as scheme, host and path: --upstream-openai https://gateway.example/v1' +
+            '\n  read in order: --upstream-*, then AGENTICREPLAY_UPSTREAM_*, then the gateway from agenticreplay setup');
+    }
+    const headers = gatewayHeaders(config, env);
+    // Unanimity, not `some`. `upstreamHeaders` are attached to every live call the proxy makes —
+    // there is no per-dialect header channel — so if any origin we might reach is not the gateway,
+    // attaching the key sends it there. A `.some()` check passed whenever *one* dialect still
+    // defaulted to the gateway, which is exactly what happens when a flag redirects the other: the
+    // gateway's credential went to api.anthropic.com. Verified against the built CLI.
+    //
+    // Erring towards withholding costs an unauthenticated request and a clear 401. Erring the other
+    // way hands a third party a key they were never meant to see, and nothing says it happened.
+    const origins = Object.values(upstream ?? {});
+    const goingToGateway = config.gateway?.url !== undefined &&
+        origins.length > 0 &&
+        origins.every((origin) => sameOrigin(origin, config.gateway.url));
+    return {
+        upstream,
+        headers: goingToGateway && Object.keys(headers).length > 0 ? headers : undefined,
+        headersOrigin: goingToGateway ? config.gateway.url : undefined,
+    };
+}
+//# sourceMappingURL=upstream.js.map

package/packages/cli/dist/upstream.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"upstream.js","sourceRoot":"","sources":["../src/upstream.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AACtD,OAAO,EAAE,cAAc,EAAE,UAAU,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AA6BtF,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,IAAgB,EAChB,MAAyB,OAAO,CAAC,GAAG;IAEpC,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC,GAAG,CAAC,CAAC;IACrC,MAAM,QAAQ,GAAG,MAAM,eAAe,CAAC,IAAI,EAAE,GAAG,CAAC,CAAC;IAElD,8EAA8E;IAC9E,iHAAiH;IACjH,gGAAgG;IAChG,wFAAwF;IACxF,gGAAgG;IAChG,gGAAgG;IAChG,8FAA8F;IAC9F,2FAA2F;IAC3F,KAAK,MAAM,CAAC,OAAO,EAAE,MAAM,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,QAAQ,IAAI,EAAE,CAAC,EAAE,CAAC;QAC/D,MAAM,OAAO,GAAG,cAAc,CAAC,MAAM,CAAC,CAAC;QACvC,IAAI,OAAO,KAAK,SAAS;YAAE,SAAS;QACpC,MAAM,IAAI,KAAK,CACb,oBAAoB,OAAO,4CAA4C,OAAO,EAAE;YAC9E,oFAAoF;YACpF,2GAA2G,CAC9G,CAAC;IACJ,CAAC;IACD,MAAM,OAAO,GAAG,cAAc,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAC5C,6FAA6F;IAC7F,+FAA+F;IAC/F,0FAA0F;IAC1F,+FAA+F;IAC/F,kFAAkF;IAClF,EAAE;IACF,gGAAgG;IAChG,4FAA4F;IAC5F,MAAM,OAAO,GAAG,MAAM,CAAC,MAAM,CAAC,QAAQ,IAAI,EAAE,CAAC,CAAC;IAC9C,MAAM,cAAc,GAClB,MAAM,CAAC,OAAO,EAAE,GAAG,KAAK,SAAS;QACjC,OAAO,CAAC,MAAM,GAAG,CAAC;QAClB,OAAO,CAAC,KAAK,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,UAAU,CAAC,MAAM,EAAE,MAAM,CAAC,OAAQ,CAAC,GAAG,CAAC,CAAC,CAAC;IACrE,OAAO;QACL,QAAQ;QACR,OAAO,EAAE,cAAc,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,SAAS;QAChF,aAAa,EAAE,cAAc,CAAC,CAAC,CAAC,MAAM,CAAC,OAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,SAAS;KAChE,CAAC;AACJ,CAAC"}

package/packages/cli/dist/version.d.ts

@@ -0,0 +1,2 @@
+export declare const AGENTICREPLAY_VERSION: string;
+//# sourceMappingURL=version.d.ts.map

package/packages/cli/dist/version.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../src/version.ts"],"names":[],"mappings":"AAkBA,eAAO,MAAM,qBAAqB,EAAE,MAE3B,CAAC"}

package/packages/cli/dist/version.js

@@ -0,0 +1,18 @@
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+/**
+ * Read from the manifest rather than restating it.
+ *
+ * This was a hardcoded constant, and `npm version --workspaces` does not touch source, so 0.2.0
+ * shipped reporting 0.1.2 — from `--version`, from the MCP server's `serverInfo`, and into
+ * `manifest.agenticreplay_version` on every trace it wrote. A recording that misreports the version that
+ * produced it is a provenance bug, not a cosmetic one.
+ *
+ * `../package.json` resolves the same way in all three places this is loaded from:
+ * `dist/version.js` in the published package, `dist/version.js` in the repo, and `src/version.ts`
+ * under vitest — each is exactly one directory below `packages/cli/package.json`, and npm always
+ * ships the manifest.
+ */
+const manifest = fileURLToPath(new URL('../package.json', import.meta.url));
+export const AGENTICREPLAY_VERSION = JSON.parse(readFileSync(manifest, 'utf8')).version;
+//# sourceMappingURL=version.js.map

package/packages/cli/dist/version.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"version.js","sourceRoot":"","sources":["../src/version.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC;;;;;;;;;;;;GAYG;AACH,MAAM,QAAQ,GAAG,aAAa,CAAC,IAAI,GAAG,CAAC,iBAAiB,EAAE,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAE5E,MAAM,CAAC,MAAM,qBAAqB,GAChC,IAAI,CAAC,KAAK,CAAC,YAAY,CAAC,QAAQ,EAAE,MAAM,CAAC,CAC1C,CAAC,OAAO,CAAC"}

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agenticreplay",
-  "version": "0.5.0",
+  "version": "0.1.2",
   "mcpName": "io.github.askdkc/agenticreplay",
   "type": "module",
   "license": "Apache-2.0",
@@ -37,15 +37,15 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "@agenticreplay/schema": "0.5.0",
-    "@agenticreplay/plugin-api": "0.5.0",
-    "@agenticreplay/core": "0.5.0",
-    "@agenticreplay/proxy": "0.5.0",
-    "@agenticreplay/providers": "0.5.0",
-    "@agenticreplay/adapters": "0.5.0",
-    "@agenticreplay/fs-capture": "0.5.0",
-    "@agenticreplay/viewer": "0.5.0",
-    "@agenticreplay/mcp-shim": "0.5.0",
-    "@agenticreplay/shell-shim": "0.5.0"
+    "@agenticreplay/schema": "0.1.2",
+    "@agenticreplay/plugin-api": "0.1.2",
+    "@agenticreplay/core": "0.1.2",
+    "@agenticreplay/proxy": "0.1.2",
+    "@agenticreplay/providers": "0.1.2",
+    "@agenticreplay/adapters": "0.1.2",
+    "@agenticreplay/fs-capture": "0.1.2",
+    "@agenticreplay/viewer": "0.1.2",
+    "@agenticreplay/mcp-shim": "0.1.2",
+    "@agenticreplay/shell-shim": "0.1.2"
   }
 }

package/.dockerignore

@@ -1,11 +0,0 @@
-.git
-node_modules
-**/node_modules
-**/dist
-**/*.tsbuildinfo
-**/__pycache__
-**/build
-**/.venv
-.agenticreplay
-prompt
-companion-kiokuko-dsh.patch

package/.gitattributes

@@ -1,19 +0,0 @@
-# A trace is evidence, and its integrity is a byte hash over the file. Git's newline conversion
-# rewrites those bytes on a Windows checkout, so a freshly cloned example fails its own integrity
-# check for a reason that has nothing to do with the reader. Before this file existed, every trace
-# under examples/ arrived with CRLF on Windows and `verify_integrity()` returned False on a run
-# that was intact in the repository — the failure mode this project exists to rule out.
-
-# Normalise to LF in the index and check out LF everywhere. The tooling, the tests and the trace
-# format all assume LF; nothing here wants CRLF.
-* text=auto eol=lf
-
-# Content-addressed. Never rewritten, in either direction.
-examples/traces/** -text
-packages/*/fixtures/** -text
-packages/*/test/fixtures/** -text
-
-*.png binary
-*.jpg binary
-*.gz binary
-*.zip binary

package/.github/workflows/ci.yml

@@ -1,146 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-  workflow_dispatch:
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  check:
-    name: check (node ${{ matrix.node }})
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        node: ['24', '26']
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node }}
-          cache: npm
-      - uses: actions/setup-python@v5
-        with: { python-version: '3.12' }
-      - run: npm ci
-      - run: npm run fmt:check
-      - run: npx tsc --build
-      - run: npx vitest run --reporter=verbose
-
-  conformance:
-    name: trace format conformance
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with: { node-version: '24', cache: npm }
-      - run: npm ci
-      - run: npx tsc --build
-      # Every example trace shipped in the repo must validate against the normative schema.
-      # This is what makes the format a format rather than whatever the writer happens to emit.
-      - run: node scripts/conformance.mjs
-      # "Replay is reliable" as a number that regresses visibly rather than as a sentence. The
-      # budgets live beside the corpus in the script; a change that costs fidelity fails here.
-      - run: node scripts/fidelity.mjs --check
-
-  integrations:
-    name: framework integrations
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '24'
-          cache: 'npm'
-      - uses: actions/setup-python@v5
-        with:
-          python-version: '3.12'
-      - run: npm ci
-      - run: npx tsc --build
-      # The frameworks this speaks for. A check whose package is missing is skipped rather than
-      # failed, so a contributor can run the suite without all of them.
-      - run: >
-          pip install openai anthropic litellm langgraph langchain-openai browser-use haystack-ai
-          crewai openai-agents openhands-sdk llama-index-core llama-index-llms-openai
-      # Mastra is the one framework here that is JS, and it is 130 MB — more than this repo's whole
-      # dependency tree. `--no-save` keeps it out of package.json so it costs this job and nothing
-      # else: no npm ci anywhere else gets slower, and a contributor who has not run this line gets
-      # a skip rather than a failure, exactly as the pip line above behaves.
-      - run: npm install --no-save @mastra/core @ai-sdk/openai ai
-      # From the tree, not PyPI: the `openai-agents-handoff` and `langgraph-nodes` checks exist to
-      # prove the adapters in *this* commit work, and installing a published copy would test the
-      # last release instead.
-      - run: pip install -e python-openai-agents
-      - run: pip install -e python-langgraph
-      # `--require-all`, because installing them above was never what enforced it. Two checks were
-      # added without a line here and CI stayed green on the skips, while the README said "in CI"
-      # about both. A skip is now a failure on this runner, so forgetting the line above fails
-      # loudly instead of quietly making a claim untrue.
-      - run: node test/integrations/run.mjs --require-all
-      # Not part of the matrix: this records nothing and replays nothing. It asks CrewAI which model
-      # names it resolves and fails if the answer has drifted from what `docs/integrations.md` says.
-      # It exists because that claim was wrong once — the measurement behind it used a model name no
-      # known-model list contains, and read the refusal as being about the prefix.
-      - run: python test/integrations/agents/crewai_model_names.py
-        working-directory: .
-        env:
-          OPENAI_API_KEY: unused-but-crewai-wants-one
-      # Same shape, same reason: LlamaIndex refuses any model name outside a list compiled into it,
-      # before a request is made. That is a real limit on pointing it at a gateway, `docs/integrations.md`
-      # now says so, and this is what fails when it stops being true.
-      - run: python test/integrations/agents/llama_index_model_names.py
-        working-directory: .
-
-  python-sdk:
-    name: python sdk
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
-        with: { python-version: '3.11' }
-      # The SDK itself has no runtime dependencies and is meant to keep it that way, but the test
-      # runner is not the SDK: setup-python provides a clean interpreter with no pytest on it.
-      # Installing the package rather than running pytest against the source tree also checks that
-      # `pip install agenticreplay-trace` actually works, which is how anyone will really get it.
-      - run: pip install ./python[dev]
-      - run: python -m pytest python/ -q
-      # The second Python distribution in this tree. It was added with tests and with a `pip install
-      # -e` in the integrations job, and nothing ran them — the same shape as the skipped checks
-      # that job now fails on, one layer out. Its `[dev]` extra brings the Agents SDK, because two
-      # of its tests are about how `install()` registers with it.
-      - run: pip install ./python-openai-agents[dev]
-      - run: python -m pytest python-openai-agents/ -q
-      # The third. Its `[dev]` extra brings langgraph and langchain-core, because the half of its
-      # suite that matters builds real graphs and invokes them — the unit tests assert what
-      # langchain-core is believed to pass, and only a real graph keeps that belief honest.
-      - run: pip install ./python-langgraph[dev]
-      - run: python -m pytest python-langgraph/ -q
-
-  plugin-api-neutrality:
-    name: plugin API neutrality
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with: { node-version: '24', cache: npm }
-      - run: npm ci
-      # A vendor plugin must reach AgenticReplay only through the published interface.
-      # If this ever fails, a plugin has grown a privileged path into the core.
-      - run: node scripts/check-neutrality.mjs
-
-  distributions:
-    name: installed npm packages and Docker
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with: { node-version: '24', cache: npm }
-      - run: npm ci
-      - run: npm run build
-      - run: node scripts/installed-smoke.mjs
-      - run: docker build -t agenticreplay-local .
-      - run: docker run --rm --entrypoint agenticreplay agenticreplay-local --version

package/.grok-plugin/plugin.json

@@ -1,12 +0,0 @@
-{
-  "name": "agenticreplay",
-  "version": "0.2.2",
-  "description": "Record, inspect, replay and fork coding-agent runs: read what an agent actually did from the evidence of its run, offline.",
-  "author": {
-    "name": "Continuum AI Corp",
-    "url": "https://github.com/Continuum-AI-Corp"
-  },
-  "repository": "https://github.com/askdkc/AgenticReplay",
-  "license": "Apache-2.0",
-  "keywords": ["agenticreplay", "agent run replay", "agent trace", "record agent run"]
-}

package/.mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "agenticreplay": {
-      "command": "npx",
-      "args": ["-y", "agenticreplay", "mcp"]
-    }
-  }
-}

package/.prettierignore

@@ -1,4 +0,0 @@
-dist/
-node_modules/
-*.md
-examples/

package/.prettierrc.json

@@ -1 +0,0 @@
-{ "singleQuote": true, "printWidth": 100, "semi": true, "trailingComma": "all" }

package/CONTRIBUTING.md

@@ -1,106 +0,0 @@
-# Contributing to AgenticReplay
-
-## The five-minute dev loop
-
-```console
-git clone https://github.com/askdkc/AgenticReplay
-cd AgenticReplay
-npm install
-npm run check     # format check + typecheck + tests
-```
-
-`npm run check` is the fast loop — format check, typecheck, tests — and it is the first CI job, but
-it is not all of CI. Three more jobs run commands `check` does not:
-
-```console
-node scripts/conformance.mjs      # the shipped example traces and a freshly written one both
-                                  # validate against the normative schema
-node scripts/check-neutrality.mjs # no vendor plugin reaches past @agenticreplay/plugin-api
-pip install ./python[dev] && python -m pytest python/ -q   # the Python SDK
-```
-
-`conformance.mjs` reads `packages/*/dist`, so run it after a build — `npm run check` has already
-done one by the time you get there.
-
-Run those four on Node 24 and Node 26; CI exercises both runtime lines.
-
-The published CLI and the development toolchain both require Node 24 or newer. The root
-`package.json` declares `>=24.0.0`, so `npm ci` reports an unsupported runtime immediately.
-
-Working on one package:
-
-```console
-npx vitest run packages/core      # one package
-npx vitest                        # watch mode, everything
-npx tsc --build                   # typecheck the project graph
-```
-
-If that took longer than five minutes on a clean machine, that is a bug — please open an issue
-saying where it stalled. Time-to-first-contribution is a metric we actually track.
-
-## Tests come first
-
-This project is built test-first, and not as a slogan: the payload schema, the checkpoint snapping
-rules and the redactor all had real bugs caught by a test written before the implementation.
-
-Write the failing test, run it, confirm it fails **for the reason you expect**, then implement.
-A test that has never been red has not proven anything.
-
-## What we are looking for
-
-The highest-value contributions, in order:
-
-1. **Adapters** — support for an agent harness we do not cover. `packages/adapters/` has the
-   pattern; the interface is two methods.
-2. **Providers** — a model API we cannot fork onto. `packages/providers/` has two examples.
-3. **Redaction rules** — a secret shape we fail to catch. These are small, self-contained, and
-   they protect everyone.
-4. **Trace analyzers** — anything that reads a trace and finds something useful. The loop detector
-   in `packages/viewer/src/render.ts` is the model: about forty lines, no privileged access.
-
-## Rules of the road
-
-- **No new runtime dependencies** without discussion. The CLI has none beyond a JSON Schema
-  validator, and a debugger you install to diagnose a broken environment should not drag in a
-  hundred packages. `devDependencies` are easier, but still argue for them.
-- **The spec is normative.** `spec/agenticreplay-trace-v0.md` and the JSON Schema come first; TypeScript
-  types are verified against them. If you need a format change, change the spec in the same PR and
-  bump the schema version. Adding an event type is a MINOR bump; changing one is MAJOR.
-- **Readers skip what they do not understand.** Never make an unknown event type an error.
-- **Replay never silently approximates.** If a match is inexact, emit a `divergence` event. A
-  debugger that quietly guesses is worse than no debugger, because you will believe it.
-- **Secrets never reach disk or a TTY.** Redaction lives in the write path. If you add a new sink,
-  it goes through the redactor. If it *cannot* — anything written by the agent's own process, or by
-  a child of it, is on disk before agenticreplay sees it — then ask one question first: **does anything read
-  this file after the run?**
-  - No: it is a transport, not part of the trace. Keep it out of the run directory, write an
-    allow-list of the fields something actually reads rather than whatever the payload holds, and
-    delete it once it has been read. `shell-frames.jsonl` and the agent-spans file are both this.
-  - Yes: it stays, and it is unredacted material in a directory people share. Say so in
-    SECURITY.md, and make sure `agenticreplay scrub` at least *searches* it — a scrubber that reports
-    "nothing matched" over a file it never opened is the one failure mode SECURITY.md says it must
-    not have. `mcp-frames.jsonl` is this: a replay answers from it, and rewriting a frame changes
-    the key it is looked up by, so a scrub that edited it would make the replay serve a different
-    recorded response rather than fail.
-- **A new field is a new sink.** The redactor works on payloads derived from the incoming request,
-  so a value sourced from anywhere else — configuration, a flag, an environment variable — arrives
-  having bypassed it. Adding an attribute, ask where its value comes from and whether that source
-  can carry a credential; `agenticreplay setup --gateway` accepts any URL, and `https://user:pw@gw` and
-  `https://gw?key=…` are both ordinary ways to configure a gateway. This was learned the hard way:
-  a field naming the origin that answered each call was verified four ways, all of them asking
-  whether the value was *correct* and none asking what else could be in it. Review caught it.
-  `packages/cli/test/no-credential-in-attrs.test.ts` is the part that cannot be forgotten — it
-  walks every attribute of every event and fails on the shape, whatever the field is called.
-
-## Sign your commits
-
-We use the [Developer Certificate of Origin](https://developercertificate.org/). Add a `Signed-off-by`
-line with `git commit -s`. There is no CLA and no copyright assignment.
-
-**This one is honour-system.** No CI job checks for the trailer and no bot will ask you for it, so a
-PR without one is not blocked — we would rather tell you that than have you discover it from a
-green tick. If we ever start enforcing it, it will be a check you can see, not a surprise on merge.
-
-## Code of conduct
-
-By participating you agree to the [Contributor Covenant](CODE_OF_CONDUCT.md).

package/Dockerfile

@@ -1,30 +0,0 @@
-# Ships only the MCP server, not the recorder.
-#
-# Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git
-# index. None of that survives a container boundary, so `agenticreplay record` inside here would watch an
-# empty namespace. What does travel is the read side: the six MCP tools serve runs that already
-# exist on disk, so a client mounts its `.agenticreplay` directory and reads it.
-#
-#   docker run -i --rm -v "$PWD/.agenticreplay:/work/.agenticreplay:ro" agenticreplay
-#
-# Read-only is deliberate. `agenticreplay replay` and `agenticreplay compare` execute a real agent and can spend
-# money, so a container that only ever reads is the honest default; drop `:ro` if you mean to
-# fork from in here.
-FROM node:24-alpine AS build
-WORKDIR /src
-COPY . .
-RUN npm ci && npm run build \
-    && mkdir /artifacts \
-    && npm pack --workspaces --pack-destination /artifacts
-
-FROM node:24-alpine
-
-ENV NODE_ENV=production
-WORKDIR /work
-
-# Install every matching workspace tarball from this checkout, including unpublished renamed packages.
-COPY --from=build /artifacts /artifacts
-RUN npm install -g --omit=dev /artifacts/*.tgz && rm -rf /artifacts
-
-# stdio transport — the client owns stdin/stdout, so no port is exposed.
-ENTRYPOINT ["agenticreplay", "mcp"]

package/MAINTAINERS.md

@@ -1,24 +0,0 @@
-# Maintainers
-
-| Area | Maintainer |
-|---|---|
-| Trace format & core | @Continuum-AI-Corp |
-| Proxy & replay | @Continuum-AI-Corp |
-| Adapters & providers | @Continuum-AI-Corp |
-| Viewer | @Continuum-AI-Corp |
-
-## Governance
-
-Today this is maintainer-led: the people above merge changes and cut releases.
-
-**The path out of that is written down on purpose.** Once three maintainers from outside the
-founding organisation are active, we form a technical steering committee with a published charter,
-and format changes require its consent rather than ours. Ambiguity about who controls an open
-format is a reason not to build on it, so we would rather commit to the trigger now than be asked
-about it later.
-
-## Becoming a maintainer
-
-Sustained, high-quality contribution in an area, plus the judgement to say no to changes that widen
-the surface. Adapters and providers are the usual route in. Ask — we would rather have the
-conversation early than have you guess.