wiki-status

What it does

You are computing the current state of the wiki: what's been ingested, what's new since last ingest, and what the delta looks like. This helps the user decide whether to append (ingest the delta) or rebuild (archive and reprocess everything).

How it works

1. Read configuration and the vault manifest to establish the ingest state and sources.
2. Scan sources from Documents (OBSIDIAN_SOURCES_DIR), Claude History, Codex History, and any other known sources; record path, size, modification time, and related metadata.
3. Compute the delta by comparing current sources against the manifest; classify as New, Modified, Touched, Unchanged, or Deleted; handle older manifest entries by falling back to mtime comparison when content_hash is missing.
4. For Claude history, compute New projects, New conversations, and Updated memory files. For Codex history, compute New rollout files, Updated session_index.jsonl entries, andArchived rollout delta when requested.
5. Produce a status report including a visibility tally and a delta section showing New sources, Modified sources, and summary metrics such as Total wiki pages, Page visibility, Total sources ingested, Projects tracked, and Last ingest timestamp.
6. Compute a token footprint estimate via per-tier page sizes and a rough 4 chars per token heuristic; produce a foreground methodology note and a threshold-based warning if needed.
7. Provide a ranked What to Do Next section, gathering signals from staged writes, _raw, stale core pages, orphan pages, synthesis opportunities, source delta, and lint status; render up to 6 items in priority order with concrete commands.
8. If Insights Mode is triggered, run graph analysis to surface hub pages, bridges, and clusters; present anchor pages, bridge pages, and tag-cluster cohesion insights.

When to use it

• When the user asks about the wiki status, how much is ingested, what’s left to process, the delta, what changed since last ingest, or for a wiki health overview. Also used before deciding whether to append or rebuild. Insights mode can be triggered by terms like wiki insights, what’s central, show me the hubs, etc.

What to touch

• Access to: Obsidian vault manifest, OBSIDIAN_VAULT_PATH, OBSIDIAN_SOURCES_DIR, CLAUDE_HISTORY_PATH, CODEX_HISTORY_PATH. It reads these paths and reads files in those locations to compute deltas and inventories.

Caveats

• Relies on the manifest structure and path conventions; mismatched paths can cause duplicate or missed ingest entries. If a manifest entry lacks content_hash, delta uses mtime comparison. Insights mode requires obsidian-wiki graph analysis data; if not installed, it falls back to wikilink parsing.