memory-wiki: Stale Pages report flags intentionally durable references (concepts, syntheses) as aging

Plugin: memory-wiki
Affected versions: 2026.6.1 (and likely all versions where the report was introduced)

Description

The Stale Pages report flags any page with page.kind !== "report" whose updatedAt is older than 30 days as "aging" and 90+ days as "stale". In bridge-mode vaults, concept and synthesis pages are intentionally durable reference material and should not be subject to the same staleness threshold as event-driven sources.

In our 853-source / 5-concept / 7-synthesis vault, every concept and synthesis page is currently flagged as "aging" — so the report's signal-to-noise ratio is 0 for the most valuable references.

page.kind is directory-derived (sources/ → source, concepts/ → concept, etc.) and the lint check at cli-BC1g2VJh.js:3127 enforces that pageType frontmatter matches the expected type, so pages cannot be relabeled as reports without breaking the structure validator.

The relevant filter at cli-BC1g2VJh.js:653:

const matches = pages.filter((page) => page.kind !== "report").flatMap(...)

The WIKI_STALE_DAYS = 90 constant and the implicit 30-day aging threshold are at lines 39 and 71 of the same file.

Reproduction

1. Initialize a bridge-mode vault with at least one concept and one synthesis page.
2. Wait 31 days.
3. Run openclaw wiki compile.
4. Read reports/stale-pages.md — observe all concept and synthesis pages listed as "aging" with the message last touched <14-day-old timestamp>.

Proposed fix

Add a user-configurable exclude list to the staleness check. Suggested shape:

{
  "plugins": {
    "memory-wiki": {
      "reports": {
        "stalePages": {
          "excludeKinds": ["concept", "synthesis"],
          "excludePathPatterns": ["^/concepts/", "^/syntheses/"],
          "durableFrontmatterKey": "durable",
          "staleAfterDays": 90,
          "agingAfterDays": 30
        }
      }
    }
  }
}

Defaults: empty arrays (current behavior), durableFrontmatterKey defaults to "durable" and is treated as opt-in when the value is true, staleAfterDays defaults to 90, agingAfterDays defaults to 30.

Additional request

The hardcoded WIKI_STALE_DAYS = 90 and the implicit 30-day aging threshold should be exposed as configurable thresholds (staleAfterDays, agingAfterDays) so operators can tune to their own vault activity cadence.

Workarounds attempted (none viable)

Impact

High noise in a high-value report. Operationally, the report is currently unusable for spotting genuinely stale source pages because durable references drown out real signal.