Conversation
Introduce setup_soft_epoch and setup_hard_epoch in the soul frontmatter. The leiter binary has compiled-in expected values for both. On session start, `leiter context` compares them: - Hard mismatch: blocks the session (soul not injected), tells the user what happened and how to fix it. - Soft mismatch: nudges with an explanation but still injects the soul. Both default to 1 when absent from the YAML, so existing souls are seamlessly compatible. This lets future leiter upgrades that require user action (e.g. re-running agent-setup) detect the condition and alert the user, without needing to bump soul_version or change the soul template. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Introduce setup_soft_epoch and setup_hard_epoch in the soul
frontmatter. The leiter binary has compiled-in expected values for
both. On session start,
leiter contextcompares them:user what happened and how to fix it.
Both default to 1 when absent from the YAML, so existing souls are
seamlessly compatible.
This lets future leiter upgrades that require user action (e.g.
re-running agent-setup) detect the condition and alert the user,
without needing to bump soul_version or change the soul template.