release: ship v2026.5.99 — T9964 follow-ups (briefing diet + ferrous-forge + release-prepare.yml)

[kryptobaseddev]

Summary

Ships PR #459 (T9964 v5.97 follow-ups) as v2026.5.99, after v5.98 (#460, T9961+T9962) shipped in parallel.

Contents

• Real briefing diet (T9974 AC1 was missed in v5.97): default cleo briefing now ≤1000 tokens via progressive disclosure. peerLearnings/decisions emit {id, title, createdAt, _next.fetch} only (full body via --memory-detail). relatedDocs surfaces slug+type instead of useless attachmentId. memoryContext.recent* titles capped at 80 chars.
• Ferrous-forge fixture compliance: packages/cleo/test/fixtures/release-test-rust-crate/Cargo.toml now uses edition=2024 + lints sections. Pre-commit hook passes without --no-verify on release commits.
• release-prepare.yml workflow (closes T9781): cleo release open <version> now actually dispatches the GH Actions workflow that cuts the release branch, bumps versions, and opens the PR.
• Workflow jq bug fix: Bump workspace @cleocode/* dep refs step used (.dependencies // {}) |= ... which jq rejected with "Invalid path expression" on packages/adapters/package.json (no dependencies field). Replaced with if has("dependencies") then ... else . end per jq's path-expression semantics. This was caught during my v5.98 dispatch attempt.

Version bumps

• 21 workspace packages/*/package.json + root package.json → 2026.5.99
• Cargo.toml [workspace.package].version → 2026.5.99
• Cargo.lock refreshed for 13 workspace crates

Test plan

• vitest briefing-diet asserts ≤1000 default, ≥1500 with --memory-detail (already merged in chore(T9964): v5.98 follow-ups — real briefing diet + ferrous-forge fix + release-prepare.yml #459)
• release-prepare.yml syntax valid + jq fix verified
• CI on this PR
• Tag push triggers release.yml → npm publish
• Global install + post-publish validation

🤖 Generated with Claude Code