Skip to content

fix(vent): always report consolidate outcome, not just non-empty filings - #386

Merged
getappz merged 1 commit into
masterfrom
task/215
Aug 4, 2026
Merged

fix(vent): always report consolidate outcome, not just non-empty filings#386
getappz merged 1 commit into
masterfrom
task/215

Conversation

@getappz

@getappz getappz commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • hook.rs's vent-consolidate diagnostic previously only eprintln!'d when items_created was non-empty, so "consolidation ran, nothing to file" and "consolidation is silently broken" were indistinguishable from the outside (item hook: deprecate inert PreCompact FTS5 scorer, keep as no-op stub #215).
  • Both call sites (session_start, prompt_submit) now always report the outcome, and a caught panic in catch_unwind is surfaced instead of swallowed silently.

Testing

  • cargo build / cargo check clean
  • cargo fmt --check clean
  • cargo clippy --all-targets --all-features -- -A unsafe_code -A clippy::pedantic -D warnings clean
  • cargo test --bin agentflare vent — 35 passed, 0 failed

Previously the hook only eprintln'd when items_created was non-empty, so
'consolidation ran, nothing to file' and 'consolidation is silently broken'
were indistinguishable from the outside. Also surface a caught panic
instead of swallowing it silently.
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@getappz, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: faf21191-de48-4227-8078-b64ec0831f15

📥 Commits

Reviewing files that changed from the base of the PR and between d1f4607 and ae18ac7.

📒 Files selected for processing (1)
  • src/hook.rs

Comment @coderabbitai help to get the list of available commands.

@getappz
getappz merged commit 9a83c4c into master Aug 4, 2026
16 checks passed
@getappz
getappz deleted the task/215 branch August 4, 2026 07:39
getappz added a commit that referenced this pull request Aug 11, 2026
…ge collisions (#456)

* git-shim/worktree residual polish: teardown messaging, branch-create accuracy, stranded-checkout recovery

- worktree deny message now distinguishes provisioning (claim) from
  teardown (check_merge/release/audit --prune) so an agent denied
  mid-teardown gets the exact cleanup action (vent #350)
- is_branch_create() classifies checkout -b/-B and switch -c/-C;
  canonical-checkout deny says 'create a new branch' instead of the
  misleading 'would detach HEAD' (vent #395)
- audit_orphans flags worktrees stranded on the default branch (intact
  gitdir) so worktree audit --prune clears the gh pr merge --delete-
  branch / post-merge-sync collision root cause (vents #351/#394/#423)
- AGENTFLARE_GIT_ALLOW_CANONICAL_MUTATE now also lifts the default-branch
  checkout/switch deny in the canonical checkout, giving stranded
  checkouts a sanctioned way back (vent #386 residual)
- allowlist classify.rs (already 1604L on master) in the LOC gate

Agentflare-Agent: 1
Agentflare-Branch: task/441
Agentflare-Item: 441

* fix(git-shim): close branch-create detection gaps, protect dirty stranded worktrees

CodeRabbit review on PR #456:
- is_branch_create only matched exact -b/-B/-c/-C, missing --orphan
  (checkout+switch), switch's --create/--force-create long forms, and
  attached short-option spellings (-bname). Those forms slipped past
  both would_detach_head and deny_canonical_detach_reason undetected,
  letting an agent create a branch in the canonical checkout via e.g.
  'git switch --orphan x' or 'git checkout -bx' with no deny at all.
- audit_orphans' new on-default-branch detection could hand a dirty,
  uncommitted stranded worktree to gc_orphans for deletion; the only
  other gc_orphans caller (cleanup_item_worktree) already refuses on
  a dirty status check first. Apply the same guard here.

Agentflare-Agent: claude-code_2-1-227_agent
Agentflare-Branch: task/441
Agentflare-Item: 441
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