Repository navigation
chore: release 0.6.0 - #10
Merged
Merged
Conversation
A minor version, because it adds a frontmatter field: - `revisit: YYYY-MM-DD` (#9) dates a decision taken "for now" or an accepted risk. From that date recall flags the entry, `/lore:lint --report` lists it for `/lore:sweep`, and `/lore:stats` counts it. Re-verifying the claim on or after the date clears it. - Claims that go stale by an event rather than by age (#9): the skill asks for an absence claim's `files:` to point where the change would land, and for an entry a new learning contradicts to be superseded -- a rule the capture-time overlap check now prints as well. `_common.py` and `verify_refs.py` changed again, so the linter will ask projects to re-run /lore:init to refresh their `.lore/` copies; that is also when CI `--strict` starts checking `revisit:` values. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DMXx6BJswH6xiwdqrwQnEf
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.
Summary
This bumps the three version fields (marketplace, marketplace plugin entry,
plugin.json) from 0.5.2 to 0.6.0. It's a minor release because #9 adds a frontmatter field.revisit: YYYY-MM-DD: the date a decision taken "for now" or an accepted risk must be re-decided. From that date:! revisit due since <date>;/lore:lint --reportlists it, so/lore:sweeppicks it up;/lore:statscounts it.Re-verifying the claim on or after the date clears the flag.
Claims that go stale through an event rather than age: the skill asks for an absence claim ("there is no backup") to anchor
files:where the change would land. It also asks for an entry that a new learning contradicts to be markedsupersededinstead of staying live; the capture-time overlap check now prints this rule too.Upgrade notes
_common.pyandverify_refs.pychanged, so the linter will ask projects to re-run/lore:initto refresh their.lore/copies.--strictstarts rejecting unreadablerevisit:values after that refresh.revisit:is optional; stores that don't use it see no change.Test plan
python -m unittest discover -s tests: 211 passed, 1 skipped.test_manifestschecks that the three versions agree.claude plugin validate .: passed.v0.6.0onmain.🤖 Generated with Claude Code
https://claude.ai/code/session_01DMXx6BJswH6xiwdqrwQnEf
Generated by Claude Code