chore(release): 1.0.56

[anconina]

Description

Release bump to 1.0.56 across all 16 packages/*/package.json. No source changes.

This ships the fix for the broken global install (#350). v1.0.55 is unusable — every npm install -g comisai, and therefore every curl -fsSL https://comis.ai/install.sh | bash, fails before a single package is built:

npm error code ENOENT
npm error syscall spawn sh
npm error path .../comisai/node_modules/@google/genai

latest on npm stays broken until this tag ships, so the bump is the remaining blocker.

Also carried since v1.0.55: pi SDK 0.82.1 (#352), the Renovate backlog sweep (#353), and a @types/node bump (#335).

Release version-pin sweep is clean — only the 16 version fields move; no stray 1.0.55 in any JSON/MD/MDX.

Related Issue

N/A: version-bump-only release commit. The behavior change it ships was reviewed and linked in #350 (fixes #351); this commit adds no source change of its own.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Refactor
• Release (version bump only)

Checklist

• Targeted checks for the changed area pass
• Full repository validation passes (pnpm validate) — see caveat below
• New or changed behavior has a test that demonstrated the RED state before the production change — N/A, no behavior change here
• Documentation updated (if applicable) — docs no longer pin release versions
• No secrets or credentials committed
• Security implications considered
• The change is focused on one concern

pnpm validate caveat, stated plainly: a local run of this content reported 24 failures, all of which were collateral — a concurrent process in the same checkout ran build:clean, wiping and rewriting packages/*/dist mid-test-run. 21 failures were Failed to resolve entry for package "@comis/*" / Cannot find package, and the other 3 were assertions reading half-written modules. Every one of them passes on re-run against an intact dist (agent-handlers 219 passed, setup-memory 41 passed, delivery-tracer/setup-learning green). No failure referenced a version string, so the bump broke no assertion. CI on this PR is the authoritative gate and runs the full Linux tiers.

RED Test Proof

EXEMPT: version-bump-only release commit — no packages/*/src/** change.

Evidence and Residual Risk

• Contribution path: not applicable — release metadata only.
• Evidence level: live integration run of the payload this release ships. A tarball built from this tree's parent commit was installed on a factory-reset Ubuntu 24.04 host (no Node, no service user) through website/public/install.sh: installer exit 0, the bundled-dependency repair pass succeeded, all 11 bundled-provider dependencies resolve, zero empty scope dirs, systemd + Xvfb active, daemon booted with 0 errors and 0 restarts, comis doctor 9 pass / 0 fail, and comis system-health returned a real report.
• Tested profile: Ubuntu 24.04 (aws), Node 22.23.1, npm 10.9.8, dedicated comis system user, systemd, fresh global prefix; pnpm validate on macOS.
• Residual risk: pnpm validate:full and a Docker image build have not been run on Linux. docker-release.yml only fires on the tag, and its selective COPY packages/<n>/package.json list is hand-maintained — the drift class that broke the image build once before. dockerfile-workspace-packages.test.ts covers it in validate, but the image itself is unbuilt until the tag exists; if it fails there the npm publish still succeeds and only the images are missing, which is recoverable by fixing forward and re-cutting the tag. Three defects found during the clean-room install (comis init accepting an under-length gateway token into a systemd restart loop; comis doctor's PID-file check false-negative under systemd; init --quick relocating the documented log path) are not fixed here and ship as-is — none affects installability.

🤖 Generated with Claude Code