Byte-aware deferral sort

What it does

Decides which MCP tools to defer by the size of their definitions rather than by their count.

Source

ganja-code-v2l (byte-aware deferral sort).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README says nothing about MCP or deferred loading (README.md:6).
• Today's terminal users: The threshold counts tools on purpose — "the unit a person can count in /mcp's own listing" (crates/ganja-tool/src/deferral.rs:86-90) — while the byte-accurate signal stays available.
• Evidence: No report shows the count to be the wrong proxy.

Depends on

Nothing.

Verdict

• Verdict: park
• Reopens: when a use report shows that the tool count is the wrong proxy for context cost (for example a server with few but very large definitions).
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #43

Theme: #55

Start with README.md:6 and crates/ganja-tool/src/deferral.rs:86-90 to understand the current deferred-loading rationale and count-based threshold. This issue is explicitly parked; work should wait for a use report showing tool count is the wrong proxy, after which the desired byte-aware behavior and completion criteria can be defined.