@xyagent/cli 0.0.1

package/src-shared/logger.mjs

@@ -0,0 +1,167 @@
+// 结构化 JSON 行日志。契约见 agentlink-cli/docs/LOGGING.md。
+//
+// 使用：
+//   import { createLogger } from "../src-shared/logger.mjs";
+//   const log = createLogger({ comp: "bridge", rt: "claude" });
+//   log.info("bridge.start", "bridge starting", { pid: process.pid });
+//   const child = log.child({ session: "agent:u1:::claude-1" });
+//
+// 硬要求：
+//   - 任何未 catch 的异常不能阻断日志输出；logger 本身不能 throw。
+//   - 敏感字段（token/credential/cookie/secret/password/authorization）
+//     在 `meta` 里遇到则替换为 "<redacted>"。
+//   - `text` / `prompt` / `content` 字段长度超 500 → 截断并标记 truncated。
+
+import fs from "node:fs";
+import path from "node:path";
+import os from "node:os";
+import process from "node:process";
+
+const LEVELS = { debug: 10, info: 20, warn: 30, error: 40 };
+
+const SENSITIVE_KEY_RE = /token|credential|cookie|secret|password|authorization|api[_-]?key/i;
+const TRUNCATE_KEYS = new Set(["text", "prompt", "content", "body", "message"]);
+const TRUNCATE_LIMIT = 500;
+
+function resolveLevel(raw) {
+  const v = String(raw || "").trim().toLowerCase();
+  return Object.prototype.hasOwnProperty.call(LEVELS, v) ? v : "info";
+}
+
+function resolveLogDir() {
+  const override = process.env.AGENTLINK_AGENT_LOG_DIR;
+  if (override && override.trim()) return override.trim();
+  return path.join(os.homedir(), ".agentlink", "logs");
+}
+
+function sanitize(value, keyName) {
+  if (value == null) return value;
+  if (typeof value === "string") {
+    if (keyName && TRUNCATE_KEYS.has(keyName) && value.length > TRUNCATE_LIMIT) {
+      return value.slice(0, TRUNCATE_LIMIT);
+    }
+    return value;
+  }
+  if (typeof value !== "object") return value;
+  if (Array.isArray(value)) return value.map((v) => sanitize(v));
+  const out = {};
+  for (const [k, v] of Object.entries(value)) {
+    if (SENSITIVE_KEY_RE.test(k)) {
+      out[k] = "<redacted>";
+      continue;
+    }
+    out[k] = sanitize(v, k);
+    if (k && TRUNCATE_KEYS.has(k) && typeof v === "string" && v.length > TRUNCATE_LIMIT) {
+      out.text_truncated = true;
+    }
+  }
+  return out;
+}
+
+function ensureDir(dir) {
+  try {
+    fs.mkdirSync(dir, { recursive: true });
+    return true;
+  } catch {
+    return false;
+  }
+}
+
+// 日志落盘 —— 用 appendFileSync 而非 createWriteStream，
+// 因为 process.exit() 不会等 stream flush，进程马上死的场景下日志会丢。
+// 日志量低（info 为主），同步 IO 代价可接受。跨平台表现一致。
+//
+// 首次写入时确保目录存在；目录打不开则降级为不落盘（只 stderr）。
+
+// 单文件：`agent-YYYYMMDD.log`。runtime 不进文件名，已在每行的 `rt` 字段里。
+// 按日期滚动，查某天的全部 runtime：`jq . agent-YYYYMMDD.log`
+// 过滤某 runtime：`jq 'select(.rt == "claude")' agent-YYYYMMDD.log`
+
+let resolvedLogPath = null;
+let fileSinkDisabled = false;
+
+function resolveFilePath() {
+  if (fileSinkDisabled) return null;
+  if (resolvedLogPath) return resolvedLogPath;
+  const dir = resolveLogDir();
+  if (!ensureDir(dir)) {
+    fileSinkDisabled = true;
+    return null;
+  }
+  const ymd = new Date().toISOString().slice(0, 10).replace(/-/g, "");
+  resolvedLogPath = path.join(dir, `agent-${ymd}.log`);
+  return resolvedLogPath;
+}
+
+function writeFile(line) {
+  const file = resolveFilePath();
+  if (!file) return;
+  try {
+    fs.appendFileSync(file, line);
+  } catch {
+    fileSinkDisabled = true;
+  }
+}
+
+export function createLogger(baseCtx = {}) {
+  const threshold = LEVELS[resolveLevel(process.env.AGENTLINK_AGENT_LOG_LEVEL)];
+
+  function emit(level, event, msg, extra) {
+    if (LEVELS[level] < threshold) return;
+    const row = {
+      ts: new Date().toISOString(),
+      level,
+      ...baseCtx,
+      event: event || "unknown",
+      msg: msg || "",
+      pid: process.pid,
+      ...sanitize(extra || {}),
+    };
+    let line;
+    try {
+      line = JSON.stringify(row) + "\n";
+    } catch (err) {
+      line = JSON.stringify({
+        ts: row.ts,
+        level: "error",
+        comp: baseCtx.comp || "shared",
+        event: "logger.serialize_error",
+        msg: String(err && err.message ? err.message : err),
+        pid: process.pid,
+      }) + "\n";
+    }
+    // 日志一律走 stderr —— stdout 是业务产出通道（help/version/JSON 响应）。
+    try {
+      process.stderr.write(line);
+    } catch {}
+    writeFile(line);
+  }
+
+  const self = {
+    debug: (event, msg, extra) => emit("debug", event, msg, extra),
+    info: (event, msg, extra) => emit("info", event, msg, extra),
+    warn: (event, msg, extra) => emit("warn", event, msg, extra),
+    error: (event, msg, extra) => emit("error", event, msg, extra),
+    child(patch) {
+      return createLogger({ ...baseCtx, ...patch });
+    },
+    context() {
+      return { ...baseCtx };
+    },
+  };
+  return self;
+}
+
+// 便利方法：logger.safe(() => ...) 包裹任意同步块，异常不冒泡只落日志。
+export function safeRun(logger, where, fn) {
+  try {
+    return fn();
+  } catch (err) {
+    logger.error("error.caught", "uncaught exception", {
+      where,
+      err: err && err.message ? err.message : String(err),
+      stack: err && err.stack ? String(err.stack).split("\n").slice(0, 8).join("\n") : undefined,
+    });
+    return undefined;
+  }
+}

package/src-shared/relay-defaults.json

@@ -0,0 +1,3 @@
+{
+  "defaultRelayUrl": "https://go-relay.xyagent.com"
+}

package/src-shared/relay_revoke.mjs

@@ -0,0 +1,46 @@
+// relay_revoke —— bridge long-poll「服务端已解绑」自清的纯判定逻辑。
+//
+// 抽成共享纯函数，供 bin/agentlink 的 openclaw/hermes bridge 与单测复用：
+//   - 防止有人把 readRelayNextGatewayRequest 的 404 分支「简化」回 fail()
+//     （那样本机配对凭证不会被清，服务管理器重拉后陷入 404 崩溃循环，下次 pair
+//      报「本地状态残留」——正是这个模块要守护的回归）。
+//   - 删除凭证用 **delete** 语义而非轮换：必须让 relayGatewayId 缺失，否则
+//     pair-all 的 readLocalPairState 仍读到残留 gatewayId、探测未绑定、又报残留。
+
+/**
+ * long-poll 取请求时，哪些 HTTP 状态码代表「该 gateway 已被服务端解绑」、
+ * bridge 应当自清本机配对状态：
+ *   401 = bridge token 失效 / 无权
+ *   404 = gateway session 不存在（典型：App 端移除智能体软删 pair_session）
+ *   410 = 资源已 gone
+ * 其余（含 5xx）一律不自清，按瞬态 / 其它错误处理。
+ *
+ * @param {number} status
+ * @returns {boolean}
+ */
+export function isRevokedPollStatus(status) {
+  return status === 401 || status === 404 || status === 410;
+}
+
+/**
+ * 从 agentlink state 对象就地删除指定 runtime 的 relay 配对凭证（delete 语义）。
+ * openclaw / hermes 用不同 key 前缀，二者凭证独立。
+ * 非对象入参原样返回（防御）。
+ *
+ * @param {Record<string, unknown>} state
+ * @param {string} runtime  归一化后的 runtime（'hermes' 走 hermes 前缀，其余按 openclaw）
+ * @returns {Record<string, unknown>} 同一个 state（已就地删除）
+ */
+export function deleteRelayPairCredentials(state, runtime) {
+  if (!state || typeof state !== "object") return state;
+  if (runtime === "hermes") {
+    delete state.hermesRelayGatewayId;
+    delete state.hermesRelayClientToken;
+    delete state.hermesRelayGatewayToken;
+  } else {
+    delete state.relayGatewayId;
+    delete state.relayClientToken;
+    delete state.relayGatewayToken;
+  }
+  return state;
+}

package/src-shared/vendor/README.md

@@ -0,0 +1,60 @@
+# Vendored libraries
+
+`npm_cli` deliberately maintains a **zero-dependency** posture (`package.json`'s
+`dependencies: {}`). To preserve this while needing document-preserving YAML and
+TOML round-trip editing for the MCP runtime fanout adapters (Codex
+`~/.codex/config.toml`, Hermes `~/.hermes/config.yaml`), the relevant libraries
+are vendored under this directory.
+
+## Vendored packages
+
+| Package    | Version | License        | Purpose                                         |
+|------------|---------|----------------|-------------------------------------------------|
+| `yaml`     | 2.5.1   | ISC            | Document-preserving YAML edits (Hermes adapter) |
+| `smol-toml`| 1.4.1   | BSD-3-Clause   | TOML round-trip edits (Codex adapter)           |
+
+Each package directory contains its original `LICENSE`, `package.json`, and
+distribution artifacts (`dist/` etc.), plus a sibling `VENDORED.md` recording
+provenance.
+
+## Importing
+
+Use relative paths from the import site, NOT a bare specifier — bare specifiers
+won't resolve since the packages are not in `node_modules`. Examples:
+
+```js
+// from src-ext/runtime/hermes/mcpConfigAdapter.mjs
+import YAML from "../../../src-shared/vendor/yaml/dist/index.js";
+
+// from src-ext/runtime/codex/mcpConfigAdapter.mjs
+import { parse, stringify } from "../../../src-shared/vendor/smol-toml/dist/index.js";
+```
+
+The actual entry points come from each package's own `package.json` `main` /
+`exports`; check `yaml/package.json` and `smol-toml/package.json` for the
+authoritative entry. The smoke test at `test/vendor/import.test.mjs` validates
+that both packages import + round-trip a sample doc.
+
+## Refreshing
+
+Run the refresh script when a security advisory or upstream patch warrants a
+bump:
+
+```bash
+node scripts/refresh-vendored-libs.mjs --check   # verify pinned sha256s
+node scripts/refresh-vendored-libs.mjs --apply   # re-download + overwrite
+```
+
+The script pins exact versions and verifies tarball sha256 — it will refuse to
+apply if the upstream hash doesn't match the recorded value. To intentionally
+bump a version, edit the pinned versions in the script *and* update the
+expected sha256s, then run `--apply`.
+
+## Security review notes
+
+- Vendoring trades transitive npm supply-chain risk for **manual** review burden.
+  Upgrades are explicit, gated, and visible in PR diffs.
+- These two packages have minimal sub-dependencies (smol-toml has zero; yaml has
+  zero runtime deps too). Each tarball was inspected for unexpected file
+  contents (no postinstall scripts, no native code).
+- Both are MIT-compatible licenses; see each `LICENSE` file.

package/src-shared/vendor/smol-toml/LICENSE

@@ -0,0 +1,24 @@
+Copyright (c) Squirrel Chat et al., All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+3. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software without
+   specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/src-shared/vendor/smol-toml/README.md

@@ -0,0 +1,236 @@
+# smol-toml
+[![TOML 1.0.0](https://img.shields.io/badge/TOML-1.0.0-9c4221?style=flat-square)](https://toml.io/en/v1.0.0)
+[![License](https://img.shields.io/github/license/squirrelchat/smol-toml.svg?style=flat-square)](https://github.com/squirrelchat/smol-toml/blob/mistress/LICENSE)
+[![npm](https://img.shields.io/npm/v/smol-toml?style=flat-square)](https://npm.im/smol-toml)
+[![Build](https://img.shields.io/github/actions/workflow/status/squirrelchat/smol-toml/build.yml?style=flat-square&logo=github)](https://github.com/squirrelchat/smol-toml/actions/workflows/build.yml)
+
+[![GitHub Sponsors](https://img.shields.io/badge/GitHub%20Sponsors-support%20me-EA4AAA?style=flat-square)](https://github.com/sponsors/cyyynthia)
+[![Weekly downloads](https://img.shields.io/npm/dw/smol-toml?style=flat-square)](https://npm.im/smol-toml)
+[![Monthly downloads](https://img.shields.io/npm/dm/smol-toml?style=flat-square)](https://npm.im/smol-toml)
+
+A small, fast, and correct TOML parser and serializer. smol-toml is fully(ish) spec-compliant with TOML v1.0.0.
+
+Why yet another TOML parser? Well, the ecosystem of TOML parsers in JavaScript is quite underwhelming, most likely due
+to a lack of interest. With most parsers being outdated, unmaintained, non-compliant, or a combination of these, a new
+parser didn't feel too out of place.
+
+*[insert xkcd 927]*
+
+Nowadays, smol-toml is the most downloaded TOML parser on npm thanks to its quality. From frameworks to tooling, it
+has been battle-tested and is actively used in production systems.
+
+smol-toml passes most of the tests from the [`toml-test` suite](https://github.com/toml-lang/toml-test); use the
+`run-toml-test.bash` script to run the tests. Due to the nature of JavaScript and the limits of the language,
+it doesn't pass certain tests, namely:
+- Invalid UTF-8 strings are not rejected
+- Certain invalid UTF-8 codepoints are not rejected
+- Certain invalid dates are not rejected
+  - For instance, `2023-02-30` would be accepted and parsed as `2023-03-02`. While additional checks could be performed
+	to reject these, they've not been added for performance reasons.
+
+Please also note that by default, the behavior regarding integers doesn't preserve type information, nor does it allow
+deserializing integers larger than 53 bits. See [Integers](#integers).
+
+You can see a list of all tests smol-toml fails (and the reason why it fails these) in the list of skipped tests in
+`run-toml-test.bash`. Note that some failures are *not* specification violations per-se. For instance, the TOML spec
+does not require 64-bit integer range support or sub-millisecond time precision, but are included in the `toml-test`
+suite. See https://github.com/toml-lang/toml-test/issues/154 and https://github.com/toml-lang/toml-test/issues/155
+
+## Installation
+```
+[pnpm | yarn | npm] i smol-toml
+```
+
+## Usage
+```js
+import { parse, stringify } from 'smol-toml'
+
+const doc = '...'
+const parsed = parse(doc)
+console.log(parsed)
+
+const toml = stringify(parsed)
+console.log(toml)
+```
+
+Alternatively, if you prefer something similar to the JSON global, you can import the library as follows
+```js
+import TOML from 'smol-toml'
+
+TOML.stringify({ ... })
+```
+
+A few notes on the `stringify` function:
+- `undefined` and `null` values on objects are ignored (does not produce a key/value).
+- `undefined` and `null` values in arrays are **rejected**.
+- Functions, classes and symbols are **rejected**.
+- By default, floats will be serialized as integers if they don't have a decimal part. See [Integers](#integers)
+  - `stringify(parse('a = 1.0')) === 'a = 1'`
+- JS `Date` will be serialized as Offset Date Time
+  - Use the [`TomlDate` object](#dates) for representing other types.
+
+### Integers
+When parsing, both integers and floats are read as plain JavaScript numbers, which essentially are floats. This means
+loss of type information, and makes it impossible to safely represent integers beyond 53 bits.
+
+When serializing, numbers without a decimal part are serialized as integers. This allows in most cases to preserve
+whether a number is an integer or not, but fails to preserve type information for numbers like `1.0`.
+
+#### Enabling BigInt support and type preservation
+To parse integers beyond 53 bits, it's possible to tell the parser to return all integers as BigInt. This will
+therefore preserve the type information at the cost of using a slightly more expensive container.
+
+```js
+import { parse } from 'smol-toml'
+
+const doc = '...'
+const parsed = parse(doc, { integersAsBigInt: true })
+```
+
+If you want to keep numbers for integers that can safely be represented as a JavaScript number, you can pass
+`"asNeeded"` instead.
+
+To get end-to-end type preservation, you can tell the serializer to always treat numbers as floating point numbers.
+Then, only BigInts will be serialized as integers and numbers without a decimal part will still be serialized as float.
+
+```js
+import { stringify } from 'smol-toml'
+
+const obj =  { ... }
+const toml = stringify(obj, { numbersAsFloat: true })
+```
+
+### Dates
+`smol-toml` uses an extended `Date` object to represent all types of TOML Dates. In the future, `smol-toml` will use
+objects from the Temporal proposal, but for now we're stuck with the legacy Date object.
+
+```js
+import { TomlDate } from 'smol-toml'
+
+// Offset Date Time
+const date = new TomlDate('1979-05-27T07:32:00.000-08:00')
+console.log(date.isDateTime(), date.isDate(), date.isTime(), date.isLocal()) // ~> true, false, false, false
+console.log(date.toISOString()) // ~> 1979-05-27T07:32:00.000-08:00
+
+// Local Date Time
+const date = new TomlDate('1979-05-27T07:32:00.000')
+console.log(date.isDateTime(), date.isDate(), date.isTime(), date.isLocal()) // ~> true, false, false, true
+console.log(date.toISOString()) // ~> 1979-05-27T07:32:00.000
+
+// Local Date
+const date = new TomlDate('1979-05-27')
+console.log(date.isDateTime(), date.isDate(), date.isTime(), date.isLocal()) // ~> false, true, false, true
+console.log(date.toISOString()) // ~> 1979-05-27
+
+// Local Time
+const date = new TomlDate('07:32:00')
+console.log(date.isDateTime(), date.isDate(), date.isTime(), date.isLocal()) // ~> false, false, true, true
+console.log(date.toISOString()) // ~> 07:32:00.000
+```
+
+You can also wrap a native `Date` object and specify using different methods depending on the type of date you wish
+to represent:
+
+```js
+import { TomlDate } from 'smol-toml'
+
+const jsDate = new Date()
+
+const offsetDateTime = TomlDate.wrapAsOffsetDateTime(jsDate)
+const localDateTime = TomlDate.wrapAsLocalDateTime(jsDate)
+const localDate = TomlDate.wrapAsLocalDate(jsDate)
+const localTime = TomlDate.wrapAsLocalTime(jsDate)
+```
+
+## Performance
+> [!NOTE]
+> These benchmarks are starting to get a bit old. They will be updated in the (hopefully near) future to better
+> reflect numbers of the latest version of smol-toml on the latest version of Node.js.
+
+A note on these performance numbers: in some highly synthetic tests, other parsers such as `fast-toml` greatly
+outperform other parsers, mostly due to their lack of compliance with the spec. For example, to parse a string,
+`fast-toml` skips the entire string while `smol-toml` does validate the string, costing a fair share of performance.
+
+The ~5MB test file used for benchmark here is filled with random data which attempts to be close-ish to reality in
+terms of structure. The idea is to have a file relatively close to a real-world application, with moderately sized
+strings etc.
+
+The large TOML generator can be found [here](https://gist.github.com/cyyynthia/e77c744cb6494dabe37d0182506526b9)
+
+| **Parse**      | smol-toml           | @iarna/toml@3.0.0 | @ltd/j-toml     | fast-toml       |
+|----------------|---------------------|-------------------|-----------------|-----------------|
+| Spec example   | **71,356.51 op/s**  | 33,629.31 op/s    | 16,433.86 op/s  | 29,421.60 op/s  |
+| ~5MB test file | **3.8091 op/s**     | *DNF*             | 2.4369 op/s     | 2.6078 op/s     |
+
+| **Stringify**  | smol-toml            | @iarna/toml@3.0.0 | @ltd/j-toml    |
+|----------------|----------------------|-------------------|----------------|
+| Spec example   | **195,191.99 op/s**  | 46,583.07 op/s    | 5,670.12 op/s  |
+| ~5MB test file | **14.6709 op/s**     | 3.5941 op/s       | 0.7856 op/s    |
+
+<details>
+<summary>Detailed benchmark data</summary>
+
+Tests ran using Vitest v0.31.0 on commit f58cb6152e667e9cea09f31c93d90652e3b82bf5
+
+CPU: Intel Core i7 7700K (4.2GHz)
+
+```
+ RUN  v0.31.0
+
+ ✓ bench/parseSpecExample.bench.ts (4) 2462ms
+     name                hz     min     max    mean     p75     p99    p995    p999     rme  samples
+   · smol-toml    71,356.51  0.0132  0.2633  0.0140  0.0137  0.0219  0.0266  0.1135  ±0.37%    35679   fastest
+   · @iarna/toml  33,629.31  0.0272  0.2629  0.0297  0.0287  0.0571  0.0650  0.1593  ±0.45%    16815
+   · @ltd/j-toml  16,433.86  0.0523  1.3088  0.0608  0.0550  0.1140  0.1525  0.7348  ±1.47%     8217   slowest
+   · fast-toml    29,421.60  0.0305  0.2995  0.0340  0.0312  0.0618  0.0640  0.1553  ±0.47%    14711
+ ✓ bench/parseLargeMixed.bench.ts (3) 16062ms
+     name             hz     min     max    mean     p75     p99    p995    p999     rme  samples
+   · smol-toml    3.8091  239.60  287.30  262.53  274.17  287.30  287.30  287.30  ±3.66%       10   fastest
+   · @ltd/j-toml  2.4369  376.73  493.49  410.35  442.58  493.49  493.49  493.49  ±7.08%       10   slowest
+   · fast-toml    2.6078  373.88  412.79  383.47  388.62  412.79  412.79  412.79  ±2.72%       10
+ ✓ bench/stringifySpecExample.bench.ts (3) 1886ms
+     name                 hz     min     max    mean     p75     p99    p995    p999     rme  samples
+   · smol-toml    195,191.99  0.0047  0.2704  0.0051  0.0050  0.0099  0.0110  0.0152  ±0.41%    97596   fastest
+   · @iarna/toml   46,583.07  0.0197  0.2808  0.0215  0.0208  0.0448  0.0470  0.1704  ±0.47%    23292
+   · @ltd/j-toml    5,670.12  0.1613  0.5768  0.1764  0.1726  0.3036  0.3129  0.4324  ±0.56%     2836   slowest
+ ✓ bench/stringifyLargeMixed.bench.ts (3) 24057ms
+     name              hz       min       max      mean       p75       p99      p995      p999     rme  samples
+   · smol-toml    14.6709   65.1071   79.2199   68.1623   67.1088   79.2199   79.2199   79.2199  ±5.25%       10   fastest
+   · @iarna/toml   3.5941    266.48    295.24    278.24    290.10    295.24    295.24    295.24  ±2.83%       10
+   · @ltd/j-toml   0.7856  1,254.33  1,322.05  1,272.87  1,286.82  1,322.05  1,322.05  1,322.05  ±1.37%       10   slowest
+
+
+ BENCH  Summary
+
+  smol-toml - bench/parseLargeMixed.bench.ts >
+    1.46x faster than fast-toml
+    1.56x faster than @ltd/j-toml
+
+  smol-toml - bench/parseSpecExample.bench.ts >
+    2.12x faster than @iarna/toml
+    2.43x faster than fast-toml
+    4.34x faster than @ltd/j-toml
+
+  smol-toml - bench/stringifyLargeMixed.bench.ts >
+    4.00x faster than @iarna/toml
+    18.33x faster than @ltd/j-toml
+
+  smol-toml - bench/stringifySpecExample.bench.ts >
+    4.19x faster than @iarna/toml
+    34.42x faster than @ltd/j-toml
+```
+
+---
+Additional notes:
+
+I initially tried to benchmark `toml-nodejs`, but the 0.3.0 package is broken.
+I initially reported this to the library author, but the author decided to
+- a) advise to use a custom loader (via *experimental* flag) to circumvent the invalid imports.
+  - Said flag, `--experimental-specifier-resolution`, has been removed in Node v20.
+- b) [delete the issue](https://github.com/huan231/toml-nodejs/issues/12) when pointed out links to the Node.js
+documentation about the flag removal and standard resolution algorithm.
+
+For the reference anyway, `toml-nodejs` (with proper imports) is ~8x slower on both parse benchmark with:
+- spec example: 7,543.47 op/s
+- 5mb mixed: 0.7006 op/s
+</details>

package/src-shared/vendor/smol-toml/VENDORED.md

@@ -0,0 +1,37 @@
+# Vendored: smol-toml@1.4.1
+
+| Field            | Value                                                                |
+|------------------|----------------------------------------------------------------------|
+| Source           | https://registry.npmjs.org/smol-toml/-/smol-toml-1.4.1.tgz           |
+| Version          | 1.4.1                                                                |
+| License          | BSD-3-Clause (see `LICENSE`)                                         |
+| Upstream         | https://github.com/squirrelchat/smol-toml                            |
+| Tarball sha256   | 0e66934cd88d0ba679014f5736b91c87fd816e73a965b1870f8b48d3b4bfe77b     |
+| Vendored on      | 2026-05-21                                                           |
+| Vendor command   | `npm pack smol-toml@1.4.1 && tar xzf smol-toml-1.4.1.tgz`            |
+| Purpose          | TOML round-trip editing for Codex config.toml adapter                |
+
+## Trade-off on comment preservation
+
+`smol-toml` is a minimal TOML 1.0 parser/serializer. It does NOT preserve user
+comments through parse → modify → stringify. The alternatives `@iarna/toml` and
+`@ltd/j-toml` have heavier comment-preservation but introduce more code.
+
+**Decision**: Codex config.toml round-trip via smol-toml; user comments inside
+`[mcp_servers.agentlink]` (if any) are lost on rewrite, BUT comments OUTSIDE
+that section (the rest of the user's Codex config) survive because we only
+write our own section. The Codex adapter SHALL be careful to merge, not full
+rewrite.
+
+If user feedback indicates lost comments are a problem, swap to
+`@iarna/toml` later — adapter API is module-internal, callers won't notice.
+
+## What's used
+
+The Codex MCP config adapter uses:
+- `parse(text)` — returns `Record<string, any>`
+- `stringify(obj)` — emits canonical TOML
+
+## Why pinned
+
+See yaml/VENDORED.md for general policy.

package/src-shared/vendor/smol-toml/dist/date.d.ts

@@ -0,0 +1,41 @@
+/*!
+ * Copyright (c) Squirrel Chat et al., All rights reserved.
+ * SPDX-License-Identifier: BSD-3-Clause
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright notice, this
+ *    list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright notice,
+ *    this list of conditions and the following disclaimer in the
+ *    documentation and/or other materials provided with the distribution.
+ * 3. Neither the name of the copyright holder nor the names of its contributors
+ *    may be used to endorse or promote products derived from this software without
+ *    specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+ * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+export declare class TomlDate extends Date {
+    #private;
+    constructor(date: string | Date);
+    isDateTime(): boolean;
+    isLocal(): boolean;
+    isDate(): boolean;
+    isTime(): boolean;
+    isValid(): boolean;
+    toISOString(): string;
+    static wrapAsOffsetDateTime(jsDate: Date, offset?: string): TomlDate;
+    static wrapAsLocalDateTime(jsDate: Date): TomlDate;
+    static wrapAsLocalDate(jsDate: Date): TomlDate;
+    static wrapAsLocalTime(jsDate: Date): TomlDate;
+}