Memory Tree shows degraded status despite full extraction coverage

[Al629176]

Summary

The Memory Tree page shows a degraded / wiki structure incomplete warning even when extraction coverage reports 100% of chunks have structure.

Problem

Expected: Memory Tree health should accurately reflect the current extraction and sync state, and should not show a degraded status when the underlying coverage indicates the structure is complete.

Actual: The page displays a degraded status and warning that the memory extraction model is timing out, while the same screen reports 100% extraction coverage. Per-integration health also shows sources as stale, which makes it unclear whether the issue is model timeout, stale sync, or incorrect UI status calculation.

Steps to reproduce:

1. Open the Intelligence / Memory Tree page.
2. Observe the Memory Tree health banner and status cards.
3. Compare the degraded warning with the extraction coverage value.
4. Notice that the page simultaneously reports degraded status and full extraction coverage.

Version / platform: desktop app, exact version unknown.

Impact: Users cannot tell whether memory is actually unhealthy, stale, or working correctly, which reduces trust in the memory system and makes troubleshooting difficult.

Solution (optional)

Audit the Memory Tree health calculation and UI copy. Separate model-timeout, stale-source, and extraction-coverage states so the page shows a precise reason for degradation. If coverage is complete, avoid showing “wiki structure incomplete” unless another failing condition is clearly explained.

Acceptance criteria

• Accurate status — Memory Tree status matches the underlying extraction, sync, and model health data.
• No contradictory copy — The page does not show “wiki structure incomplete” when extraction coverage is complete unless a separate failing condition is explicitly named.
• Clear stale state — Stale per-integration sources are shown separately from extraction/model failures.
• User guidance — If model timeout is the root cause, the UI explains which setting to change and why.
• Regression safety — Unit or UI coverage verifies degraded, stale, healthy, and timeout states render correctly.
• Diff coverage ≥ 80% — the fix PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by .github/workflows/coverage.yml).

Related

• Screenshot shared in internal report on June 4, 2026.