skaile-cli 6.6.0 → 6.7.0

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Changelog
 
+## 6.7.0
+
+### Minor Changes
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - An agent is rendered once per instance. `add agent:@crew/bookkeeper` writes `.claude/agents/<instance id>.md` (omp: `.omp/agents/<id>/`, codex: `.codex/agents/<id>.toml`) and no file named after the asset. The asset-named file is written only for an agent that no instance binds, and an agent called as a `binding: run` role gets no native file (p416). `install`, `update` and `add` remove the asset-named file an earlier CLI wrote when skaile still owns it (the bytes equal the lock); an edited file stays. Renaming an instance in `skaile.yaml` converges with one `install`: `check` is clean at once (p2080). `install` no longer says `the deployed copy is gone` when the instance file is there (p2083). `update` re-runs the rebuild for every agent that holds a pin, so `check` and `run` stay clean after a library edit (p1911).
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - The repl banner lists the declared instances for `--instance` and the delegate sub-agents on their own line. The generated `.gitignore` now ignores `.skaile/composition-runs/` and `.skaile/agent-instances-managed.json`, an existing project gets the lines on the next write, and only the 20 newest run snapshots are kept. `run --dry-run` names the bound instances and `--instance <id>` when `agents:` is set and no primary agent is. `serve` refuses an `agents.<id>.ref` that does not resolve with one line, as `validate` does. The docs say that `composition.<id>` is a name in the compile plan and that omp and codex reach a connector through `skaile connector`.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - A manifest entry whose root holds no files now fails `validate`, `library index` (exit 1) and the publish plan with one line, and `add` fails with the same line. `add` on a reader library or a source clone no longer tells the user to run `library index`; it names the owner's push and `library pull` or `source sync`. `library init --path` on a folder with `SKILL.md` at its root indexes the skill with root `.` instead of a ghost entry. `add` of a renamed flow no longer prints `LibraryEntryError:`. `library init --path` refuses a git clone with no branch checked out. `validate` of a connector without `id` prints one error and never the id `undefined`. `migrate assets` ends with `N file(s) not converted: ...` and exits 1 when it leaves a bundle behind. `.coverage`, `htmlcov/`, `.tox/`, `.nox/`, `.nyc_output/`, `*.egg-info/` and `._*` (any depth) and `dist/`, `build/`, `coverage/` (directly in the asset root only) are no longer deployed or hashed, and `library index` warns once per untracked file in the root of an asset the git library already holds. `library create` without `--library` writes into the library whose folder holds the current directory and names it in the output. The `authoring-skaile-assets` skill shows the `composes:` entry shape.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - `skaile --help` now ends with a `More:` group that lists `asset`, `migrate`, `providers`, `auth`, `cache`, `npx`, `rebuild`, `verify` and `complete`. `config get <unknown key>` exits 1 with the key list, as `config set` does. `session show`, `switch`, `delete` and `resume --session` print `Run skaile session list to see the ids.` when an id matches no session and the project has sessions.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - A failing `install`, `update` or `install --locked` writes nothing: not `skaile.lock.yaml` (the upgrade of a 5.10.0 to 5.13.0 lock included), not a deployed copy, not an instance file (p1642). `check` and `outdated` print `! lock predates instance files: run skaile update` for a lock written before it listed the instance files, and the first run that writes prints `Restored <file>` for an instance file whose bytes it changes. The omp folder of an `AGENT.md` library agent names the version the lock holds, not `1.0.0` (p2025). `migrate harness` labels each line with its scope (`project settings.json`, `user settings.json`), changes the user-level `settings.json` only with `--user`, and keeps a one-line `settings.json` on one line.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - The plugin store no longer trusts `.skaile/plugins/.reconcile-hash` when `node_modules` is missing a declared package, so a clone or a copied store installs its plugins again; `skaile init` adds the hash file to `.gitignore`. `plugin install` loads the new plugin after the other declared plugins, so a target id that one of them already registers fails the install and restores `skaile.yaml`. `plugin install` prints `Added` or `Updated` only after the install worked. `resolveLanguageModel` refuses `<x>/<y>` when `<x>` is no provider, also for a registry whose entries list no models, so a typo in the provider id never sends a credential to another entry.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - Every failed `capability_result` now carries `error` (equal to `message`), whichever handler answered. `serve --port 0` names the port it got in the no-token WARNING. The agent's managed gitconfig also includes `~/.config/git/config` (or `$XDG_CONFIG_HOME/git/config`), before `~/.gitconfig`, as git reads them. A git command that fails because the mount token is withheld ends its error with the cause and the fix, for example `token withheld: your global git config sets http.sslCAInfo; use GIT_SSL_CAINFO or remove the key`. A claude-sdk turn that fails on an expired login sends one fatal `error` with `category: "auth"` and no extra `text` event. A default `serve` that no client sent `session_init` to buffers the events of a turn that ran while no client was connected. The docs now say that a prompt before `session_init` is held in provisioned mode, and every version gate reads `major > N || (major === N && minor >= M)`.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - `run --dry-run` now always prints the plan, then one `✗` line per problem the real run would stop on, and exits 1 when there is one. The problems are a missing harness program (`omp`, `gemini`, `qwen`, `opencode`, `goose`, `continue`) or SDK (`claude-sdk`, `codex`), a provider surface the harness cannot speak (`claude-sdk` with `--model ollama/llama3`, `gemini` or `qwen` with an entry they cannot bind), and a model the harness refuses. One preflight per harness serves `run`, `run --dry-run` and `repl`. An id no registry entry lists (`nosuch/foo`, `meta-llama/Llama-3.3-70B`) now reaches omp exactly as typed instead of as `<first entry>/<id>`; omp is asked whether it lists it. `run --help` shows that `claude-code` (deploy) is `claude-sdk` (run). The `run` docs and tutorial 03 say that a dry run exits 1 on a missing SDK or program.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - `outdated` no longer says `All assets are up to date.` for a source it could not compare: a clone whose `origin` is another repository than the declared url, or a clone folder with no git checkout, is named and `outdated`, `check` and `doctor` exit 1. A clone origin that differs only by case, a trailing slash or `.git` is the same repository. `source sync` points a changed origin back at the declared url. `skaile.yaml` `sources[].publisher` and `branch:` follow the rules of `source add`, and `validate` refuses a bad one with one line. `update` re-locks only what `outdated` lists: a dependent asset whose files did not change keeps its lock entry. A kind-qualified ref of the wrong kind says `It is an agent: agent:@pub/name.`. `library init --git <empty remote>` commits its scaffold, so `library pull` and `sync` work at once; the line for uncommitted changes names `skaile library commit`. A diverged source clone names the unpublished commit and the reset command. `source sync` replaces a clone folder with no git checkout; `source add` checks out the only branch when the remote `HEAD` names a missing one. `library init --git` and `library link` refuse a remote a source already clones. A source clone's library row is derived from the clone: `library list` shows it only in a project that declares the source, and it goes with the clone.
+
+- [#1126](https://github.com/skaile-ai/workspaces/pull/1126) [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9) Thanks [@mortegro](https://github.com/mortegro)! - `outdated`, `check` and `doctor` now name the locked store assets they could not check when the store does not answer (`store unreachable: skill:@admin/review#0.1.0 not checked (...)`) and exit 1, as `install` and `update` do. An air-gapped client (`catalog.cache_ttl: 0`) gets the same line as information and exits 0; `catalog.url: local` and `install --locked` stay offline-safe. `info` of a locked store skill shows the locked version and the upstream repository and commit as `source:`, with the path of the copy on a `deployed:` line. An agent whose `extends` parent is not part of its copy prints one plain line per run instead of a raw path line.
+
+### Patch Changes
+
+- Updated dependencies [[`6dffc64`](https://github.com/skaile-ai/workspaces/commit/6dffc6410196be90b9d147f1fa7b785396fee37e), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9), [`124a7de`](https://github.com/skaile-ai/workspaces/commit/124a7dedbfc306165a7d9181e6ba47ec5302e0c9)]:
+  - @skaile/workspaces@6.7.0
+
 ## 6.6.0
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skaile-cli",
-  "version": "6.6.0",
+  "version": "6.7.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.6.0"
+    "@skaile/workspaces": "6.7.0"
   },
   "publishConfig": {
     "access": "public"