Repository navigation
gap-map 0.2.0
·
101 commits
to main
since this release
- A design question has to show what it rests on. An obligation with a
questionnow needsbasis: the file lines it rests on, and a literal-text search with its scope and hit count for every claim that something is absent. A map without it is refused. (#219)
claude plugin marketplace update lim claude plugin update gap-map@lim
- A question that went stale says so. The script reruns each search and checks each line on every run. When a basis no longer holds, the obligation stays open and
gaps.mdmarks the question(stale, recheck before deciding)with the reason. On the real Bend repository, the first map's wrong question about argument order fails at once:searching guide/GUIDE.md for "left to right" now finds 1, the question says 0. (#219)
Maps written for 0.1.x need a basis on each obligation that has a question.