@uru-intelligence/cli 0.3.61 → 0.4.11

package/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Uru CLI changelog
+
+> Generated from `changes/cli/*.json`. Do not edit release rows by hand.
+
+## Unreleased
+
+### Security
+
+- Bind npm publication to an attested candidate tarball and require the published cli_pin matrix before release success. — surfaces: cli, release; reference: docs/plans/cli-sdk-native-release-modernization/PLAN.md
+  - Action: Release operators must supply the exact candidate run, attempt, release-evidence artifact ID, and MCP commit to the protected publish workflow.
+
+### Added
+
+- Add a side-effect-free internal CLI library entrypoint with a typed whoami foundation. _(internal)_ — surfaces: cli, sdk; reference: docs/plans/cli-sdk-native-release-modernization/DECISION_RECORDS.md
+  - Action: Programmatic callers must pass an explicit token and workspace; no public SDK compatibility promise is introduced.
+- Add direct CLI access to Home pins and Focus rules from the shared operation registry. — surfaces: cli, docs; reference: content/docs/home.mdx
+  - Action: Use uru home <operation> --params-json '{...}' or the matching home.* operation ID.
+
+### Fixed
+
+- Report a non-JSON API response as what it is. A proxy or firewall that answers with an HTML page now produces the HTTP status and content type instead of `Unexpected token '<', "<!DOCTYPE "... is not valid JSON`. — surfaces: cli; reference: apps/cli/src/client.ts
+  - Action: No action is required. Failures of this class now carry the `non_json_response` error code, keep the auth exit code on a 401, and print a tip naming the likely cause.
+- Report what a rejected credential actually means: `uru doctor` now runs a read-only data call instead of trusting `uru whoami`, API error envelopes are read in full, and auth advice follows where the token came from. — surfaces: cli; reference: apps/cli/src/doctor.ts
+  - Action: No action is required. `uru doctor` gains a `data access` check and fails when a credential validates but cannot execute tools; a token supplied through `--token` or `URU_TOKEN` is no longer told to run `uru login`.
+- Use the shared SemVer contract when deciding whether to show a CLI update notice. — surfaces: cli, release; reference: docs/plans/cli-sdk-native-release-modernization/PLAN.md
+  - Action: No action is required; prerelease and malformed registry versions now follow the same validation and ordering rules as release publication.
+
+### Internal
+
+- Retain an executable compatibility probe for the paused Stricli migration decision. _(internal)_ — surfaces: cli; reference: docs/plans/cli-sdk-native-release-modernization/DECISION_RECORDS.md
+  - Action: Do not adopt Stricli until a pinned upstream release passes this probe and the required seven-slice hard-cut proof.

package/README.md

@@ -46,7 +46,7 @@ bun src/index.ts gems versions diff 'library/Golden Gems/My Gem.gem' 13 14
 bun src/index.ts gems versions restore 'library/Golden Gems/My Gem.gem' 12
 bun src/index.ts gems releases create 'library/Golden Gems/My Gem.gem' 14
 bun src/index.ts gems releases list 'library/Golden Gems/My Gem.gem'
-bun src/index.ts gems links create 'library/Golden Gems/My Gem.gem' --name Client --version 14
+bun src/index.ts gems links create 'library/Golden Gems/My Gem.gem' --name Client --pin --version 14
 bun src/index.ts gems links set-version 'library/Golden Gems/My Gem.gem' <link-id> 14
 bun src/index.ts gems runs list 'library/Golden Gems/My Gem.gem'
 bun src/index.ts gems runs show 'library/Golden Gems/My Gem.gem' <run-id>
@@ -68,14 +68,14 @@ bun src/index.ts library mv 'library/Notes/Draft.md' 'library/Notes/Final.md'
 bun src/index.ts library rm 'library/Notes/Old.md'
 bun src/index.ts library restore 'library/Notes/Old.md'
 bun src/index.ts datasets query revenue_rows --limit 50 --response-format concise --json
-bun src/index.ts library ls --params-json '{"path":"library","resource_type":"dataset"}'
-# Copy the exact resourceSlug from Library discovery; never infer it from name.
-bun src/index.ts datasets get --params-json '{"dataset_id":"revenue-rows"}'
-bun src/index.ts datasets rows-upsert --params-json '{"dataset_id":"revenue-rows","rows":[{"name":"Acme"}]}'
-bun src/index.ts datasets manage-create --params-json '{"title":"Revenue Rows","data_schema":{"properties":[]}}'
+# Registry-family commands accept canonical camelCase fields and adapt them at
+# the tool-protocol boundary.
+bun src/index.ts datasets get revenue-rows
+bun src/index.ts datasets rows --params-json '{"op":"upsert","datasetId":"revenue-rows","rows":[{"name":"Acme"}]}'
+bun src/index.ts datasets create --params-json '{"title":"Revenue Rows","properties":[{"clientKey":"name","name":"Name","type":"title","required":true,"nullable":false,"position":0,"config":{}}]}'
 
 # Automation helpers over the platform tool surface.
-bun src/index.ts automations ls --status active --view summary
+bun src/index.ts automations ls --limit 100
 bun src/index.ts automations get <automation-id>
 bun src/index.ts automations create "Daily revenue digest" --status draft
 bun src/index.ts automations enable <automation-id>
@@ -84,7 +84,7 @@ bun src/index.ts automations runs ls <automation-id> --scope workspace --limit 2
 bun src/index.ts automations runs tail <run-id> --level warn
 bun src/index.ts automations runs cancel <run-id> --yes
 
-# Raw platform-tool escape hatch for diagnostics and parity.
+# Raw platform-tool escape hatch for diagnostics and low-level operations.
 bun src/index.ts tools ls
 bun src/index.ts tools schema gem_control_plane --json
 bun src/index.ts tools run gem_control_plane --params-json '{"op":"inspect","path":"library/Golden Gems/My Gem.gem"}'
@@ -105,6 +105,7 @@ bun src/index.ts mcp install --path ~/.config/claude-code/mcp.json --api-key "$U
 bun src/index.ts complete bash
 bun src/index.ts complete zsh
 bun src/index.ts complete fish
+bun src/index.ts complete powershell
 ```
 
 Generated MCP configs use non-interactive `npx -y` and pin
@@ -178,6 +179,17 @@ For one-off usage:
 printf '%s' "$URU_TOKEN" | npx @uru-intelligence/cli whoami --token-stdin --json
 ```
 
+The package root is a side-effect-free library entry. It does not execute a
+command, read local CLI configuration, install signal handlers, write output,
+or start network activity on import. The package currently exposes only the
+fail-closed internal `createUruClient` foundation: callers must supply a token
+and an explicit workspace, every call accepts cancellation, and it validates
+the authenticated workspace before returning a typed result. DG-1 has not
+accepted a public high-level SDK compatibility promise, so no broader SDK or
+raw API surface is implied by this export. The executable remains the `uru`
+binary; `@uru-intelligence/cli/cli` is an explicit executable subpath for
+packaging tools, not an SDK API.
+
 ## Release validation
 
 Before publishing, run the full local CLI gate and the staging CLI/MCP smoke with a staging-scoped token. The smoke reads credentials from env or macOS Keychain and never prints the token. To avoid putting a token in shell history, store it as `uru_staging_smoke_token` with `security add-generic-password -a "$USER" -s uru_staging_smoke_token -w '<token>' -U`.
@@ -191,14 +203,47 @@ URU_CLI_MCP_STAGING_SMOKE_TARGET=staging \
 ```
 
 Publish the scoped CLI only through the **Publish Uru CLI to npm** workflow on
-`main`. It first verifies that the exact pinned `uru-mcp` release exists, runs
-release validation, publishes through npm trusted publishing from a
-GitHub-hosted runner in the protected `production` environment, and then
-requires a separate live-registry job to verify the exact published version.
-The registry smoke intentionally runs `npm exec` from a clean OS temporary
-directory so the monorepo workspace cannot shadow the published package. The
-source repository is private, so npm OIDC authenticates the publish without a
-long-lived token but cannot emit a public provenance attestation.
+`main`. A release request must identify the candidate certification workflow
+run ID, attempt, and exact retained bundle artifact ID; the publisher never
+selects `latest` evidence. Before it reads the release record, it verifies the
+candidate's GitHub DSSE/in-toto artifact attestations for both the canonical
+release record and the exact `uru_cli.tgz`, pins the builder repository,
+candidate workflow path, development ref policy, run/attempt, predicate type,
+and source-bundle identity, then recomputes the build-input inventory at
+`main`.
+
+The workflow publishes that retained tarball from a sterile private temporary
+directory with `npm publish --ignore-scripts`; it never rebuilds, repacks, or
+rewrites it. npm trusted publishing runs only from the protected `production`
+environment. The registry smoke compares npm `dist.integrity` to the certified
+SRI and runs `npm exec` from a clean OS temporary directory so the monorepo
+workspace cannot shadow the published package. It then invokes the complete
+published `cli_pin` certification matrix for both staging and production. A
+value-free publication-state artifact records the observed npm SRI even when a
+publish response or a later gate fails. Re-dispatching the same immutable
+candidate selector resumes only when npm already serves that exact certified
+SRI; it then repeats the registry and published-matrix proof before evidence,
+tag, or GitHub release creation. A different SRI fails closed. A changed source
+or failed certification needs a higher-version forward fix; no npm version is
+ever rewritten.
+
+The workflow requires the immutable, no-bypass CLI tag policy before npm
+publication and revalidates it before tag creation. GitHub hides a ruleset's
+bypass actors from an ordinary workflow token, so the two policy-check steps
+mint a short-lived, repository-scoped GitHub App token solely to inspect that
+property. The App's client ID is the `production` environment variable
+`CLI_RULESET_AUDIT_APP_CLIENT_ID`; its private key is the matching
+`CLI_RULESET_AUDIT_APP_PRIVATE_KEY` environment secret. Its administration
+write grant is required for visibility only and is never available to the npm
+publication step or the tag/release creation step. Only after published evidence
+is retained does the workflow create the annotated
+`uru-cli-vX.Y.Z` tag at the exact dispatched `main` commit and a GitHub release
+with generated notes. The final job verifies an existing tag is annotated and
+points to that same commit before it can resume an interrupted GitHub-release
+request; it never changes the npm package, repoints a tag, or treats a draft or
+prerelease as success. Before the first use, repository policy must contain an
+active, no-bypass `refs/tags/uru-cli-v*` rule that blocks both updates and
+deletions; the workflow queries and requires it before creating the tag.
 
 ```bash
 bun --filter=@uru-intelligence/cli run smoke:registry