skaile-cli 6.1.0 → 6.3.0

package/CHANGELOG.md

@@ -1,5 +1,70 @@
 # Changelog
 
+## 6.3.0
+
+### Minor Changes
+
+- [#1108](https://github.com/skaile-ai/workspaces/pull/1108) [`e750e6d`](https://github.com/skaile-ai/workspaces/commit/e750e6db28a26fefe31a761c39ffb27fba501ffe) Thanks [@mortegro](https://github.com/mortegro)! - `@skaile/workspaces/ai-sdk`: `resolveLanguageModel`, `loadMergedProviderRegistry`.
+
+  - `resolveLanguageModel(selector, { projectDir?, env? })` turns a provider-registry selector (`<providerId>/<modelId>`, a bare model id or `@role`) into a ready AI SDK `LanguageModel` over the same merged registry the CLI reads, with the credential read from `env:` refs. It returns the model, `providerId`, `modelId`, the endpoint `baseUrl`, the `role` and the selector's parse `warnings`. The provider SDKs (`@ai-sdk/anthropic`, `@ai-sdk/openai`, `@ai-sdk/openai-compatible`) are optional peers, loaded for the entry's surface only; a missing package or an unsupported surface fails with an error that names it.
+  - `loadMergedProviderRegistry({ projectDir })` (from `@skaile/workspaces/bridge` and `./sdk/bridge`) is the two-pass registry load `skaile providers` always did, moved out of the CLI. The CLI's output is unchanged.
+
+### Patch Changes
+
+- Updated dependencies [[`e750e6d`](https://github.com/skaile-ai/workspaces/commit/e750e6db28a26fefe31a761c39ffb27fba501ffe)]:
+  - @skaile/workspaces@6.3.0
+
+## 6.2.0
+
+### Minor Changes
+
+- [#1106](https://github.com/skaile-ai/workspaces/pull/1106) [`7af33f2`](https://github.com/skaile-ai/workspaces/commit/7af33f2cf748dab42e4a5114e872ff97f55036ca) Thanks [@mortegro](https://github.com/mortegro)! - model-endpoint: `POST /v1/chat/completions` forwards `response_format`, `usage` and `provider` to OpenAI-compatible upstreams and reports upstream `usage.cost`
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Agents: `run`, `repl` and `rebuild` refuse an `agents:` block that `validate`, `install` and `check` reject, with the same line and exit 1 before the session starts (p1512). The `Connected Resources` block in rendered agent files names `skaile connector ops <id>` and `skaile connector run <id> <operation>` instead of the removed `skaile res` (p1710). Unknown keys in `agent:` and `agents:` (`agents.<id>.colour`, `agent.modle`, `model.preffered`) warn in `check`, `doctor`, `install`, `run` and `repl`, not only in `validate` (p1712).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Authoring: one verdict in every command. `library init --path <clone> --reader` and `--contributor` write nothing into the clone, so `library pull` and `sync` keep working; an owner is told that `skaile.manifest.yaml` changed and needs a commit (p1600). A scaffold placeholder body is a hard error in `asset import` and `add` too, with the `validate` line (p223). A `files:` entry that names a missing file fails the publish plan also when the entry has a `root:` (p1404). `library index` leaves a manifest entry alone when the asset's name is invalid and prints only the invalid-name line (p1601). A requires/dependencies error prints one line without `ManifestRequiresError:` (p1602). Path-less `validate versions` and `validate changelog` check the cwd like plain `validate`, and exit 1 outside a library instead of falling back to the factory assets (p1194). An unquoted `@publisher/name` in `agent.yaml`, `skaile.yaml` or any YAML manifest gets the double-quote hint (p1750). `library create flow` writes a strict v2 flow (`schemaVersion: 2`, one example `agent` node, no `globals:`), and a flow with `run:` nodes but no `schemaVersion: 2` is refused instead of read as an inert legacy flow (p489).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Consume fixes from the 6.1.0 critique:
+
+  - `check`, `doctor`, `validate` and every command that reads `skaile.yaml` refuse a `dependencies:` that is no list, a `dependencies:` item that is no string and a `sources:` that is no list with one `skaile.yaml — parse error: …` line and exit 1. `add` and `source add` write nothing (p1620).
+  - `diff`, `update`, `info`, `remove` and `why` give the `Did you mean agent:@pub/name` hint that `add` gives for a kindless ref (p1425).
+  - `source list|add|remove|show|sync` on a `skaile.yaml` whose root is not a map print the one parse-error line, no stack, and `validate` flags the file (p1421).
+  - `add --dry-run` prints the version once, and for an agent the files each harness writes (`.claude/agents/<name>.md`, ...), not a folder it never writes (p1621).
+  - A symlink cycle inside a library prints one `! <library>: asset scan truncated (cycle) - the symlink … points back into the tree …` line on stderr, not a raw timestamped `[runner:asset-scan]` record (p1622). New core export: `setWalkTruncationSink`.
+  - `add` of a manifest entry whose asset file now names another asset prints the `validate` line (`… now names "<name>" … run skaile library index <library>`) (p1603).
+  - `outdated` names `skaile install`, as `check` does, for a library asset that changed since the lock; a newer version still says `skaile update` (p1604).
+  - `run <flow> --dry-run` names every node skill that is not deployed, and the `skaile add` that fixes it (p1757). New `AssetManager.undeployedSkills()`.
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Harness: a `skaile.yaml` without `agent-config` uses one default, claude-sdk, which deploys to `.claude/`: `config show`, `run`, `repl` and `serve` now agree with `add` and `install` (p1670). After `harness set`, `install`, `list` and `add` name the copies of every other harness folder (`.claude/`, `.omp/`, `.codex/`) as stale, one line per folder (p1671). The repl banner names the agent the session runs; deployed agents are listed apart as not selected (p1672). The codex delegate warning is printed when an agent file was written, not when only a skill was added or restored (p1673). `config set model` prints `passed on as the model id <id> (no provider selected)` when no registry entry names or lists the model, and `config show` prints `passed on as:` (p1674). One message names the harness names of every command (`config set harness`, `harness set`, `init --harness`, `add --harness`, `integration --harness`, `run`, `repl`) (p1753). `install`, `list` and `config show` refuse an unknown `harness:` in `skaile.yaml` as `validate` does (p1754). A failed plugin install names its own reason for each plugin (p1272). `plugin install ./dir` and `file:../dir` exit 1 with one line that names the `name@file:/path/to/dir` form (p1737).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Protocol: the omp harness forwards `GIT_CONFIG_GLOBAL` to the agent's shell like every other harness (p1738). `serve` prints one `x` line for an unknown harness (p1731), a `--project-dir` that is no directory (p1732) and an `agent.definition` that does not resolve, which `validate` now refuses too (p1733). A `serve` option that takes a value and is followed by a flag names the missing value (p1730). The provisioned-mode error names `session_init` and its `secrets` map (p1734). `capability_result` failures always have the shape `{ok:false, code, message}` (p1736). A connector with `adapter:` gets the `validate` text, not a warning about the driver "undefined" (p1739). `serve --harness omp --model <x>` asks omp for its models and refuses a model it does not list before the ready line (p1334).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Restore fixes from the 6.1.0 critique:
+
+  - `install --locked` on a machine where the lock's library is not registered restores the files from the lock `url:` when every file has the locked hash, prints one notice line per library, exits 0, and `check` and `doctor` stay green (p1655). It never takes other bytes from a `sources:` repository instead (p128).
+  - Script files keep their exec bit in a store `add`, in `install --locked` from the lock url, in a store cache an older CLI filled, and in `../` compose folders copied next to an agent (p1657). New library exports: `isScriptBytes`, `restoreScriptModes`.
+  - `No skaile.yaml found` shows `--project-dir` after the command name, where it works (p1656).
+  - A factory asset is locked as `source: {url: factory, commit: <@skaile/workspaces version>}` instead of the ai-assets GitHub url at the all-zero commit (p1755). An older lock is still read and is rewritten by the next `add`, `install` or `update`. New core exports: `FACTORY_SOURCE_URL`, `LOCK_FACTORY_URL`.
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Store fixes from the 6.1.0 critique:
+
+  - `check`, `doctor`, `outdated` and `diff` no longer call the source of a freshly added store asset missing: the lock lookup uses the locked version, so assets of any store repo (not only ai-assets) pass (p380).
+  - A failed `skaile update` keeps the warm catalog cache on a REST-framed catalog too (p960).
+  - `source add` after `source remove` of the last source writes a block `sources:` list (p1690).
+  - `source manifest verify|rebuild|edit|publish <name>` finds the manifest `init` wrote for a non-GitHub URL by its bare repo name or slug (p1691).
+  - A rejected `SKAILE_GITHUB_PAT` prints one warning and the public repo is still read (p1692).
+  - `diff` labels its sides `(deployed)` and `(library)`/`(source)`/`(rendered)` instead of printing timestamps (p1693).
+  - `skaile search <word>` without a hit prints `No results for "<word>" (local and store).` (p1694).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Upgrade: `add --global --harness X` on an asset that is already global adds X to its harness set and deploys there; the new `--only` flag replaces the set (a copy left in a harness that drops out is named, not deleted). `add --global` prints the paths it wrote, harness by harness (p1640). `check` keeps reporting a hand-edited deployed file after a library version bump, and `update` and `install` stop before they replace it, name the file and need `--force` (`update` and `install` both take it). The lock records the bytes of a copied library asset (`copied:` in `skaile.lock.yaml`) for this (p1641). A failing `install --locked` writes nothing: a library that changed since the lock or a `../` compose folder that moved leaves every restorable file as it is (p1642). `migrate assets --write` refuses a bundle or old persona/ruleset file whose final kind and name is that of a preset, ruleset or persona file the repo already holds (p1241). `check` names `skaile update` for a `../` compose folder the library changed, as `install --locked` does (p1711).
+
+### Patch Changes
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Docs: the command and protocol pages now describe what the 6.1.0 critique found wrong. `runner/api-reference.md` lists `session_init` and no longer the removed `provision_secrets` and `configure` (p1735); the flow example creates its skill in the `personal` library of tutorial 01 (p1756). Other fixes cover `files:` paths and `--description` limits in the library pages, `--project-dir` after the subcommand, library-less `install --locked`, hand-edited deployed files and `--force`, the global harness set, the default harness of a `skaile.yaml` without `agent-config`, the repl banner, stale harness copies, `validate versions` outside a library, source manifest slugs, search with no hit, the unused `secrets.timeoutMs`, local plugin specs, and the planned-only commands of the curriculum page.
+
+- Updated dependencies [[`7af33f2`](https://github.com/skaile-ai/workspaces/commit/7af33f2cf748dab42e4a5114e872ff97f55036ca), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d)]:
+  - @skaile/workspaces@6.2.0
+
 ## 6.1.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skaile-cli",
-  "version": "6.1.0",
+  "version": "6.3.0",
   "description": "Run the Skaile CLI via `npx skaile-cli` — thin wrapper around @skaile/workspaces",
   "type": "module",
   "bin": {
@@ -25,7 +25,7 @@
     "asset-manager"
   ],
   "dependencies": {
-    "@skaile/workspaces": "6.1.0"
+    "@skaile/workspaces": "6.3.0"
   },
   "publishConfig": {
     "access": "public"