@lark-codem/lark-cli 0.1.1-test.20261024.2 → 0.1.1-test.20261110.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 +6 -0
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -10,6 +10,10 @@ The pinned official CLI owns personal commands, OAuth, profiles, user credential
|
|
|
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
|
|
|
13
|
+
Hosts may set `CODEM_LARK_PROXY_URL=https://<facade-host>/goapi/v5/proxy/lark/request` to select the Facade Sidecar protocol for all commands and `/codem/lark-cli/context`. This dedicated endpoint does not change other tools' `CODEM_PROXY_BASE_URL`. The CLI sends the current CodeM identity token, logical method, escaped path, raw query, name/value headers, one Base64 body and `lark_context`; it restores the inner HTTP status, headers and bytes before existing output, authorization and download handling. An invalid envelope fails closed. A configured endpoint never falls back to Base after failure.
|
|
14
|
+
|
|
15
|
+
Personal cloud computers use the platform bootstrap's `CODEM_IMAGE_PROFILE=cloud-computer` and provide the current `CODEM_TOKEN` and `CODEM_LARK_PROXY_URL`. The profile selects the managed runtime without a CLI mode override. They may omit Dispatch; the profile itself grants no identity or permission. Base verifies the token's trusted personal subject and rejects task-bound credentials with missing or mismatched Dispatch. Missing runtime credentials or endpoint block business calls without reading local OAuth; help and version remain offline. Existing tasks retain their actual Dispatch and use the legacy protocol when no dedicated URL is configured. Each invocation consumes the runtime's current token without persisting or refreshing it in the CLI.
|
|
16
|
+
|
|
13
17
|
The gateway base accepts an HTTPS origin or the same origin with `/goapi/codem` (and an optional trailing slash), including the Native host's `CODEM_SERVER_URL`. Both forms produce exactly `/goapi/codem/lark_proxy/request`; arbitrary paths, query strings, fragments and embedded credentials remain rejected. Version and official help commands work offline without a gateway or task token, while retaining task mode and private config. Business commands still require the complete task context and never fall back to personal credentials.
|
|
14
18
|
|
|
15
19
|
`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.
|
|
@@ -27,3 +31,5 @@ On local installations the dependency lives inside the selected CodeM version un
|
|
|
27
31
|
Tag task authorization is checked during the existing `/codem/lark-cli/context` handshake, before a business request is constructed. A missing server grant returns a public `_codem_authorization` object (kind `server_user_authorization`, status `authorization_required`). The CLI emits that object to stdout and exits nonzero; the host displays its opaque CodeM short link and stops the turn. No token, personal profile or callback URL is read or persisted by this path. Malformed invitations, dependency failures and generic 403 responses never become authorization links.
|
|
28
32
|
|
|
29
33
|
After the initiator confirms completion, run exactly `lark-cli whoami` in the same task. For Tag this checks Base's keeper directly and reports identity `user` with `_codem_authorization.status=ready`, without an extra user-info API or replaying the blocked operation. If the grant is still absent, the new check may create a fresh invitation; display the current link and stop rather than polling. AI-node identity and capability policy are unchanged. Deploy the context authorization support in Base !2126 first, then release this adapter and the paired Bridge !709 instructions. Existing package versions remain immutable.
|
|
34
|
+
|
|
35
|
+
When an existing Tag UAT lacks a business scope, Base may return its own HTTP 403 authorization response marked `X-Codem-Authorization: server_user_authorization`. The transport adapter projects only validated public intent fields and stops with a nonzero exit; it does not retry the business request or borrow local credentials. Later requests in the same invocation are blocked, including batch shortcuts that normally return partial results as success; partial output is preserved with an explicit authorization error and nonzero exit. Ordinary responses, attachments and streams are not buffered or interpreted. Base owns the shared scope-upgrade allowlist, initiating-user binding and callback scope validation. Missing application permissions or resource ACL failures do not enter this flow. Deploy the Base response support before releasing this adapter; previously published packages are unchanged.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lark-codem/lark-cli",
|
|
3
|
-
"version": "0.1.1-test.
|
|
3
|
+
"version": "0.1.1-test.20261110.1",
|
|
4
4
|
"description": "Official Lark CLI with CodeM personal and task credential boundaries.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"exports": {
|
|
@@ -20,12 +20,12 @@
|
|
|
20
20
|
"test:package": "node scripts/test-package.mjs"
|
|
21
21
|
},
|
|
22
22
|
"optionalDependencies": {
|
|
23
|
-
"@lark-codem/lark-cli-darwin-x64": "0.1.1-test.
|
|
24
|
-
"@lark-codem/lark-cli-darwin-arm64": "0.1.1-test.
|
|
25
|
-
"@lark-codem/lark-cli-linux-x64": "0.1.1-test.
|
|
26
|
-
"@lark-codem/lark-cli-linux-arm64": "0.1.1-test.
|
|
27
|
-
"@lark-codem/lark-cli-win32-x64": "0.1.1-test.
|
|
28
|
-
"@lark-codem/lark-cli-win32-arm64": "0.1.1-test.
|
|
23
|
+
"@lark-codem/lark-cli-darwin-x64": "0.1.1-test.20261110.1",
|
|
24
|
+
"@lark-codem/lark-cli-darwin-arm64": "0.1.1-test.20261110.1",
|
|
25
|
+
"@lark-codem/lark-cli-linux-x64": "0.1.1-test.20261110.1",
|
|
26
|
+
"@lark-codem/lark-cli-linux-arm64": "0.1.1-test.20261110.1",
|
|
27
|
+
"@lark-codem/lark-cli-win32-x64": "0.1.1-test.20261110.1",
|
|
28
|
+
"@lark-codem/lark-cli-win32-arm64": "0.1.1-test.20261110.1"
|
|
29
29
|
},
|
|
30
30
|
"engines": {
|
|
31
31
|
"node": ">=18"
|