Greptile Summary

This PR improves the tool/skill/file name display in the usage panel's context breakdown by adding CSS truncation with text-overflow: ellipsis and native title tooltips, preventing long names from overflowing their containers.

• title="${name}" attributes are added to all three breakdown item spans (skills, tools, files), correctly exposing the full name as a hover tooltip when text is visually truncated — a good UX improvement.
• A new .mono CSS rule is added to usageStyles-part3.ts. The rule itself is correct in intent, but it is unscoped: the rest of the codebase already scopes .mono overrides to a parent class (e.g., .context-list-item .mono in usageStyles-part2.ts). Because the whole app renders in a light DOM (no Shadow DOM encapsulation), this style is injected globally when the usage tab is active and could unintentionally affect other .mono elements — most critically those in the persistent top-bar in app-render.ts. Scoping to .context-breakdown-item .mono would be the safe, consistent fix.

Confidence Score: 4/5

• This PR is nearly safe to merge; the only concern is the unscoped .mono CSS rule which is a style best-practice issue rather than a functional bug.
• The title tooltip additions are unambiguously correct. The CSS change achieves its visual goal but is unscoped, inconsistent with the existing pattern, and technically injects global styles when the usage tab is active. In practice the current impact appears minimal because other tabs' content is not in the DOM simultaneously and topbar .mono elements are protected by a higher-specificity rule, but it is still fragile and should be scoped.
• ui/src/ui/views/usage-styles/usageStyles-part3.ts — the .mono rule should be scoped to .context-breakdown-item .mono.

_{Last reviewed commit: be591b7}

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

Codex review: needs changes before merge.

Workflow note: Future ClawSweeper reviews update this same comment in place.

Summary
The branch adds native title tooltips to usage context breakdown skill/tool/file names and adds scoped ellipsis CSS in the old split usage stylesheet.

Reproducibility: yes. at source/proof level: current main lacks the three title attributes and scoped ellipsis selector, while the inspected screenshots show the intended visual behavior. I did not establish a live browser reproduction in this read-only pass.

PR rating
Overall: 🦐 gold shrimp
Proof: 🦞 diamond lobster ✨ media proof bonus
Patch quality: 🦐 gold shrimp
Summary: The visual proof is strong, but the patch remains blocked by a stale stylesheet path and live merge conflict.

Rank-up moves:

• Move the scoped truncation selector into ui/src/styles/usage.css.
• Keep the three title attributes and run focused usage render/style checks.

PR egg
✨ Hatched: 🥚 common Gilded Merge Sprite

       /\  .---.  /\         
      /  \/     \/  \        
     /   ( -   - )   \       
    |       ._.       |      
    |   /|  ===  |\   |      
     \  \|______/|/  /       
      '._  `--'  _.'         
         '-.__.-'            
       _/|_|  |_|\_          
      /__|      |__\         
       .-----------.         
      '-------------'        

Rarity: 🥚 common.
Trait: hums during re-review.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Gilded Merge Sprite in ClawSweeper.

Real behavior proof
Sufficient (screenshot): The PR body's before/after screenshots were downloaded and inspected; they directly show the long usage-panel name overflowing before and truncating with tooltip after.

Mantis proof suggestion
A short browser visual proof would directly verify the visible usage-panel truncation and native tooltip behavior after the stale CSS path is refreshed. A maintainer can ask Mantis to capture proof by posting a new PR comment that starts with the OpenClaw Mantis account mention, followed by:

visual task: verify a usage context breakdown with a long tool name ellipsizes and the native title tooltip exposes the full name.

Risk before merge
Why this matters: - The live PR is currently conflicting and still edits a stylesheet file that current main has deleted, so the CSS fix will not land from the proposed path.

• I did not run a live browser session or tests in this read-only pass; the behavior proof is the PR screenshots plus source inspection.

Maintainer options:

1. Decide the mitigation before merge
   Refresh the branch so the current renderer keeps the three title attributes and ui/src/styles/usage.css owns the scoped .context-breakdown-item .mono ellipsis rule, then let automerge proceed after focused usage checks and mergeability are clean.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge
Automerge is armed and the only blocker is a narrow mechanical refresh from the deleted split stylesheet to the current consolidated usage stylesheet.

Security
Cleared: The diff only changes Lit-rendered attributes and CSS, with no dependency, workflow, secret, permission, or code-execution surface.

Review findings

• [P2] Port the ellipsis rule to usage.css — ui/src/ui/views/usage-styles/usageStyles-part3.ts:327-333

@clawsweeper automerge

🦞🔧
ClawSweeper picked up the repair feedback.

Source: clawsweeper[bot]
Feedback: structured ClawSweeper marker: fix-required (finding=review-feedback sha=d6d6c9dc3c6f3007ffccc2399a3dfc37f114f3c9)
Action: repair worker queued. Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651
Model: gpt-5.5

I will update this PR branch, or open a safe credited replacement, if the repair worker finds a narrow fix.

Automerge progress:

• 2026-05-19 16:59:59 UTC review queued d6d6c9dc3c6f (queued)

• 2026-05-19 17:02:11 UTC repair queued d6d6c9dc3c6f (autonomous) Run: https://github.com/openclaw/clawsweeper/actions/runs/26112528297

• 2026-05-19 19:39:20 UTC review requested repair d6d6c9dc3c6f (structured ClawSweeper marker: fix-required (finding=review-feedback sha=d6d6c9...)

• 2026-05-19 20:36:45 UTC repair started (running) in 3s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 automerge-openclaw-openclaw-42197

• 2026-05-19 20:37:01 UTC validation plan (passed) in 18s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 pnpm check:changed; pnpm lint; pnpm check:test-types

• 2026-05-19 20:37:13 UTC Codex write preflight (passed) in 30s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 danger-full-access

• 2026-05-19 20:42:59 UTC Codex edit 1 c53fa4f4f69e (complete) in 6m 16s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 exit 0

• 2026-05-19 20:50:42 UTC validation and review 1 5101461865c0 (base moved) in 13m 59s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 rebased

• 2026-05-19 20:51:18 UTC repair finished 5101461865c0 (opened) in 14m 35s Run: https://github.com/openclaw/clawsweeper/actions/runs/26123581651 open_fix_pr

ClawSweeper 🐠 reef update

Thanks for the work here. ClawSweeper could not write to the source branch, so it opened a replacement PR rather than letting the fix drift. attribution still points back here.

Why replacement: ClawSweeper could not update the source PR branch directly; GitHub did not grant sufficient push rights to the bot for that branch.
Replacement PR: #84310
Why close: this run explicitly closes the superseded source PR after the credited replacement PR is open, so review continues in one place.
This closeout is intentional for this run: the replacement PR is now the active review lane.
Attribution is preserved in the replacement PR body and release-note trail.
Co-author credit kept:

• @Rain120: Co-authored-by: Rain120 20939839+Rain120@users.noreply.github.com

fish notes: model gpt-5.5, reasoning high; reviewed against 5101461.