Skip to content

refactor: remove the storage inspector - #49

Merged
ragnorc merged 2 commits into
mainfrom
refactor/remove-storage-inspector
Nov 1, 2026
Merged

ragnorc merged 2 commits into
mainfrom
refactor/remove-storage-inspector

Conversation

@aaltshuler

Copy link
Copy Markdown
Contributor

Part of the plan to cut Studio's bloat. The storage inspector is a diagnostic tab, and its name collides with the right dock's Inspector. Nothing depends on it except its startup call and its menu and palette entries.

This removes crates/inspectors, OpenInspector, and the session reads only it used (server_state, ServerState, branch_snapshot, snapshot_of). Spec 010 is marked superseded, and names 8b26a45 as the last commit with it.

  • A saved Storage tab is skipped on restore, as any tab of an unregistered kind is. The other tabs stay.
  • GraphClient::readiness no longer has a caller outside tests. I kept it, because graph_client types the whole contract and its route tests call it.

Test

  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test -p graph_store -p studio -p studio_actions. feature_reads_are_counted_while_they_run now counts the two change reads, since the four server reads are gone
  • cargo deny check, check-layers.py, check-brand.py, check-design-tokens.py, cargo fmt --all --check

The full workspace test suite wasn't run locally, because only these crates' code changed beyond the removal. I didn't open the app.

🤖 Generated with Claude Code

aaltshuler and others added 2 commits October 31, 2026 20:40
A diagnostic tab reached through a name that also means the right dock,
which nothing else depends on. Its session reads go with it. The client
keeps `readiness`, as it keeps every route of the contract it types.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ragnorc
ragnorc merged commit 8509aaa into main Nov 1, 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.

2 participants