chore: remove cache analyzer

[julienrbrt]

Overview

This tool does not do anything anymore.

Summary by CodeRabbit

• Chores
  • Removed the internal cache analyzer development tool and its accompanying documentation as part of routine maintenance.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2cb21394-9762-45e0-95cf-ba2b7da86207

📥 Commits

Reviewing files that changed from the base of the PR and between f9c8717 and 209a605.

📒 Files selected for processing (2)

• tools/cache-analyzer/README.md
• tools/cache-analyzer/main.go

💤 Files with no reviewable changes (2)

• tools/cache-analyzer/README.md
• tools/cache-analyzer/main.go

---

📝 Walkthrough

Walkthrough

The entire cache-analyzer tool has been removed from the repository, including its documentation and Go CLI implementation. This tool previously analyzed pending DA events cache from sync nodes by loading and decoding Gob-encoded data files.

Changes

Cohort / File(s)	Summary
Cache Analyzer Tool Removal tools/cache-analyzer/README.md, tools/cache-analyzer/main.go	Deleted complete cache-analyzer tool comprising documentation and CLI program. Removed cache loading, decoding, event analysis, and formatted output logic including Gob type registration and the DataHashForEmptyTxs exported variable.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 The cache analyzer hops off the stage,
No pending events on its final page,
The tool departs with a gentle sigh,
Its gob-encoded bytes say goodbye! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is largely incomplete. While it includes the Overview section, the explanation is vague ('does not do anything anymore') and lacks the context, background, rationale, or issue reference specified in the template.	Expand the Overview section with more context on why the cache analyzer is being removed, any related issues, and the rationale for deprecation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: removal of the cache analyzer tool. It is specific, relates directly to the changeset, and follows semantic commit conventions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch julien/cache-analyzer

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Claude finished @julienrbrt's task in 51s —— View job

---

Code Review

• Gather context and read relevant files
• Check for remaining references to the deleted tool
• Provide review feedback

---

The deletion itself is clean and straightforward — removing a no-op tool is the right call. However, there's one incomplete cleanup:

.just/tools.just still references cache-analyzer in several places (lines 17–23, 27, 44–49, 53, 60, 69):

• build-tool-cache-analyzer recipe (lines 17–23)
• build-tools depends on build-tool-cache-analyzer (line 27)
• install-tool-cache-analyzer recipe (lines 44–49)
• install-tools depends on install-tool-cache-analyzer (line 53)
• clean-tools removes cache-analyzer binary (line 60)
• list-tools lists cache-analyzer (line 69)

Running just build-tools or just install-tools will fail after this PR merges since the source directory is gone. This file should be updated as part of this PR. Fix this →

No other issues — the removed code itself was straightforward cleanup.

[github-actions]

The latest Buf updates on your PR. Results from workflow CI / buf-check (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	⏩ skipped	✅ passed	✅ passed	Mar 24, 2026, 10:22 AM

[alpe]

uAck

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.14%. Comparing base (f9c8717) to head (209a605).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3192   +/-   ##
=======================================
  Coverage   61.14%   61.14%           
=======================================
  Files         117      117           
  Lines       12082    12082           
=======================================
  Hits         7387     7387           
- Misses       3868     3869    +1     
+ Partials      827      826    -1     

Flag	Coverage Δ
combined	61.14% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.