Skip to content

chore(release): prepare 0.8.26-alpha.10 - #1302

Merged
lavaman131 merged 1 commit into
mainfrom
prerelease/0.8.26-alpha.10
Jun 8, 2026
Merged

chore(release): prepare 0.8.26-alpha.10#1302
lavaman131 merged 1 commit into
mainfrom
prerelease/0.8.26-alpha.10

Conversation

@lavaman131

@lavaman131 lavaman131 commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Prepares the 0.8.26-alpha.10 prerelease. The primary change is a comprehensive overhaul of the compaction documentation to accurately reflect the transcript-bound Verbatim Compaction planner shipped in #1301.

Changes

Documentation (packages/coding-agent/docs/)

  • compaction.md — Major rewrite covering:
    • What "verbatim" means: append-only JSONL, logical deletion by stable entry/content-block ID, no generated summaries or paraphrasing
    • Updated 7-step "How It Works" flow (transcript file, tool-guided planner, fail-closed validation, rebuild)
    • New Transcript-Bound Tools section documenting context_search_transcript, context_read_entry, context_delete, and context_grep_delete (bulk-delete with guardrails, match-count caps, cumulative state)
    • New Protection and Validation Rules section (user messages, last-five entries, error states, tool-call/result orphan consistency)
    • New Standard vs. Critical Overflow Mode section (threshold/manual vs. overflow recovery pass)
    • ContextCompactionEntry TypeScript structure (deletedTargets, protectedEntryIds, stats, backupPath)
    • Clarified keepRecentTokens is a legacy summary-compaction setting; Verbatim Compaction protects recent entries structurally
    • Renamed "Summary Format" → "Legacy Summary Format" throughout to distinguish from Verbatim Compaction
  • extensions.md — Updated ctx.compact() description to reflect transcript-bound deletion tools and that non-empty customInstructions now fails (not silently ignored)
  • sdk.md — Added note that compact() accepts no custom summary instructions and runs the same planner as /compact
  • Minor terminology fixes in json.md, rpc.md, session-format.md, sessions.md, settings.md, usage.md

Release Artifacts

  • Bumped all workspace packages to 0.8.26-alpha.10
  • Added 0.8.26-alpha.10 changelog sections across all packages
  • Refreshed bun.lock

Validation

bun run typecheck
(cd packages/coding-agent && bun run docs:check)
bunx --bun mintlify@latest validate
bunx --bun mintlify@latest broken-links
bun run test:unit
bun run hooks:run
bun run test:integration
(cd packages/coding-agent && bun run build)

@claude

claude Bot commented Jun 8, 2026

Copy link
Copy Markdown

Review: PR #1302chore(release): prepare 0.8.26-alpha.10

Reviewed against CLAUDE.md release/changelog conventions and verified every doc claim against the actual source in packages/coding-agent/src/core/compaction/. This is a well-executed release-prep PR — version bumps, changelog entries, and a substantial, accurate rewrite of the compaction docs. ✅ Recommend merge.

Version & changelog hygiene — correct

  • All 6 workspace packages bumped consistently 0.8.26-alpha.9 → 0.8.26-alpha.10, and bun.lock refreshed to match. No stragglers.
  • Changelog entries follow the repo format: new version sections added, [Unreleased] left empty, prior released sections untouched, dated 2026-06-08 (matches today). 👍

Documentation accuracy — verified against source

I spot-checked the substantive compaction.md rewrite claim-by-claim and they all hold up:

  • Transcript-bound toolscontext_search_transcript, context_read_entry, context_delete, context_grep_delete all exist with those exact names (context-compaction.ts:92-95). The context_grep_delete guardrails described (literal/regex, maxMatches, expectedMatchCount, skips protected) match the impl/prompt.
  • "Last five context-eligible entries" protected in standard mode — confirmed: recentEntryIds = ...slice(-CONTEXT_CRITICAL_OVERFLOW_RECENT_ENTRY_COUNT) with the constant = 5, applied via isProtectedEntry during prepareContextCompaction (context-compaction.ts:576,611).
  • customInstructions now fails (doc changed from "ignored" → "fails") — accurate: compact() throws "Custom compaction instructions are not supported..." on a non-empty value (agent-session.ts:2017-2018).
  • ContextCompactionEntry / ContextDeletionTarget / ContextCompactionStats — the documented TypeScript shapes match session-manager.ts:78-97 exactly.
  • Standard vs. critical overflow modeContextCompactionMode = "standard" | "critical_overflow", the single retry pass, and protected-entry eligibility during overflow all match (context-compaction.ts:34, 947-975, 2019-2022, 2148).
  • context_compact compatibility RPC + historical event names — confirmed (rpc-mode.ts:541, rpc-types.ts:45,162, agent-session.ts:161-179).

Minor nitpicks (non-blocking)

  • In the ContextCompactionEntry code block (compaction.md), id / parentId / timestamp are shown inline, but in source they're inherited from SessionEntryBase. Accurate for the on-the-wire JSONL shape; optional to add a "(plus base entry fields)" note for readers cross-referencing the type.
  • Doc source-file links point at /blob/main/.... Fine for living docs, but they reference symbols on this line of work — they'll only resolve once merged to main.

Coverage

No code changes, so no new tests are warranted. The PR body lists a thorough validation matrix (typecheck, docs:check, mintlify validate + broken-links, unit/integration, hooks, build) — appropriate for a docs+release PR.

Nice attention to detail keeping the legacy-summary vs. Verbatim-Compaction distinction consistent throughout (usage.md, sessions.md, settings.md, sdk.md, json.md, rpc.md).

@lavaman131
lavaman131 merged commit de6186d into main Jun 8, 2026
10 checks passed
@lavaman131
lavaman131 deleted the prerelease/0.8.26-alpha.10 branch June 8, 2026 07:45
@mintlify

mintlify Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
bastani 🔴 Failed Jun 8, 2026, 7:58 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

lavaman131 added a commit that referenced this pull request Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant