[dofastted]

Ship v1.4.069 with the current local Claude 2.1.321 UPX binaries and the cluster CRAG fix. The remote slot publisher now includes signed manifest.json and hashes it into the content digest; this prevents old manifest/new encrypted payload mixing, the direct cause of the failed AWS restart. Payload manifest uses the standard versioned v1.4.069 tag. Focused cluster/kernel tests pass; 71 tests pass in the local targeted run. No credentials or plaintext core committed.

---

Note

Medium Risk
Changes cluster CRAG publication and pinned production binaries; incorrect rollout could leave nodes with mismatched manifest and payload or failed license validation until rollback.

Overview
v1.4.069 is a release that pins the Claude 2.1.321 UPX toolchain and fixes cluster CRAG slot images so hot-replaced encrypted packages stay internally consistent.

Cluster slot image building (cragSlotPayload in slot-image.mjs) now ships opt/kin/crag-v2/manifest.json alongside the wrapper and encrypted members, and folds the manifest path and hash into the image content digest. That stops nodes from reusing an old signed manifest with new bootstrap/core bytes—a mismatch that broke license checks and VM recovery after AWS restarts.

Release metadata is bumped (VERSION, CHANGELOG, deploy/payload.json release v1.4.069, deploy/arm64-cli.json CLI hashes, docs/releases/v1.4.069-notes.md). A unit test asserts baked slot images include manifest.json at mode 0644.

^{Reviewed by Cursor Bugbot for commit bc0aa9f. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 303efab7-44a6-47e7-986d-5cacb63fa1c3)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 8240e989-ddc7-435a-8981-ebd7568bb3be)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 7283d842-9761-450a-9f20-93d20f425bed)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: a21a94a6-b258-4c05-b276-91463fa6424c)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 31e56672-963a-4daa-ae10-b2e4f086d520)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: da57d9c1-d538-451f-a8e0-1db50f6970a3)