v3.38.20 — statusline: stop pinning intelligence to a hardcoded 0%

Fix

• statusline: stop pinning intelligence to a hardcoded 0% (#3092, closes #3091)

  intelligencePct had 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 touched system. So any CLI failure (a source-only plugin-marketplace checkout with no install step, or an npx fetch dying in a workspace root with no version field — both reachable under ordinary conditions) silently pinned the brain segment to a literal 0% 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 of 0%, 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.cjs and v3/@claude-flow/cli/.claude/helpers/statusline.cjs).

🤖 Generated with claude-flow