chore(release): 1.0.55

[anconina]

Description

Release chore for v1.0.55. Bumps all 16 packages/*/package.json to 1.0.55 (they must move together — the umbrella comisai package bundles the others, so version drift surfaces at publish time, not in local builds) and cuts the CHANGELOG's [Unreleased] section into ## [1.0.55] - 2026-07-25.

v1.0.54 shipped without cutting a CHANGELOG section, so the [1.0.55] entry aggregates every user-visible change since 1.0.53 and states that explicitly, linking the v1.0.54 release for its generated notes. Link references updated so [Unreleased] now compares against v1.0.55.

No packages/*/src/** change is included.

Contents since v1.0.54

• feat: durable proactive scheduling and background execution (feat: add durable proactive scheduling and background execution #344)
• fix(terminal): durable tmux under unsafeDisableSandbox via scrubbed server env + per-session -e (fix(terminal): durable tmux under unsafeDisableSandbox via scrubbed server env + per-session -e #341)
• docs: README/website/docs/package-metadata refresh (docs: refresh README, website, docs, and package metadata copy #333, docs: remove the live-catalog evidence table from the README #334)

Related Issue

N/A: release version bump limited to package manifests and CHANGELOG.md. No runtime behavior, architecture, or security expectation changes.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Refactor

Release chore — version manifests plus the CHANGELOG section cut.

Checklist

• Targeted checks for the changed area pass
• Full repository validation passes (pnpm validate)
• New or changed behavior has a test that demonstrated the RED state before the production change — no behavior change in this PR (manifests + CHANGELOG only)
• Documentation updated (if applicable)
• No secrets or credentials committed
• Security implications considered
• The change is focused on one concern and links the related issue, or states the allowed N/A reason

RED Test Proof

EXEMPT: release version bump — packages/*/package.json manifests and CHANGELOG.md only, no packages/*/src/** change.

Evidence and Residual Risk

• Contribution path: not applicable — release versioning chore
• Evidence level: deterministic test — full pnpm validate on the bump commit
• Tested profile: macOS (darwin 25.3.0), Node 22.21.1, pnpm 10.34.4; docs:check, build:clean, cycles, cycles:refs, lint:security, test:coverage all green — 2319 test files / 41121 tests passed, per-package coverage floors met
• Residual risk: pnpm validate is the cross-platform floor, not the full CI surface. It does not exercise the Docker image build, *.linux.test.ts (skipped on macOS), or the integration/tarball tiers (validate:full, Linux-only). Those run in CI on this PR. The version-pin sweep for 1.0.54 is clean: no *.json / *.mdx / *.md pins remain outside the bumped manifests.

Additional Notes

Every release from 1.0.40 through 1.0.54 has been a patch bump regardless of content, so this follows that convention despite #344 landing a feat.

Post-merge: tag v1.0.55 and gh release create, which triggers npm-publish.yml, docker-release.yml, and dockerhub-release.yml. Verify the publish landed with npm view comisai dist-tags — that job has silently drifted before.

🤖 Generated with Claude Code