Repository navigation
kibi-cursor@2.9.7
Patch Changes
-
a84493d: Symbol coordinates no longer cause merge conflicts.
.kb/symbol-coordinates.yamlis now a local cache that everykibi syncderives from source; it is gitignored and never committed. Before, each coordinate record carried a hash of its whole source file, so any two branches that edited the same source file conflicted on it, even when they touched different declarations.What changes for you:
kibi initadds.kb/symbol-coordinates.yamlto.gitignore. Everykibi syncrefreshes the cache incrementally, re-extracting only symbols whose source or identity changed, and never rewrites.kb/symbols.yaml.- The staged check judges symbol evidence by the declaration titles in the staged
.kb/symbols.yaml. When those titles cover every declaration of a staged source file, that is impact evidence for it, so a body-only edit to a modeled symbol now commits with only thesymbol_semantic_review_neededwarning instead of needing a coordinate refresh staged with it. A renamed or added declaration that.kb/symbols.yamldoes not list still fails, and the message names the uncovered and stale titles. kibi check-generated --stagedchecks only the.kb/symbols.yamllayout and rejects a commit that stages the coordinate cache.- Schema 13:
kibi migrateadds the gitignore entry and removes a committed.kb/symbol-coordinates.yamlfrom the Git index while keeping the local file. Commit the result once; until thencheck-generatedblocks commits in repositories that still track the file. - The reviewed refresh gate for Python decorator coordinates is retired, since there is no committed coordinate refresh left to review.