chore(release): 1.0.60

[anconina]

Description

Release bump 1.0.59 → 1.0.60.

Moves all 16 packages/*/package.json versions together — the umbrella comisai package bundles the others, so version drift between them surfaces at publish time rather than in local builds. No source, config, or documentation changes.

Release-protocol steps completed:

• All 16 package manifests bumped in one commit.
• Version-pin sweep is clean: grep -rn '1.0.59' --include='*.json' --include='*.mdx' --include='*.md' (excluding node_modules, dist/, lockfiles, and CHANGELOG) returns no hits.
• pnpm validate passes locally, enforced by the pre-push hook (✓ pre-push: validate passed.) — docs:check, build:clean, cycles, cycles:refs, lint:security, test:coverage.

Content shipping in this release (already merged and CI-green on main): #491, #492, #493, #494, #495, #496.

Related Issue

N/A: version-manifest-only change. No runtime behavior, architecture, or security expectation is altered.

Type of Change

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

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 — N/A, no behavior change
• Documentation updated (if applicable) — N/A, docs do not pin release versions
• 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 chore. The diff touches only the "version" field of the 16
packages/*/package.json manifests — no packages/*/src/** change, so the
tests-first rule does not apply.

Evidence and Residual Risk

• Contribution path: not applicable — release versioning only.
• Evidence level: deterministic test (pnpm validate full gate, green via the pre-push hook).
• Tested profile: macOS (darwin 25.3.0), Node 22, no isolation mode exercised, no provider/model involved, existing workspace state.
• Residual risk: pnpm validate is the cross-platform floor, not the full CI surface. It does not run the Docker image build, *.linux.test.ts (skipped on macOS), or the integration tier. Those are covered by this PR's CI run and, post-tag, by docker-release.yml / dockerhub-release.yml. The publish itself is verified after the tag workflows conclude via npm view comisai dist-tags.

Additional Notes

After merge: tag v1.0.60 on the merge commit and create the GitHub release. The tag triggers npm-publish.yml (which waits for ci.yml on the tagged commit to conclude success), docker-release.yml, and dockerhub-release.yml.