What problem does it solve? Keeping a large campaign wiki healthy requires constant upkeep — ingesting new source material, fixing frontmatter and formatting drift, linking orphan pages, and regenerating the index. Doing this manually every day is repetitive and easy to skip, so the vault slowly decays. ## Core Features & Use Cases - Autonomous triage-driven maintenance: Runs wiki-init validation, counts pending ingest sources, checks lint status, and verifies Obsidian availability before deciding how to spend its budget. - Priority-based execution: Processes work in a fixed INGEST → LINT → CROSS-LINK chain, capping ingest at 6 sources per run and deferring all judgment calls to a review queue instead of acting on them. - Idempotent and crash-safe: Safe to re-run after interruption, commits each phase separately, logs errors, and continues past single-phase failures. - Use Case: Schedule it via cron each morning so the campaign wiki ingests new session material, auto-fixes lint issues, links orphans, regenerates the index, and appends a summary to the daily log — all without DM involvement. ## Quick Start Ask the agent to run the daily update to triage the wiki, ingest pending sources, fix lint issues, and regenerate the index.
