@lark-codem/lark-cli 0.1.0-codem.4 → 0.1.1-test.20261023.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,11 +2,11 @@
2
2
 
3
3
  Maintained in [codem-cli-adapters](https://code.byted.org/dc/codem-cli-adapters). Fixed official Agent Skills are packaged in the sibling `packages/codem-larkcli-plugin`; credentials and authorization remain in Base.
4
4
 
5
- Install `@lark-codem/lark-cli` with optional dependencies enabled, then invoke `lark-cli` directly. The main package selects exactly one matching native package on macOS, Windows or Linux, x64 or arm64. Hosts can synchronously load `require('@lark-codem/lark-cli').resolveLarkCliBinary()` and link the returned native executable onto PATH. `packageVersion` and `@lark-codem/lark-cli/package.json` expose the exact package version.
5
+ Install `@lark-codem/lark-cli` as an exact private dependency with optional dependencies enabled. This package declares no npm `bin` command and does not replace the user's global Lark CLI. The main package selects exactly one matching native package on macOS, Windows or Linux, x64 or arm64. CodeM hosts can synchronously load `require('@lark-codem/lark-cli').resolveLarkCliBinary()` and use the returned absolute path or prepend its directory only to an agent child's PATH. `packageVersion` and `@lark-codem/lark-cli/package.json` expose the exact package version.
6
6
 
7
7
  The pinned official CLI owns personal commands, OAuth, profiles, user credentials, document formats, output and exit codes. With no task context, `CODEM_LARK_CLI_MODE=personal` (or unset) executes that CLI unchanged, including the host's managed UAT and `LARKSUITE_CLI_STRICT_MODE=user` environment.
8
8
 
9
- `CODEM_LARK_CLI_MODE=task`, a task token, dispatch ID or native sandbox marker selects the task boundary. `CODEM_TOKEN` and `CODEM_SANDBOX_DISPATCH_ID` (legacy `CODEM_DISPATCH_ID`) are both required; incomplete context fails before any business request. An explicit personal hint cannot downgrade an existing task. Task invocations isolate personal CLI config, ignore personal Lark credentials, use controlled placeholder credentials and send OpenAPI requests through the CodeM gateway. Gateway denial never falls back to personal auth. Sandbox business requests use the bot placeholder; Base executes with application TAT only. Sandbox calls never load, refresh or use a UAT. Base disables the calendar, meeting/minutes, whiteboard and user-identity helper capabilities in both sandbox scenes. Commands that require user credentials cannot run with the sandbox bot-only provider. Tag resource operations require Base to prove the initiator's permission under its configured policy; application access alone does not grant task access. Explicit `--as user`, app selection and personal profiles are rejected in task mode.
9
+ `CODEM_LARK_CLI_MODE=task`, a task token, dispatch ID or native sandbox marker selects the task boundary. `CODEM_TOKEN` and the current `CODEM_SANDBOX_DISPATCH_ID` (legacy `CODEM_DISPATCH_ID`) are both required. The CLI requests public scene metadata from Base through the same gateway: Tag resolves to the persisted initiator's user identity, while Meego AI nodes resolve to bot. No UAT, RT or application secret enters the CLI. Placeholder tokens are removed before forwarding; Base obtains the Tag initiator's server-owned Web UAT through UAT Keeper and preserves official API responses. Tag has no CodeM business capability allowlist; Feishu still enforces user scopes, resource permissions and each API's supported identities. AI-node requests retain the existing Base capability and work-item policy with TAT. Neither path falls back to personal profiles, device-owner credentials or another identity. Local credential/install management remains owned by the CodeM host. Deploy the context-capable Base before upgrading this CLI. Help and version stay offline. Dry runs resolve the same task identity as execution. Upstream may perform a read-only user-info lookup, but does not execute the previewed business operation.
10
10
 
11
11
  Personal and sandbox modes retain the pinned official business commands, parameters and help. The CLI does not consume the capability catalog, filter commands by scene, or rewrite business options. All sandbox scenes share the same functional Skills. Legacy `CODEM_LARK_TASK_SCENE` hints are ignored. Base independently resolves the persisted task scene and authorizes every logical request; a visible command does not grant permission. Official Skills are distributed separately as `@lark-codem/codem-larkcli-plugin` and a static plugin ZIP, loaded unchanged by the existing managed-resource loader in every scene. The sandbox plugin retains only Meegle work-item operations.
12
12
 
@@ -14,8 +14,10 @@ The gateway base accepts an HTTPS origin or the same origin with `/goapi/codem`
14
14
 
15
15
  `node packages/lark-cli/scripts/release.mjs` cross-compiles six executables with the npm package version embedded in the official `--version` output and packs the six platform packages followed by the main package. Artifacts, `manifest.json` and `SHA256SUMS` are written under `.artifacts/lark-cli/<version>/`. Each platform package exports its native binary, `package.json`, and `manifest.json` with the native SHA256, version and pinned upstream.
16
16
 
17
- The default command does not publish. Explicit `--publish --tag codem` publishes the exact platform tarballs first, checks each registry integrity, then publishes the main tarball. The current local candidate is `0.1.0-codem.4`, including document media/history support and the sandbox application-only boundary. Previously released artifacts remain immutable; update the main version, all six platform versions and exact optional dependencies together. Install all seven local tarballs with `npm install --ignore-scripts --offline --force <paths>` in an isolated test directory to validate a local candidate without registry publication. Production installs select the platform through npm normally.
17
+ The default command does not publish. Explicit `--publish` publishes the exact platform tarballs first, checks each registry integrity, then publishes the main tarball. Stable releases use ordinary `X.Y.Z` versions without a `-codem` suffix and default to the `latest` dist-tag. Prereleases default to `codem` and cannot publish to `latest`. The already published `0.1.0-codem.4` remains a test release, including document media/history support and the sandbox application-only boundary. Previously released artifacts remain immutable; update the main version, all six platform versions and exact optional dependencies together. After registry readback, update and release the Bridge's exact dependency; the CodeM installer/update installs that paired version rather than an independently selected latest release. The upstream update notifier and self-updater are disabled to prevent replacing this distribution with `@larksuite/cli`. Install all seven local tarballs with `npm install --ignore-scripts --offline --force <paths>` in an isolated test directory to validate a local candidate without registry publication. Production installs select the platform through npm normally.
18
18
 
19
19
  Sandbox local auth/config/skills management is disabled because it does not pass through Base. The official self-update command and upstream update/skills notices are disabled. Upgrade this distribution through the CodeM installer or host so the custom task boundary remains installed. All personal business and auth commands retain the official implementation.
20
20
 
21
21
  Native Linux fixture and installed-tarball tests verify protocol and packaging. Builds use CGO_ENABLED=0, -trimpath and -buildvcs=false; native manifests identify the exact executable bytes. Cross-compilation does not substitute for macOS and Windows native execution checks.
22
+
23
+ On local installations the dependency lives inside the selected CodeM version under `~/.codem/runtime/versions/`; sandbox images use their private runtime directory. Installation and update never uninstall or relink a user-owned global `lark-cli`. Existing published versions remain immutable; the no-bin contract applies when a new version is released.
package/package.json CHANGED
@@ -1,17 +1,13 @@
1
1
  {
2
2
  "name": "@lark-codem/lark-cli",
3
- "version": "0.1.0-codem.4",
3
+ "version": "0.1.1-test.20261023.1",
4
4
  "description": "Official Lark CLI with CodeM personal and task credential boundaries.",
5
5
  "type": "module",
6
- "bin": {
7
- "lark-cli": "bin/lark-cli.js"
8
- },
9
6
  "exports": {
10
7
  ".": "./resolve.cjs",
11
8
  "./package.json": "./package.json"
12
9
  },
13
10
  "files": [
14
- "bin",
15
11
  "resolve.cjs",
16
12
  "platforms.cjs",
17
13
  "README.md",
@@ -24,12 +20,12 @@
24
20
  "test:package": "node scripts/test-package.mjs"
25
21
  },
26
22
  "optionalDependencies": {
27
- "@lark-codem/lark-cli-darwin-x64": "0.1.0-codem.4",
28
- "@lark-codem/lark-cli-darwin-arm64": "0.1.0-codem.4",
29
- "@lark-codem/lark-cli-linux-x64": "0.1.0-codem.4",
30
- "@lark-codem/lark-cli-linux-arm64": "0.1.0-codem.4",
31
- "@lark-codem/lark-cli-win32-x64": "0.1.0-codem.4",
32
- "@lark-codem/lark-cli-win32-arm64": "0.1.0-codem.4"
23
+ "@lark-codem/lark-cli-darwin-x64": "0.1.1-test.20261023.1",
24
+ "@lark-codem/lark-cli-darwin-arm64": "0.1.1-test.20261023.1",
25
+ "@lark-codem/lark-cli-linux-x64": "0.1.1-test.20261023.1",
26
+ "@lark-codem/lark-cli-linux-arm64": "0.1.1-test.20261023.1",
27
+ "@lark-codem/lark-cli-win32-x64": "0.1.1-test.20261023.1",
28
+ "@lark-codem/lark-cli-win32-arm64": "0.1.1-test.20261023.1"
33
29
  },
34
30
  "engines": {
35
31
  "node": ">=18"
package/resolve.cjs CHANGED
@@ -4,7 +4,7 @@ const { version } = require('./package.json');
4
4
 
5
5
  // Synchronous for host installers using createRequire. Resolution never runs a
6
6
  // subprocess or changes installed files. Hosts may link the returned native
7
- // executable directly onto PATH; agents invoke the ordinary `lark-cli` command.
7
+ // executable into an agent child's private PATH; never the user's global PATH.
8
8
  function resolveLarkCliBinary({ platform = process.platform, arch = process.arch, resolve = require.resolve } = {}) {
9
9
  const target = targets.find(target => target.platform === platform && target.arch === arch);
10
10
  if (!target) throw new Error(`unsupported Lark CLI platform: ${platform}/${arch}`);
package/bin/lark-cli.js DELETED
@@ -1,12 +0,0 @@
1
- #!/usr/bin/env node
2
- import { spawnSync } from 'node:child_process';
3
- import { resolveLarkCliBinary } from '../resolve.cjs';
4
- try {
5
- const result = spawnSync(resolveLarkCliBinary(), process.argv.slice(2), { stdio: 'inherit' });
6
- if (result.error) throw result.error;
7
- if (result.signal) process.kill(process.pid, result.signal);
8
- else process.exit(result.status ?? 1);
9
- } catch (error) {
10
- console.error(error.message);
11
- process.exit(1);
12
- }