v3.38.20 — statusline: stop pinning intelligence to a hardcoded 0%
- Cache pattern-count parse on store mtime and size to avoid re-parsing large stores on every prompt render
- Render unknown intelligence measurement as — instead of 0% to distinguish genuine absence from actual zero
- Stop pinning intelligence percentage to hardcoded 0% in statusline by deriving it from .claude-flow/neural/patterns.json when CLI does not report a positive value
From ruflo
Fix
-
statusline: stop pinning intelligence to a hardcoded 0% (#3092, closes #3091)
intelligencePcthad exactly one assignment in the whole statusline helper, inside the local-CLI fallback path. Every other read used it as-is, and the local-overlay repair pass — which already covers ADRs, AgentDB, tests, hooks, integration, and security — never touchedsystem. So any CLI failure (a source-only plugin-marketplace checkout with no install step, or annpxfetch dying in a workspace root with noversionfield — both reachable under ordinary conditions) silently pinned the brain segment to a literal0%beside sibling segments that were still rendering live data, with nothing to tell them apart.getLocalIntelligence()now joins the local-overlay set: it derives the percentage from.claude-flow/neural/patterns.json(project, then home) whenever the CLI didn't already report a positive value, with the pattern-count parse cached on the store's mtime+size so a large store (14.5 MB / 1,277 patterns measured) doesn't get re-parsed on every prompt render. Unknown now renders as—instead of0%, so a genuinely-absent measurement is no longer indistinguishable from a real zero.Applied identically to both committed copies of the helper (
.claude/helpers/statusline.cjsandv3/@claude-flow/cli/.claude/helpers/statusline.cjs).
🤖 Generated with claude-flow