capturelisted

# Adaptive-Depth Session Recap Session-end and checkpoint signal extraction. When the developer wraps up work or explicitly asks to checkpoint the current progress, read the conversation context and produce raw entries rich enough for weekly outlines, monthly reviews, decision roadmaps, and session-start recall. The goal is not a chronological diary. Capture the durable engineering signal: why the work happened, what was decided, what was tried, what changed, and what future sessions need to remember. ## Zero-Config Mode This skill works with or without a configured knowledge vault: - **With vault**: entries are written to `{vault}/raw/weeks/{ISO-week}/{project-slug}.json`; durable artifact indexes are written to `{vault}/raw/artifacts/{project-slug}.json` when applicable. Output is quiet by default: after a successful write, return only a short confirmation unless the user explicitly asks for verbose output. - **Without vault**: entries are rendered as structured Markdown directly in the conversation. No files written, no directories created. A one-line setup hint follows the output. Zero-config mode is best-effort. Fill every field that can be inferred from the conversation, but do not interrogate the user only to satisfy a schema field. Depth enforcement is warning-based in the helper, not a hard block. ## Capture Modes Default mode is a session-end recap. It is triggered by `/lode:capture`, "收工", "done", and similar wrap-up signals. Checkpoint mode is