Reset

To reset wiki state and clear pipeline artifacts, run a scoped reset targeting wiki markdown, raw extracted entries, logs, or checkpoint batch state. This restores the environment to a clean scaffold by removing generated artifacts while preserving placeholders like .gitkeep and core configuration files.

Yes, you can preview deletions before running destructive state cleanup because the tool generates a dry-run JSON deletion plan. This plan outlines exactly which wiki markdown artifacts, raw entries, and checkpoint state will be removed, requiring your explicit interactive confirmation before executing irreversible raw directory deletions.

The best way to clear only checkpoint and log state without deleting wiki markdown is using targeted scoped arguments. By specifying the log and checkpoints scopes instead of all, you prevent accidental overreach and ensure the reset operation only clears the designated pipeline artifacts while leaving other generated content intact.

Yes, the wiki reset process preserves core configuration files and .gitkeep placeholders. It uses deterministic tool-based execution to safely wipe generated state and raw pipeline artifacts, ensuring the known clean scaffold retains essential structural files required for your development recovery workflows.

You need a full scoped reset for development recovery when recovering from botched setups or inconsistent intermediate outputs across the entire pipeline. Targeted artifact clearing is sufficient when you only need to remove specific wiki, raw, log, or checkpoint state without affecting other generated components.

The raw pipeline reset requires interactive confirmation during state management because deleting the raw directory is an irreversible destructive operation. This safety guardrail prevents accidental data loss, ensuring you review the dry-run deletion plan and explicitly approve the removal of raw extracted entries before execution.