@lark-codem/lark-cli 0.1.2-test.20261116.2 → 0.1.2-test.20261117.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.
Files changed (2) hide show
  1. package/README.md +5 -1
  2. package/package.json +8 -8
package/README.md CHANGED
@@ -6,7 +6,7 @@ Install `@lark-codem/lark-cli` as an exact private dependency with optional depe
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 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 start with TAT and the existing Base capability and work-item policy. With the negotiated Bot-first protocol, Base alone may use the selected user UAT after an eligible permission failure, rollout checks and explicit consent for the current task. 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.
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 start with TAT and the existing Base capability and work-item policy. With the negotiated Bot-first protocol, Base alone may use the selected user UAT after an eligible permission failure, rollout checks and explicit consent for the current task. 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. All server-managed scenes skip the upstream automatic user-info lookup. Base owns identity and credential validation; an explicit user-info business request still reaches Base normally.
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
 
@@ -71,3 +71,7 @@ and projects these public fields without requiring a login intent, URL or OAuth
71
71
  Only Base's authenticated HITL decision grants node consent. Subsequent OAuth scope
72
72
  invitations retain the existing validated short-link flow. The adapter never grants consent
73
73
  or treats an agent's acknowledgement as a human decision.
74
+
75
+ ### Managed identity build
76
+
77
+ Use `node packages/lark-cli/scripts/go-managed.mjs build` (or `test`) for Go development. Release builds use the same pinned, temporary upstream source patch. It adds an explicit `ServerManagedIdentity` account opt-in and skips only automatic user-info enrichment for those accounts; personal CLI providers retain upstream verification. The patch does not modify the module cache and rejects a changed upstream version.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lark-codem/lark-cli",
3
- "version": "0.1.2-test.20261116.2",
3
+ "version": "0.1.2-test.20261117.1",
4
4
  "description": "Official Lark CLI with CodeM personal and task credential boundaries.",
5
5
  "type": "module",
6
6
  "exports": {
@@ -15,17 +15,17 @@
15
15
  ],
16
16
  "scripts": {
17
17
  "test": "node --test test/*.test.mjs",
18
- "test:cli": "cd cli && go test ./...",
18
+ "test:cli": "node scripts/go-managed.mjs test ./...",
19
19
  "pack:release": "node scripts/release.mjs",
20
20
  "test:package": "node scripts/test-package.mjs"
21
21
  },
22
22
  "optionalDependencies": {
23
- "@lark-codem/lark-cli-darwin-x64": "0.1.2-test.20261116.2",
24
- "@lark-codem/lark-cli-darwin-arm64": "0.1.2-test.20261116.2",
25
- "@lark-codem/lark-cli-linux-x64": "0.1.2-test.20261116.2",
26
- "@lark-codem/lark-cli-linux-arm64": "0.1.2-test.20261116.2",
27
- "@lark-codem/lark-cli-win32-x64": "0.1.2-test.20261116.2",
28
- "@lark-codem/lark-cli-win32-arm64": "0.1.2-test.20261116.2"
23
+ "@lark-codem/lark-cli-darwin-x64": "0.1.2-test.20261117.1",
24
+ "@lark-codem/lark-cli-darwin-arm64": "0.1.2-test.20261117.1",
25
+ "@lark-codem/lark-cli-linux-x64": "0.1.2-test.20261117.1",
26
+ "@lark-codem/lark-cli-linux-arm64": "0.1.2-test.20261117.1",
27
+ "@lark-codem/lark-cli-win32-x64": "0.1.2-test.20261117.1",
28
+ "@lark-codem/lark-cli-win32-arm64": "0.1.2-test.20261117.1"
29
29
  },
30
30
  "engines": {
31
31
  "node": ">=18"