wiki-fold

You can use extractive summarization to roll up wiki log entries into a single meta-fold page. This process preserves traceability by generating deterministic fold IDs with explicit citations referencing each contributing source entry from the original markdown logs.

Yes, you can run the wiki fold process in dry-run mode to preview the extractive summary on stdout. This default mode prevents file writes, allowing you to verify the generated meta-page content before executing a commit to the repository.

Yes, the summarization process integrates with version-control workflows by triggering repository auto-commit hooks via a PostToolUse hook. It enforces concurrency control through a wiki-lock script to prevent write races when updating your knowledge vault.

The extractive summarization fold supports bounded reads of 0 to 15 child pages. It typically reads the last 2^k entries from wiki/log.md to generate the deterministic meta-page, ensuring a strict limit on processed log entries.

You prevent duplicates during a wiki log fold by enforcing concurrency control via a wiki-lock script. This lock mechanism blocks write races, while deterministic fold IDs and idempotent writes ensure no repeated meta-pages are generated.