1natsu-entire-context

To view session history and checkpoints, reference the repository's entire CLI context to locate and explain specific sessions. This provides lineage, audit trails, and retrospectives by applying status, explain, and rewind commands without directly reading internal metadata.

Yes, you can retrieve an audit trail for a refactor by navigating checkpoints to understand milestones and rationale. This summarizes past sessions and commits to provide clear context for audits and reviews, explaining the decisions behind specific changes.

The best way to explain commit context is to apply the entire CLI explain and status commands. This retrieves and summarizes past sessions and checkpoints, providing contextual explanations for specific commits while discouraging heavy generation when unnecessary.

Session checkpoints work by capturing milestones and the rationale behind changes during development. You can navigate these checkpoints to reconstruct lineage and audit trails, enabling accurate retrospectives of development work and specific sessions.

Yes, direct reads of internal metadata are discouraged. Instead, you should apply entire status, explain, and rewind commands to access complete session context, ensuring correct access methods and constraints while avoiding unnecessary heavy generation.