Summary

The memory-wiki Stale Pages report flags intentionally durable reference pages (concepts, syntheses) as aging or stale, drowning out real staleness signal in bridge-mode vaults. This PR introduces an opt-in durable: true frontmatter marker so authors can flag pages whose value comes from durability rather than recency.

• Problem: In an 853-source / 5-concept / 7-synthesis vault, every durable reference page shows up in reports/stale-pages.md because the report only excluded report kind, not the durable kinds. Signal-to-noise drops to zero.
• Solution: Honor a strict boolean durable frontmatter field at the stale-pages filter step. Pages with durable: true are excluded regardless of updatedAt.
• What changed:
  • extensions/memory-wiki/src/markdown.ts — WikiPageSummary.durable field + parser using asBoolean.
  • extensions/memory-wiki/src/compile.ts — One-line filter addition page.durable !== true.
  • extensions/memory-wiki/src/markdown.test.ts — Strict parser coverage (true/false/string/missing/no-frontmatter).
  • extensions/memory-wiki/src/compile.test.ts — End-to-end compile coverage (durable concept + durable synthesis + control).
  • docs/plugins/memory-wiki.md — New Opting pages out of the Stale Pages report section.
• What did NOT change: No config surface, no threshold constants, no other dashboard report, no lint path, no agent-digest path. The marker is strict (real boolean only — string "true" is intentionally ignored to avoid accidental activation) and entirely opt-in.

Linked Issue

Fixes #93485

Changes

• extensions/memory-wiki/src/markdown.ts — Adds durable?: boolean to WikiPageSummary and parses it via asBoolean(parsed.frontmatter.durable) in toWikiPageSummary; strict boolean only, so sloppy durable: "true" YAML is silently ignored. Honors the user's explicit request in memory-wiki: Stale Pages report flags intentionally durable references (concepts, syntheses) as aging #93485 to make durable a recognized frontmatter field.
• extensions/memory-wiki/src/compile.ts — Adds page.durable !== true to the Stale Pages dashboard filter; a single-line addition that scopes the opt-in to the one report the issue describes.
• extensions/memory-wiki/src/markdown.test.ts — New parses the durable opt-in flag from frontmatter strictly test covering true, false, string literal, missing field, and no-frontmatter cases.
• extensions/memory-wiki/src/compile.test.ts — New excludes durable pages from the Stale Pages report test that writes three vault pages (durable concept + durable synthesis + non-durable concept), runs compileMemoryWikiVault, and asserts the report excludes durable pages but includes the control.
• docs/plugins/memory-wiki.md — New subsection Opting pages out of the Stale Pages report under Dashboards and health reports so operators discover the marker.

Real behavior proof

• Behavior addressed: Pages with durable: true frontmatter are excluded from reports/stale-pages.md regardless of updatedAt. Pages without the marker behave exactly as before.

• Real environment tested: Linux 4.19.112 (x86_64), Node v24.13.1, branch fix/wiki-stale-pages-durable-frontmatter-93485 rebased on origin/main (commit 6d640a6556).

• Exact steps or command run after this patch:

  node --import tsx --input-type=module <<'NODE'
  import { toWikiPageSummary, renderWikiMarkdown } from "./extensions/memory-wiki/src/markdown.ts";
  // ... (4 fixtures: true / false / "true" string / missing)
  NODE
  node scripts/run-vitest.mjs run extensions/memory-wiki/src/markdown.test.ts --maxWorkers=1
  node scripts/run-vitest.mjs run extensions/memory-wiki/src/compile.test.ts --maxWorkers=1
  

• Evidence after fix:

  $ node --import tsx --input-type=module <<'NODE'
  ... (production parse proof, 4 cases)
  NODE
  durable: true (boolean) -> true
  durable: false (boolean) -> false
  durable: 'true' (string literal) -> undefined
  durable: missing field -> undefined
  
  $ node scripts/run-vitest.mjs run extensions/memory-wiki/src/markdown.test.ts --maxWorkers=1
   Test Files  1 passed (1)
        Tests  8 passed (8)
  
  $ node scripts/run-vitest.mjs run extensions/memory-wiki/src/compile.test.ts --maxWorkers=1
   Test Files  1 passed (1)
        Tests  14 passed (14)

  The new compile test writes three vault pages: concepts/alpha-concept.md (durable: true), syntheses/alpha-synthesis.md (durable: true), and concepts/beta-concept.md (no marker). All three carry updatedAt: 2024-01-01 (>2 years old, well past the 90-day stale threshold). After compileMemoryWikiVault, the test asserts that Alpha Concept and Alpha Synthesis are absent from reports/stale-pages.md while Beta Concept is present.

• Observed result after fix:

  1. Pages with durable: true frontmatter are skipped at the stale-pages filter step regardless of updatedAt.
  2. Pages without the marker behave exactly as before the patch.
  3. String literals like durable: "true" are deliberately not honored — only real booleans activate the marker.
  4. No other dashboard report (open-questions, contradictions, claim-health, person-agent-directory, relationship-graph, provenance-coverage, privacy-review) is affected.
  5. The lint path's stale-page warning code and the agent-digest.json cache shape are unchanged.

• What was not tested: Live openclaw wiki compile against a real bridge-mode vault (the existing test harness covers the same path through compileMemoryWikiVault); multi-vault compile; durable: true interaction with non-concept/synthesis kinds beyond entity.

AI-Assisted

This PR was prepared with assistance from Claude Code.
Co-Authored-By: Claude Opus 4.8 [email protected]

Fixes #93485