Latest release

A patch release fixing octet update for every user, plus two terminal and workspace corrections. Publication and asset availability must be confirmed on the version-pinned release page; the source version alone does not establish publication. npm publication is separate.

Fixed#

• octet update no longer fails with release metadata exceeds the 65536-byte limit. The bound covered GitHub's whole releases payload, which carries every asset entry and the release notes body: v0.10.1 measured 75,595 bytes, so a healthy release was refused. The bound is 256 KiB, and the response still has a hard size limit, a fixed timeout and strict validation.
• --workspace accepts a working directory outside the workspace instead of failing with invocation directory ... is outside workspace. Relative paths resolve against the workspace, and workspace-trust admission and confinement are unchanged.
• Terse (non-expanded) tool-call previews show 12 input rows instead of 6 before truncating; Ctrl+O still reveals the complete value.
• The README badge, documentation index and Pi compatibility counts name the current release (they lagged after the 0.10.1 tag).

Known limitations#

• Binaries published before 0.10.2 carry the old 64 KiB bound and cannot read this fix; use the version-pinned installer if octet update reports a size-limit error.
• @gotgenes/pi-permission-system blocks a --print tool call for about 30 seconds before the host request timeout ends it, and the run still exits 0.
• Cold startup with a full 23-package Pi mirror can exceed 10 seconds.

Recovery for 0.10.0 and 0.10.1 installations#

Those binaries carry the old 64 KiB bound and cannot inherit this fix. Until you install 0.10.2, run the version-pinned installer from the release page, or the octet update fallback in installation. The published 0.10.1 release description was shortened so its API payload fits inside the old bound, which restores octet update for those users.