@qilin-agent/cli 3.1.3 → 3.1.4

package/README.i18n.yaml

@@ -2,21 +2,21 @@
 # section, a hash of its English and Chinese blocks outside code blocks and generated regions.
 # After editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write apps/cli/README.md
-/qilin-cli:
-  en: 30f6f6d09ef3f96b
-  zh: 9215ee1c45f8a0f6
-/qilin-cli/entry-modes:
-  en: 8f3f0fe760a8a5aa
-  zh: 1a5566f392aa3161
-/qilin-cli/app-arguments:
+/qilin-agent-cli:
+  en: 063f13813a8fa190
+  zh: 682d157e19163ff0
+/qilin-agent-cli/entry-modes:
+  en: cebfeaa9a9e60c00
+  zh: 652208729fa392df
+/qilin-agent-cli/app-arguments:
   en: 979c1c9bedaf1b3e
   zh: a77b6d9db2cfc191
-/qilin-cli/profiles:
-  en: 2403793fc28a4574
-  zh: b7655fd1d77a8501
-/qilin-cli/optional-overlays:
+/qilin-agent-cli/profiles:
+  en: 7d717e3a016726f8
+  zh: 9ffeeb5933153c80
+/qilin-agent-cli/optional-overlays:
   en: 55972a91e0d1d24d
   zh: 920ae26285d8e1b6
-/qilin-cli/development:
-  en: e83101b27f5dd5a3
-  zh: 17d66dcf09613c3c
+/qilin-agent-cli/development:
+  en: fa8d7705c54df6f5
+  zh: 8fe3f713cfe31dbf

package/README.md

@@ -14,11 +14,19 @@ The `qilin` command is the sole supported Node application launcher: profiles ar
 | `qilin --profile headless "job"` | Run one fresh persisted session, print the final answer, and exit. |
 | `qilin --profile sdk` | Serve SDK clients over JSON-RPC stdio until shutdown or disconnect. |
 | `qilin --profile sdk-minimal` | Serve SDK clients with the standalone minimal agent tree. |
-| `qilin web` | Boot the Web profile. |
+| `qilin`, `qilin web` | Serve the deployment at one address: one isolated Web runtime per account, each serving the application's own landing page and sign-in form. The profile you already start is the deployment. |
+| `qilin tenants accounts` | List this Harness home's accounts and the tenant directory each owns. |
+| `qilin tenants add <username>` | Create an account, prompting for its password or reading `--password-stdin`. |
+| `qilin tenants passwd <username>` | Replace an account's password and retire the sessions it issued. |
+| `qilin tenants remove <username>` | Retire an account, keeping its tenant directory unless `--purge-data` is given. |
 | `qilin plugin --profile <name> <pnpm args>` | Manage a profile's plugins by forwarding to pnpm in the profile directory. |
 | `qilin plugin list` | List a profile's bundle layers in activation order; omit `--profile` for the product profile. |
 | `qilin plugin doctor <package\|directory>` | Report one plugin package's DSH-era compatibility without installing or running anything. |
 
+The browser-serving profiles — the product surface `qilin` and `qilin web` — are the deployment: one command, one address, with no second entry. The entry draws no interface of its own: it starts one Web runtime per account on demand under `$QILIN_HOME/tenants/<account id>/`, and forwards every request the browser makes — the application document, the `/api` channel, the mux upgrade, and ranged media reads — to the runtime its routing cookie names, with the runtime's own authority in place of the entry's so its session cookie stays bound to the runtime that minted it. A runtime's harness home is its own: sessions, tasks, workspaces, attachments, plugins, model settings, credentials, skills, and presets resolve there, and only the roster at `$QILIN_HOME/auth/accounts.json` is shared. Credentials are verified by the named account's own runtime: the entry forwards the sign-in submission there and relays the session cookie it issues, and the runtime admits only its own account, so a forged routing cookie reaches a runtime that does not recognize the caller. `--idle-ms` reclaims a runtime that has served no traffic for that long, and `0` disables reclamation; `--max-tenants` bounds how many runtimes live at once, reclaiming the least recently used one past that bound; `--restart-backoff-ms` sets the first wait before a runtime that failed to start is retried, doubling per consecutive failure. `--patch` composes every runtime with an extra overlay layer; `--tls-cert` and `--tls-key` serve the entry's address over HTTPS and terminate TLS in front of the loopback runtimes, so the pair is supplied together and is refused with `--per-account-ports`. The entry reads only the flags it owns: every other argument reaches each runtime's own command line, and `--host` refuses a wildcard address. One browser drives one account at a time. The application inside a runtime owns the landing page, the sign-in form, and registration. With accounts in the roster the bare address redirects to the first account's path, `/t/<account>/`, and every other account is reachable at its own. With no accounts yet, every path goes to a first-run runtime, whose layer admits whoever the roster holds, so the product's own form creates the first account and the deployment never describes what to type. `--registration open|closed` decides whether the product's form may create accounts: the default is `open` on a loopback address and `closed` on every other, so an address other machines reach creates an account only where the operator says so, with `qilin tenants add`; a name the roster does not hold, a routing cookie naming an account it no longer holds, and every other request that names no account are answered by that same runtime, so the deployment never speaks for the application. `/healthz` and `/status` stay the entry's own reads.
+
+The roster subcommands maintain the accounts that shared file holds. A tenant runtime admits exactly the account it serves and closes registration, so its own Web surface cannot create a second account; the first-run runtime carries the deployment's policy instead, which is where a deployment that accepts accounts grows through the product's own form. `add` creates an account without a browser, `passwd` re-keys one and retires its issued sessions, and `remove` retires one while keeping its Sessions on disk unless `--purge-data` is given. A runtime started for a removed account fails loud, because its overlay admits an account the file no longer holds.
+
 The invoking directory is the default workspace root. The `web`, `headless`, `sdk`, `sdk-minimal`, and `acp` profiles auto-initialize on first use from shipped templates. Create another profile at an unused, non-shipped name with `--from-default-profile`, or initialize a base-backed profile through `qilin plugin`. The `desktop` name is reserved for the Electron-owned profile, so the CLI rejects boot, config-dump, and plugin-management requests for it. After a successful package operation the command reconciles the profile's bundle list, and it refuses a profile whose installed dependencies include an upstream DSH-era engine package: the diagnostic names each colliding package, the QiLin package it maps onto, and the `remove` command that clears it, and the command exits 1 without changing the bundle list.
 
 `list` and `doctor` read the profile and never initialize it or run pnpm. `doctor` accepts an installed package name or a package directory and checks the four rules a plugin must satisfy to load here: whether the package builds the DSH-era home itself instead of reading `DSH_HOME`/`QILIN_HOME`, installs an engine package the harness supplies, imports an engine name it never declared as a peer, and injects client module names the compatibility layer cannot map. It prints one finding per line and exits 1 only when a finding blocks activation.
@@ -32,10 +40,11 @@ Install the command itself from the published package (`npm install -g @qilin-ag
 The launcher parses only its own flags and hands everything after them to the booted profile, where any injected app plugin may parse the shared immutable snapshot ([`qilin-cmdline`](../../packages/boot/cmdline/README.md)). The first token the launcher does not recognize starts the app's arguments:
 
 ```sh
-qilin --profile web --port 8080       # --port belongs to the web app
+qilin --profile web --port 8080       # --port is the deployment's address
 qilin --profile tui --resume <id>     # example, assuming the tui profile is installed; --resume belongs to the terminal app
 qilin --profile headless "run the tests"
-qilin --profile web --help            # the web app's flags, not the launcher's
+qilin --profile web --patch ./extra.cordis.yml   # the overlay every account's runtime composes with
+qilin --profile web --help            # the deployment's flags, then the app's
 qilin --help                          # the launcher's own help
 ```
 

package/README.zh.md

@@ -14,11 +14,19 @@
 | `qilin --profile headless "job"` | 运行一个全新的持久化会话，打印最终答案并退出。 |
 | `qilin --profile sdk` | 通过 JSON-RPC stdio 为 SDK 客户端提供服务，直至关闭或断开连接。 |
 | `qilin --profile sdk-minimal` | 以独立极简 agent（智能体）配置树为 SDK 客户端提供服务。 |
-| `qilin web` | 启动 Web profile。 |
+| `qilin`、`qilin web` | 在一个地址上服务整套部署：每个账户一个隔离的 Web 运行时，各自服务应用自己的落地页与登录表单。你原本就在启动的那个 profile 就是整套部署。 |
+| `qilin tenants accounts` | 列出本 harness home 的账户，以及每个账户拥有的租户目录。 |
+| `qilin tenants add <用户名>` | 创建一个账户，交互式输入密码，或读取 `--password-stdin`。 |
+| `qilin tenants passwd <用户名>` | 替换某个账户的密码，并使其已签发的会话失效。 |
+| `qilin tenants remove <用户名>` | 注销某个账户，默认保留其租户目录，除非给出 `--purge-data`。 |
 | `qilin plugin --profile <name> <pnpm args>` | 通过在 profile 目录中转发给 pnpm 来管理该 profile 的插件。 |
 | `qilin plugin list` | 按激活顺序列出某个 profile 的 bundle 层；省略 `--profile` 时使用产品 profile。 |
 | `qilin plugin doctor <包名\|目录>` | 报告某个插件包的 DSH 时代兼容性，不安装也不运行任何东西。 |
 
+会服务浏览器的 profile——产品面 `qilin` 与 `qilin web`——就是整套部署：一条命令，一个地址，没有第二个入口。入口自己不作画：它按需在 `$QILIN_HOME/tenants/<账户 id>/` 下为每个账户启动一个 Web 运行时，并把浏览器发出的每个请求——应用文档、`/api` 通道、mux 升级与带 Range 的媒体读取——转发到它的路由 cookie 所命中的那个运行时，同时把运行时自己的 authority 顶替掉入口的，从而让它的会话 cookie 始终绑定在签发它的那个运行时上。运行时的 harness home 归它自己：会话、任务、工作区、附件、插件、模型设置、凭据、技能与预设都在其中解析，只有 `$QILIN_HOME/auth/accounts.json` 这份名册是共享的。凭据由被指名账户自己的运行时校验：入口把登录提交转发到那里，并中继它签发的会话 cookie；运行时只接纳自己的账户，因此伪造的路由 cookie 只会到达一个不认可调用者的运行时。`--idle-ms` 会回收在该时长内没有服务过任何流量的运行时，`0` 表示不回收；`--max-tenants` 限定同时存活多少个运行时，超出上限时回收最久未使用的那个；`--restart-backoff-ms` 设定启动失败的运行时第一次重试前的等待，每次连续失败翻倍。`--patch` 让每个运行时都多叠一层 overlay；`--tls-cert` 与 `--tls-key` 让入口地址以 HTTPS 服务，并在 loopback 运行时之前终止 TLS，因此两者必须成对给出，且与 `--per-account-ports` 互斥。入口只读自己拥有的 flag：其余参数一律交给每个运行时自己的命令行，而 `--host` 拒绝通配地址。同一个浏览器一次只服务一个账户。落地页、登录表单与注册都归运行时内部的应用所有。名册里有账户时，裸地址会重定向到第一个账户的路径 `/t/<账户>/`，其余账户各自在自己的路径上可达。名册为空时，每个路径都交给首启运行时，它那一层的接纳判据就是名册里有什么就接纳什么，于是由产品自己的表单创建第一个账户，入口从不说明该输入什么。`--registration open|closed` 决定产品自己的表单能否创建账户：loopback 地址上默认为 `open`，其他地址上默认为 `closed`，因此别的机器能到达的地址只在运维明说时才创建账户（用 `qilin tenants add`）；名册里没有的名字、指向一个名册已不再持有的账户的路由 cookie，以及其余任何没有指名账户的请求，都由同一个运行时回答，因此入口从不替应用说话。`/healthz` 与 `/status` 仍归入口自己读取。
+
+roster 子命令维护该共享文件中的账户。租户运行时只接纳自己服务的那个账户且关闭注册，因此它自己的 Web 界面无法创建第二个账户；首启运行时承载的则是部署自己的策略，接受新账户的部署由此通过产品自己的表单扩充账户。`add` 无需浏览器即可创建账户，`passwd` 为一个账户重新设置密码并使其已签发的会话失效，`remove` 注销一个账户，默认把它的 Session 留在磁盘上，除非给出 `--purge-data`。为已注销账户启动的运行时会明确失败，因为它的覆盖层接纳的是一个文件里已不存在的账户。
+
 运行命令时所在的目录将作为默认 workspace 根目录。`web`、`headless`、`sdk`、`sdk-minimal` 和 `acp` profile 在首次使用时会从随附模板自动初始化。使用 `--from-default-profile` 可以基于这些模板之一，在尚未使用的非内置名称处创建其他 profile；通过 `qilin plugin` 则可以初始化一个以 base 为基础的 profile。`desktop` 名称保留给 Electron 持有的 profile，因此 CLI（命令行界面）会拒绝针对它的启动、配置 dump 和插件管理请求。包操作成功后命令会协调 profile 的 bundle 列表；若 profile 的已安装依赖中出现上游 DSH 时代的引擎包，命令会拒绝：诊断会指明每个冲突包、它映射到的 QiLin 包，以及清除它的 `remove` 命令，命令以退出码 1 结束且不改变 bundle 列表。
 
 `list` 与 `doctor` 只读取 profile，既不初始化它也不运行 pnpm。`doctor` 接受已安装的包名或包目录，检查插件要在此加载必须满足的四条规则：包是否自己拼出 DSH 时代的主目录而不是读取 `DSH_HOME`/`QILIN_HOME`、是否安装了 harness 已提供的引擎包、是否导入了未声明为 peer 的引擎名、以及是否注入了兼容层无法映射的客户端模块名。它每行输出一条发现，仅当某条发现会阻断激活时才以退出码 1 结束。
@@ -32,10 +40,11 @@
 启动器只解析自身的 flag，并将其后的所有内容交给已启动的 profile；注入该 profile 的任意应用插件都可以解析这份共享的不可变快照（[`qilin-cmdline`](../../packages/boot/cmdline/README.zh.md)）。启动器无法识别的第一个 token 标志着应用参数的开始：
 
 ```sh
-qilin --profile web --port 8080       # --port belongs to the web app
+qilin --profile web --port 8080       # --port is the deployment's address
 qilin --profile tui --resume <id>     # example, assuming the tui profile is installed; --resume belongs to the terminal app
 qilin --profile headless "run the tests"
-qilin --profile web --help            # the web app's flags, not the launcher's
+qilin --profile web --patch ./extra.cordis.yml   # the overlay every account's runtime composes with
+qilin --profile web --help            # the deployment's flags, then the app's
 qilin --help                          # the launcher's own help
 ```
 

package/lib/bin.js

@@ -62,6 +62,12 @@ Examples:
                                               allow one rejected plugin/runtime pair
   qilin plugin revoke-version <pkg@ver> --qilin-version <exact>
                                               withdraw one exemption
+  qilin web --port 0                          serve the deployment; each account gets its own runtime
+  qilin tenants accounts                      list this home's accounts and their tenant directories
+  qilin tenants add alice                     create an account, prompting for its password
+  echo "$PASSWORD" | qilin tenants passwd alice --password-stdin
+                                              replace a password and retire its sessions
+  qilin tenants remove alice                  retire an account, keeping its Sessions on disk
 `;
 /**
 * Resolve a boot or dump invocation from the launcher flags and the leftover
@@ -106,7 +112,7 @@ function parseQilinArgs(argv, version) {
 	const first = argv[0];
 	let resolved;
 	const program = new Command();
-	program.name("qilin").version(version, "-V, --version", "output the version number").usage("[--profile] <name> [options] [app-args...]\n       qilin plugin --profile <name> <pnpm-args...>").description("qilin: boot the QiLin product surface, or any profile — an ordered stack of plugin-bundle patch layers under your own overrides.").addHelpText("after", HELP_EXAMPLES).exitOverride().helpOption(false).helpCommand(false).allowUnknownOption().passThroughOptions().enablePositionalOptions().argument("[args...]", "arguments for the booted profile's app (see: qilin --profile <name> --help)").option("--profile <name>", "the profile under $QILIN_HOME/profiles to boot", selectProfile).option("--from-default-profile <name>", "initialize a new custom profile from a shipped profile template").option("--patch <path>", "extra patch-list overlay applied after the profile layer (repeatable)", collect).option("--dump-config", "print the composed profile tree and exit").option("--dump-default-config", "print the profile tree without its user layer or --patch overlays and exit").action((args, options) => {
+	program.name("qilin").version(version, "-V, --version", "output the version number").usage("[--profile] <name> [options] [app-args...]\n       qilin plugin --profile <name> <pnpm-args...>\n       qilin web [options]").description("qilin: boot the QiLin product surface, or any profile — an ordered stack of plugin-bundle patch layers under your own overrides.").addHelpText("after", HELP_EXAMPLES).exitOverride().helpOption(false).helpCommand(false).allowUnknownOption().passThroughOptions().enablePositionalOptions().argument("[args...]", "arguments for the booted profile's app (see: qilin --profile <name> --help)").option("--profile <name>", "the profile under $QILIN_HOME/profiles to boot", selectProfile).option("--from-default-profile <name>", "initialize a new custom profile from a shipped profile template").option("--patch <path>", "extra patch-list overlay applied after the profile layer (repeatable)", collect).option("--dump-config", "print the composed profile tree and exit").option("--dump-default-config", "print the profile tree without its user layer or --patch overlays and exit").action((args, options) => {
 		if (options.profile === void 0 && args.some((argument) => argument === "-h" || argument === "--help")) program.help();
 		const profile = options.profile ?? PRODUCT_PROFILE;
 		if (profile === "") program.error("error: --profile needs a name");
@@ -129,8 +135,52 @@ function parseQilinArgs(argv, version) {
 			};
 		});
 	}
+	if (first === "tenants") {
+		const tenants = program.command("tenants").description("maintain the accounts every runtime under this Harness home shares; qilin web serves the deployment, one isolated runtime per account");
+		tenants.action(() => {
+			program.error("error: tenants needs a subcommand (accounts, add, passwd, remove)");
+		});
+		tenants.command("accounts").description("list the accounts of this Harness home and the tenant directory each owns").action(() => {
+			resolved = {
+				mode: "tenants",
+				request: { command: "accounts" }
+			};
+		});
+		tenants.command("add").description("create one account in this Harness home").argument("<username>", "login name: 3-32 characters of a-z, 0-9, _, ., or -, starting with a letter or digit").option("--email <address>", "address stored with the account").option("--admin", "make this the deployment's administrator: the one account that reads every account's usage ledger").option("--password-stdin", "read the password from standard input instead of prompting").action((username, options) => {
+			resolved = {
+				mode: "tenants",
+				request: {
+					command: "add",
+					username,
+					email: options.email,
+					admin: options.admin === true,
+					password: options.passwordStdin === true ? { kind: "stdin" } : { kind: "prompt" }
+				}
+			};
+		});
+		tenants.command("passwd").description("replace one account's password, retiring the sessions it issued").argument("<username>", "login name of the account to re-key").option("--password-stdin", "read the password from standard input instead of prompting").action((username, options) => {
+			resolved = {
+				mode: "tenants",
+				request: {
+					command: "passwd",
+					username,
+					password: options.passwordStdin === true ? { kind: "stdin" } : { kind: "prompt" }
+				}
+			};
+		});
+		tenants.command("remove").description("retire one account from this Harness home").argument("<username>", "login name of the account to retire").option("--purge-data", "also remove the account's tenant directory, Sessions included").action((username, options) => {
+			resolved = {
+				mode: "tenants",
+				request: {
+					command: "remove",
+					username,
+					purgeData: options.purgeData === true
+				}
+			};
+		});
+	}
 	try {
-		const expanded = first !== void 0 && !first.startsWith("-") && first !== "plugin" ? ["--profile", ...argv] : argv;
+		const expanded = first !== void 0 && !first.startsWith("-") && first !== "plugin" && first !== "tenants" ? ["--profile", ...argv] : argv;
 		program.parse(expanded, { from: "user" });
 	} catch (error) {
 		return process.exit(error instanceof CommanderError ? error.exitCode : 1);
@@ -140,6 +190,34 @@ function parseQilinArgs(argv, version) {
 	return resolved;
 }
 //#endregion
+//#region lib/types/scheduler-yield.js
+/**
+* Host fallback for the Web Scheduler API global.
+* @module @qilin-agent/cli/scheduler-yield
+*/
+/**
+* Install `globalThis.scheduler.yield` unless the host already defines a
+* `scheduler`.
+*
+* The fallback resolves on the next `setImmediate` — the API's "yield to the
+* event loop once, then continue" semantic — and a host-provided `scheduler`
+* is left untouched. Call it before importing anything that may read the
+* global; `bin.ts` calls it at the top of the entry, ahead of every mode
+* module. Rationale: [the host-shim Agent
+* Note](../../../.agents/notes/implemented/architecture/2026-10-07-web-scheduler-yield-host-shim.md).
+*
+* @returns whether this call installed the fallback.
+*/
+function installSchedulerYield() {
+	if (globalThis.scheduler !== void 0) return false;
+	Object.defineProperty(globalThis, "scheduler", {
+		value: { yield: () => new Promise((resolve) => setImmediate(resolve)) },
+		writable: true,
+		configurable: true
+	});
+	return true;
+}
+//#endregion
 //#region lib/types/startup-diagnostics.js
 /** Save original startup diagnostics while keeping the terminal report concise. */
 /** Wait for stderr to finish the write before the failed process exits. */
@@ -203,11 +281,7 @@ async function reportStartupFailure(error, context, write = writeStderr) {
 * @module @qilin-agent/cli/bin
 */
 /* v8 ignore file -- built-bin acceptance exercises this self-executing dispatch. */
-if (globalThis.scheduler === void 0) Object.defineProperty(globalThis, "scheduler", {
-	value: { yield: () => new Promise((resolve) => setImmediate(resolve)) },
-	writable: true,
-	configurable: true
-});
+installSchedulerYield();
 /**
 * Run the public qilin command-line interface.
 * @returns a promise that settles when the selected command mode finishes.
@@ -217,6 +291,21 @@ async function runCli() {
 	const invocation = parseQilinArgs(process.argv.slice(2), version);
 	switch (invocation.mode) {
 		case "profile": {
+			const { ENTRY_PROFILES, isWebEntry, runWebEntry } = await import("./web-entry-C--0C6wG.js");
+			if (ENTRY_PROFILES.includes(invocation.profile) && isWebEntry()) {
+				try {
+					process.exitCode = await runWebEntry({
+						args: invocation.args,
+						profile: invocation.profile,
+						patches: invocation.patches,
+						fromDefaultProfile: invocation.fromDefaultProfile
+					});
+				} catch (error) {
+					process.stderr.write(`${error instanceof Error ? error.message : String(error)}\n`);
+					process.exit(1);
+				}
+				break;
+			}
 			const { runProfile } = await import("./profile-boot.js");
 			try {
 				await runProfile({
@@ -242,6 +331,11 @@ async function runCli() {
 			process.exit(await runPlugin(invocation.profile, invocation.args));
 			break;
 		}
+		case "tenants": {
+			const { runTenantsRoster } = await import("./tenants-roster-Bhr9x2Jw.js");
+			process.exitCode = await runTenantsRoster(invocation.request);
+			break;
+		}
 		case "dump-config": {
 			const { runDumpConfig } = await import("./dump-config-_HRfhhWz.js");
 			runDumpConfig(invocation.profile, invocation.defaultOnly, invocation.patches, invocation.fromDefaultProfile);