Statusline ADR count is hardcoded to 0/0

[easel]

Bug Description

The statusline displays ADRs ●0/0 but this value is hardcoded and never actually counts ADRs.

Location

dist/src/commands/hooks.js line ~3035:

`${c.cyan}ADRs${c.reset} ${c.dim}●0/0${c.reset}  ${c.dim}│${c.reset}  ` +

Expected Behavior

The ADR count should be dynamic. There's already a getADRStatus() function in statusline-generator.js that:

1. Checks for adr-compliance.json in .claude-flow/metrics/
2. Falls back to scanning docs/adrs/, docs/adr/, etc. for ADR files
3. Counts files matching ADR-*.md pattern
4. Checks for Status: Accepted or Status: Implemented in content

But this function is never called by the hooks.js statusline command.

Suggested Fix

Option A: Wire up getADRStatus() in hooks.js

Option B (Better): Query the memory system instead of scanning files

// ADRs indexed in memory are more reliable than file scanning
const adrCount = await memorySearch({ namespace: 'architecture', pattern: 'adr-*' });

This would:

• Use the existing memory indexing that users set up
• Support custom ADR locations (not just hardcoded paths)
• Be consistent with how other project docs are accessed
• Handle markdown formatting variations (bold **Status**: vs plain Status:)

Additional Context

• The docs/adrs path requirement is also too rigid - projects have ADRs in various locations
• The status detection fails on **Status**: Accepted (markdown bold) - only matches Status: Accepted
• The JSON output (--json) doesn't include ADR data at all

Environment

• claude-flow v3.0.0-alpha.185
• Discovered while setting up doc indexing for a Rust project with ADRs in docs/helix/02-design/adrs/

[easel]

Additional Findings: Other Misleading Metrics

After further investigation, the statusline has several other metrics that are misleading or not useful:

DDD Progress (e.g., "DDD ●80%")

This has nothing to do with Domain-Driven Design domains. It's purely based on memory database pattern count:

if (learning.patterns >= 500) domainsCompleted = 5;      // 100%
else if (learning.patterns >= 200) domainsCompleted = 4; // 80%
else if (learning.patterns >= 100) domainsCompleted = 3; // 60%
else if (learning.patterns >= 50) domainsCompleted = 2;  // 40%
else if (learning.patterns >= 10) domainsCompleted = 1;  // 20%

Running memory init --force dropped my "DDD progress" from 100% to 80% because it reset the pattern count. This metric is memory database size dressed up as architecture progress.

CVE Count (e.g., "CVE 0/3")

Just counts files in .claude/security-scans/ or .swarm/security/ directories:

const scans = fs.readdirSync(scanResultsPath).filter((f) => f.endsWith('.json'));
cvesFixed = Math.min(totalCves, scans.length);

The "3 total CVEs" is hardcoded. It doesn't reflect actual security analysis.

Recommendation

The statusline should either:

1. Display actually useful project metrics:

   • Real ADR count from memory (indexed docs)
   • Test coverage %
   • Build status
   • Git status (ahead/behind, uncommitted changes)

2. Or be transparent about what it's showing:

   • "Memory entries: 290" instead of "DDD ●80%"
   • "Security scans: 0" instead of "CVE 0/3"

3. Remove misleading metrics entirely rather than display fake progress

The current implementation gives users a false sense of project health/progress that has no connection to reality.