sliccy 6.255.6 → 6.256.0

package/dist/ui/packages/webapp/index.html

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>slicc</title>
     <link rel="icon" type="image/png" href="/logos/sliccy-color-1scoops-32x32.png" />
-    <script type="module" crossorigin src="/assets/main-DuumegMc.js"></script>
+    <script type="module" crossorigin src="/assets/main-DVD6CfWm.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/rolldown-runtime-Dd_uD5pT.js">
     <link rel="modulepreload" crossorigin href="/assets/modulepreload-polyfill-P2Xu9kJm.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-BLdHbfdN.js">
@@ -22,12 +22,12 @@
     <link rel="modulepreload" crossorigin href="/assets/image-markers-4eaAm9QS.js">
     <link rel="modulepreload" crossorigin href="/assets/core-DoHWT79Y.js">
     <link rel="modulepreload" crossorigin href="/assets/bridge-protocol-C52CnDIj.js">
-    <link rel="modulepreload" crossorigin href="/assets/providers-BKPSCdv4.js">
+    <link rel="modulepreload" crossorigin href="/assets/providers-B5VMaUWX.js">
     <link rel="modulepreload" crossorigin href="/assets/stored-accounts-ChNHYF68.js">
     <link rel="modulepreload" crossorigin href="/assets/bedrock-camp-compat-D6dUCn_T.js">
     <link rel="modulepreload" crossorigin href="/assets/bedrock-camp-extra-models-COVvjLB5.js">
     <link rel="modulepreload" crossorigin href="/assets/claude-model-version-3MWQoaco.js">
-    <link rel="modulepreload" crossorigin href="/assets/account-store-Bm5rV5bR.js">
+    <link rel="modulepreload" crossorigin href="/assets/account-store-DRK_jfiB.js">
     <link rel="modulepreload" crossorigin href="/assets/telemetry-kqkj0A7x.js">
     <link rel="modulepreload" crossorigin href="/assets/tray-follower-status-BAjnN7Ar.js">
     <link rel="modulepreload" crossorigin href="/assets/clipboard-eqmn97SP.js">

package/dist/ui/packages/webapp/upgrade-to-seven.html

@@ -5,7 +5,7 @@
     <!-- Seven's BIOS checks this before it offers the upgrade (slicc#4051). -->
     <meta name="slicc-six-upgrade" content="1" />
     <title>Moving SLICC 6 to seven</title>
-    <script type="module" crossorigin src="/assets/upgrade-to-seven-DPRmGGSp.js"></script>
+    <script type="module" crossorigin src="/assets/upgrade-to-seven-B2H6KnlF.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/modulepreload-polyfill-P2Xu9kJm.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-BLdHbfdN.js">
     <link rel="modulepreload" crossorigin href="/assets/renamed-providers-CKF5I4-o.js">

package/dist/ui/upgrade-to-seven.html

@@ -5,7 +5,7 @@
     <!-- Seven's BIOS checks this before it offers the upgrade (slicc#4051). -->
     <meta name="slicc-six-upgrade" content="1" />
     <title>Moving SLICC 6 to seven</title>
-    <script type="module" crossorigin src="/assets/upgrade-to-seven-DPRmGGSp.js"></script>
+    <script type="module" crossorigin src="/assets/upgrade-to-seven-B2H6KnlF.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/modulepreload-polyfill-P2Xu9kJm.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-BLdHbfdN.js">
     <link rel="modulepreload" crossorigin href="/assets/renamed-providers-CKF5I4-o.js">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sliccy",
-  "version": "6.255.6",
+  "version": "6.256.0",
   "description": "Browser-based coding agent with thin CLI server",
   "license": "Apache-2.0",
   "type": "module",
@@ -122,7 +122,7 @@
     "@semantic-release/exec": "7.1.0",
     "@semantic-release/git": "11.0.1",
     "@size-limit/file": "13.0.3",
-    "@tessl/cli": "0.115.0",
+    "@tessl/cli": "0.116.0",
     "@types/node": "24.19.2",
     "@vitest/browser": "4.1.11",
     "@vitest/browser-playwright": "4.1.11",

package/dist/ui/assets/SKILL-BbHV9IdF.js

@@ -1 +0,0 @@
-var e="---\nname: package-execution\ndescription: |\n  Use this when the user asks to run or install a JavaScript/npm package with\n  `npx` or `ipx`, or to run a `package.json` script with `npm run`. Covers\n  built-in hints, any required `ipk add` bootstrap, the `--force` bypass, and\n  how script bodies resolve installed bins.\nallowed-tools: bash\n---\n\n# JavaScript package execution\n\n`ipx` runs package bins from the nearest installed `node_modules`; `npx` is an alias with the same behavior. If no local bin or installed package resolves, it normally installs the requested package and runs its bin.\n\nBefore that network install, mapped package names that duplicate SLICC built-ins redirect to the built-in instead. The command exits non-zero and prints an actionable stderr hint naming the built-in and suggesting an invocation with the original arguments. The hint may also include an exact `ipk add` bootstrap; run that bootstrap first when present, then use the suggested built-in.\n\nPrefer the built-in. To deliberately preserve install-and-run behavior for the npm package, put `--force` before its name:\n\n```bash\nnpx --force <package> [args...]\nipx --force <package> [args...]\n```\n\nAlready-installed packages, locally resolved bins, and unmapped package names keep their normal behavior. Use `commands` to discover available built-ins instead of maintaining a package mapping here.\n\n## Installing and removing packages\n\n`ipk install <pkg>` (also `npm install`, `npm i`, `ipk add`) installs into `<cwd>/node_modules` and records the package in the nearest `package.json` — in the section it already occupies, or in `dependencies` if it is new. `ipk install -D <pkg>` / `npm install --save-dev <pkg>` records new packages in `devDependencies`. A bare name that is already declared is resolved against that existing range, not latest. Versions are picked as pnpm picks them: a range takes the `latest` dist-tag whenever `latest` satisfies it (`*` always takes `latest`), and deprecated versions are passed over unless nothing else fits. Unknown install flags fail instead of being ignored. `ipk install` with no package names installs declared `dependencies`, `devDependencies` and `optionalDependencies` without rewriting `package.json`. `ipk install -g <pkg>` installs into the shared global prefix at `/shared/lib/node_modules`, records direct dependencies in `/shared/lib/package.json`, and publishes PATH-visible `.jsh` delegators under `/shared/bin` for package bins. Every downloaded tarball is checked against the registry's published hash before it is extracted. An `EINTEGRITY` error means that package's bytes did not match and it was not extracted, but packages installed before it may already be on disk and `package.json` was not updated. Check the state with `ipk list`, then retry the install; don't work around it. Installed files keep the package's executable bits (as npm sets them: 0755 for anything the tarball marks executable, 0644 otherwise), and `bin` targets are always executable, so a package's scripts and helpers (e.g. `git submodule` from `@ai-ecoverse/wasm-git`) run without `chmod +x`. A tree installed before this is repaired the next time you install into it. Platform-specific optional dependencies are skipped unless they are built for wasm (`cpu: wasm32`); the `skipping optional dependency … (unsupported platform)` notes are expected, not errors. For a napi-rs package that doesn't list its wasm binding, add `<pkg>-wasm32-wasi` (e.g. `@oxc-parser/binding-wasm32-wasi`) yourself.\n\n```bash\nipk install lodash              # local project install\nipk install -D eslint           # record in devDependencies\nnpm install --save-dev eslint@8.57.1\nipk install -g typescript       # global install (shared prefix + PATH bin)\nnpm uninstall -g typescript     # remove from global manifest and reconcile tree\nnpm list -g                     # list direct global dependencies\nnpm root -g                     # print /shared/lib/node_modules\n```\n\nGlobal bins installed with `-g` are on the default `$PATH` via `/shared/bin/<name>.jsh` delegators — invoke them by bare name from any cwd (delegators run `ipx --global <bin>` so a same-named local package does not shadow the global install). Local uninstall/list/root work without `-g` against the cwd `package.json`.\n\n## Wasm programs (`wasm`)\n\nA global package that ships wasm-realm programs (a `slicc.commands` manifest in its `package.json`, or an `@ai-ecoverse/wasm-*` package with `bin/<x>` + `bin/<x>.wasm`; `\"abi\": \"wasi\"` marks WASI programs built from Zig, Go or Rust, which have no glue) makes each program a command: `ipk add -g @ai-ecoverse/wasm-<tool>`, then run it by name. `wasm --list` lists them; `which <name>` shows the package. A built-in of the same name (`sed`, `grep`, `cat`, …) still wins, so run the program with `wasm <name> ARGS...`. `wasm -t <name>` runs it interactively on the panel terminal (a TTY: `wasm -t bash` is a real bash prompt, with job control — ^Z, `jobs`, `fg`, `bg`); the agent's own `bash` tool has no terminal to lend. Installing `@ai-ecoverse/wasm-bash` also moves your own `bash` tool onto GNU bash (real pipes, `trap`, `select`, arrays, bash's exact semantics; `cd` and exports carry between calls, shell functions do not). A WASI module you have as a file runs directly too: `wasm ./tool.wasm ARGS` (or `./tool.wasm` in GNU bash); it sees the VFS with relative paths from your working directory, pipes like any program, and WASIX builds (Wasmer's registry: bash, coreutils, python with `subprocess` and `threading`) run with fork, exec and pipes; threaded builds (`wasm32-wasip1-threads`, pthreads) run a worker per thread, at most 64 per process (`SLICC_WASM_THREADS=N` for fewer). A WASI program that crashes says `wasm trap: …` (a Zig or Rust panic is `unreachable`); run it with `SLICC_WASM_BACKTRACE=1` to see the wasm frames under that line, the functions that panicked. A WASI server gets its socket from `wasm --listen PORT ./server.wasm` (the fd is in `$SLICC_LISTEN_FDS`; Go's `net.FileListener(os.NewFile(fd, \"\"))` serves on it), reachable from your other programs at `127.0.0.1:PORT`. Supplemental commands work as before. The terminal panel then opens in GNU bash too (`wasm --login` starts it; `exit` returns to the slicc prompt, and `wasm --login` starts it again). `export SLICC_SHELL=just-bash` switches both back. Wasm programs built with socket support talk over a private loopback network: a server listening on `127.0.0.1:PORT` in one of your wasm programs is reachable from your other wasm programs while it runs (the terminal panel and each scoop have networks of their own), and a program reaches the outside over HTTP through your network's proxy: `http_proxy` / `https_proxy` point at `127.0.0.1:3128` by default (`no_proxy` keeps `localhost` direct), so `curl http://…` works the way the shell's `curl` does, masked secrets included. HTTPS works too: the proxy terminates TLS with a certificate from your network's own CA, which `SSL_CERT_FILE` / `CURL_CA_BUNDLE` / `GIT_SSL_CAINFO` point programs at (`$HOME/.config/slicc/realm-ca-*.pem`; `-k` is never needed). A redirect reaches the program as it would any HTTP client (`curl -L` follows it), except on Sliccstart, whose fetch path follows redirects itself. No other traffic leaves: only `localhost` / `127.0.0.1` resolve. Once a Go toolchain package is installed, `go build` / `go run` build Go programs here (`go` is SLICC's driver; the output is a wasip1 program you run as `./prog`, or any `GOOS`/`GOARCH` whose standard library is installed; the standard library and your module's own packages only: no cgo, `//go:embed` or module downloads yet). Once a native CPython is installed, `python3` in GNU bash is native Python, and `pyodide` stays SLICC's Pyodide under its own name. Installed Python packages are on its path by themselves. Once `@ai-ecoverse/wasm-git` is installed, `git` in GNU bash is native git (in just-bash it stays SLICC's built-in; `wasm git …` reaches native git there). Native git authenticates by itself: its default credential helper, `git-credential-slicc`, hands it your GitHub login (or `$GH_TOKEN` / `$GITHUB_TOKEN`, or a `*_TOKEN` secret scoped to the host) masked, so `git clone` / `git push` over HTTPS to a private repo just work, and it commits as SLICC's git identity. Don't put tokens in remote URLs; your `~/.gitconfig` overrides both (`$HOME/.config/slicc/gitconfig` is the realm's system config, rewritten each run).\n\nAn installed wasm command may declare `\"args\": [\"-S\", \"gem\"]` in its `slicc.commands` manifest entry. SLICC places those fixed arguments before the arguments typed at the shell or passed by a child process. `${package}` in an argument expands to the installed package directory; use it to name a script such as `\"${package}/bin/gem\"`.\n\n## Conda / emscripten-forge (`ipk mamba`)\n\n`ipk mamba install <pkg>[=<version>]` installs emscripten-wasm32 packages from emscripten-forge / conda-forge into `/shared/lib/conda` (not `node_modules`). Executable files (shared objects, scripts) keep their executable bit. Prefer this for **forge C/WASM libraries** (for example `zlib`, `libpng`) that provide headers, `.a`, and SIDE_MODULE `.so` under that prefix.\n\nKeep using `ipk install` / `ipk add -g` for the **npm** packages that power these built-ins — forge names are not drop-in replacements today:\n\n- `convert` → `ipk add -g @imagemagick/magick-wasm@…` (forge `imagemagick` has no runnable `convert.wasm`)\n- `ffmpeg` → `ipk add -g @ffmpeg/core@…` (forge `ffmpeg` is libav `.a` only)\n- `python` → `ipk add pyodide@…` (no forge `pyodide`)\n\n```bash\nipk mamba install zlib          # newest indexed build → /shared/lib/conda\nipk mamba install zlib=1.3.1    # exact version\nipk mamba list                  # conda-meta inventory (warns about unreadable records)\nipk mamba uninstall zlib\nipk mamba --help                # channels, prefix, and thin-installer limits\n```\n\n## Running package.json scripts\n\n`npm run <script>` (also `ipk run`, `npm run-script`, and the `npm test` / `start` / `stop` / `restart` shortcuts) runs a `scripts` entry from the nearest `package.json`, in that package's directory. `npm run` with no script name lists what is available — read that list instead of guessing a script name.\n\n```bash\nnpm run                      # list scripts\nnpm run build                # run build, with prebuild/postbuild around it\nnpm run build -- --watch     # pass extra args to the script body\nnpm run build --silent       # no banner, script output only (either side of the name)\nnpm run lint -- --help       # --help after -- goes to the script, not to npm\n```\n\n`--silent`/`-s` and `--if-present` are npm's own flags anywhere before `--`; everything after `--` reaches the script untouched. Missing `start` falls back to `node server.js` when the package has one, and missing `restart` to `npm stop --if-present && npm start`.\n\nA bare bin word in a script body (`vitest run`) is rewritten to `ipx vitest run` when that package is installed, because `$PATH` does not cover `node_modules/.bin` shims. This also applies after keywords like `if`/`then`/`do`. A SLICC built-in with the same name wins, and an unknown word is not installed implicitly — install it with `ipk add <pkg>` first.\n";export{e as default};