kibi-cursor 2.6.3 → 2.6.4

package/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "kibi-cursor",
   "displayName": "Kibi",
-  "version": "2.6.3",
+  "version": "2.6.4",
   "description": "Optional Cursor adapter for Kibi. Requires project-local kibi-cli, kibi-mcp, and kibi-core (SWI-Prolog is bundled on Linux and macOS) before the bundled MCP server can start.",
   "license": "AGPL-3.0-or-later",
   "author": {

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # kibi-cursor
 
+## 2.6.4
+
+### Patch Changes
+
+- 89d8b8e: `kb_model` mode `predicates` no longer offers a predicate plan that `kb_check` would then reject. The requirement's subject now binds the argument a schema names `subject` wherever it sits, and for a schema without one (such as `permission_rule`) it is recorded as the planned predicate fact's `subject_key`; a predicate that is not about a subject the requirement constrains stays `provide_argument_bindings` with a hint instead of `replace_grounding` or `apply_requires_predicate`. A value taken from the claim for an actor, resource or other participant that is a long clause (more than three words) is no longer accepted as a binding.
+
+  Technical summary: `buildSuggestion` binds `subjectHint` or the single constrained subject into `argument_names.indexOf("subject")` and adds `subject_key` and `subject_pairing` (`paired`, `unpaired`, `not_required`) to each candidate; an unpaired candidate gets `subject` or `subject_key` in `unbound_arguments`, a `bindingHints` entry (position -1 for `subject_key`) and a warning naming the schema. `buildPredicateApplyPlan` writes `subject_key` on the planned fact when it is known, so `replacementPlan` step 1 carries it. `classifyBinding` treats an extracted value of an `entity`, `actor`, `actor_scope`, `resource`, `owner`, `role` or `component` argument with more than three snake-case words as a placeholder (`clauseBindingReason`), and the hint says why. The constrained subjects are now read even when `subjectHint` is passed. The kibi-usage skill (2.9.0) describes `subject_key` and short participant bindings.
+
 ## 2.6.3
 
 ### Patch Changes

package/agent-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "kibi",
-  "version": "2.6.3",
+  "version": "2.6.4",
   "description": "Repo-local, per-branch, queryable knowledge base. Portable Agent Plugin packaging Kibi's Agent Skills and MCP server.",
   "author": { "name": "Kibi" },
   "homepage": "https://looted.github.io/kibi/",

package/agent-plugin/skills/kibi-usage/SKILL.md

@@ -2,7 +2,7 @@
 id: kibi-usage
 name: Kibi Usage
 description: Use Kibi's source-first, exact-Git, migration-aware, proof-aware operations safely across MCP or the trusted local CLI, including partial completion repair.
-version: 2.8.0
+version: 2.9.0
 kibiCompatibility: ">=1.0.0"
 tags:
   - kibi
@@ -260,7 +260,11 @@ constants) or `examples`, and why the current value was refused. With a
 `requirementId` whose requirement `constrains` one subject fact, the `subject`
 argument is already bound to that fact's `subject_key` (provenance
 `requirement`); keep it, so the predicate and the subject fact name one
-subject. Bind them
+subject. A schema without a `subject` argument (`permission_rule`) records
+that key as the planned fact's `subject_key` instead; when the requirement
+constrains several subjects, an unbound `subject_key` asks you to pass
+`subjectHint` with one of them. A participant (`actor`, `resource`, entity)
+is a short noun, never a clause of the claim. Bind them
 from the claim's own words and call again with the same `text` and
 `requirementId`, plus `schemaId` and `argumentBindings` keyed by
 `argument_names` (reuse `argument_constants` values when the schema has them).

package/dist/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "kibi-cursor",
   "displayName": "Kibi",
-  "version": "2.6.3",
+  "version": "2.6.4",
   "description": "Optional Cursor adapter for Kibi. Requires project-local kibi-cli, kibi-mcp, and kibi-core (SWI-Prolog is bundled on Linux and macOS) before the bundled MCP server can start.",
   "license": "AGPL-3.0-or-later",
   "author": {

package/dist/skills/.canon-hash.json

@@ -13,7 +13,7 @@
   "kibi-traceability/resources/operation-access.md": "39f7972ab7f4ae7479e78f7072bb50e8e6c4cdf4f857425f69d2522d37db437c",
   "kibi-traceability/resources/source-authoring.md": "408c6ee2bef1b84e0194c0538ef929c26a0a617e631b2234247388140dbbdd08",
   "kibi-traceability/resources/traceability.md": "38c290a0bc71bd1692e115f22694743946e2f69630e134acfd43cee5f613fb88",
-  "kibi-usage/SKILL.md": "91688060880c219a867e995571d869fc7f9ddd5a952d2c780af1f9759c61cc49",
+  "kibi-usage/SKILL.md": "e19f255af525a64e8e8650271c7906f4e839521db944a3352972b7bf45537c85",
   "kibi-usage/resources/branch-lifecycle.md": "f1bf359e9826e83c548f3cd0287f8175a62456527b0132b06b3f9f74aa59b7d6",
   "kibi-usage/resources/fact-lanes.md": "97f5a9aaa331835018312d6684038c2b2a0c383827716fb7c9de3faedbee622b",
   "kibi-usage/resources/kb-improvement.md": "a8408fce27342bdce6415a6718599e53fe00bb33aa1fd3dc42353ec6f61adcd7",

package/dist/skills/kibi-usage/SKILL.md

@@ -2,7 +2,7 @@
 id: kibi-usage
 name: Kibi Usage
 description: Use Kibi's source-first, exact-Git, migration-aware, proof-aware operations safely across MCP or the trusted local CLI, including partial completion repair.
-version: 2.8.0
+version: 2.9.0
 kibiCompatibility: ">=1.0.0"
 tags:
   - kibi
@@ -260,7 +260,11 @@ constants) or `examples`, and why the current value was refused. With a
 `requirementId` whose requirement `constrains` one subject fact, the `subject`
 argument is already bound to that fact's `subject_key` (provenance
 `requirement`); keep it, so the predicate and the subject fact name one
-subject. Bind them
+subject. A schema without a `subject` argument (`permission_rule`) records
+that key as the planned fact's `subject_key` instead; when the requirement
+constrains several subjects, an unbound `subject_key` asks you to pass
+`subjectHint` with one of them. A participant (`actor`, `resource`, entity)
+is a short noun, never a clause of the claim. Bind them
 from the claim's own words and call again with the same `text` and
 `requirementId`, plus `schemaId` and `argumentBindings` keyed by
 `argument_names` (reuse `argument_constants` values when the schema has them).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kibi-cursor",
-  "version": "2.6.3",
+  "version": "2.6.4",
   "description": "Kibi Cursor plugin - thin adapter for Cursor MCP integration and editor hooks",
   "type": "module",
   "main": "dist/index.js",

package/skills/.canon-hash.json

@@ -13,7 +13,7 @@
   "kibi-traceability/resources/operation-access.md": "39f7972ab7f4ae7479e78f7072bb50e8e6c4cdf4f857425f69d2522d37db437c",
   "kibi-traceability/resources/source-authoring.md": "408c6ee2bef1b84e0194c0538ef929c26a0a617e631b2234247388140dbbdd08",
   "kibi-traceability/resources/traceability.md": "38c290a0bc71bd1692e115f22694743946e2f69630e134acfd43cee5f613fb88",
-  "kibi-usage/SKILL.md": "91688060880c219a867e995571d869fc7f9ddd5a952d2c780af1f9759c61cc49",
+  "kibi-usage/SKILL.md": "e19f255af525a64e8e8650271c7906f4e839521db944a3352972b7bf45537c85",
   "kibi-usage/resources/branch-lifecycle.md": "f1bf359e9826e83c548f3cd0287f8175a62456527b0132b06b3f9f74aa59b7d6",
   "kibi-usage/resources/fact-lanes.md": "97f5a9aaa331835018312d6684038c2b2a0c383827716fb7c9de3faedbee622b",
   "kibi-usage/resources/kb-improvement.md": "a8408fce27342bdce6415a6718599e53fe00bb33aa1fd3dc42353ec6f61adcd7",

package/skills/kibi-usage/SKILL.md

@@ -2,7 +2,7 @@
 id: kibi-usage
 name: Kibi Usage
 description: Use Kibi's source-first, exact-Git, migration-aware, proof-aware operations safely across MCP or the trusted local CLI, including partial completion repair.
-version: 2.8.0
+version: 2.9.0
 kibiCompatibility: ">=1.0.0"
 tags:
   - kibi
@@ -260,7 +260,11 @@ constants) or `examples`, and why the current value was refused. With a
 `requirementId` whose requirement `constrains` one subject fact, the `subject`
 argument is already bound to that fact's `subject_key` (provenance
 `requirement`); keep it, so the predicate and the subject fact name one
-subject. Bind them
+subject. A schema without a `subject` argument (`permission_rule`) records
+that key as the planned fact's `subject_key` instead; when the requirement
+constrains several subjects, an unbound `subject_key` asks you to pass
+`subjectHint` with one of them. A participant (`actor`, `resource`, entity)
+is a short noun, never a clause of the claim. Bind them
 from the claim's own words and call again with the same `text` and
 `requirementId`, plus `schemaId` and `argumentBindings` keyed by
 `argument_names` (reuse `argument_constants` values when the schema has them).