@antoneeo/kb-agentic-skill 1.15.0 → 1.16.0

package/CHANGELOG.md

@@ -2,6 +2,46 @@
 
 Every significant change to this skill is recorded here.
 
+## [1.16.0] - 2026-09-12
+
+### Changed
+- **F-054: the recall verdict names every branch the descent opened.** The
+  descent is multi-branch by mandate (`taxonomy.md` §1: follow every parent,
+  open the final candidates), and the verdict vocabulary assumed exactly one
+  matched slug — so a mandated act had no legal way to declare its result, and
+  an agent facing two legitimate branches invented a shape for it. Both
+  node-naming verdicts now read `kb: <slug>[, <slug> …] → …`, naming every slug
+  opened and not only the one that answered, because which branches were read is
+  the part of the verdict a reader can check. **Four legal values, unchanged**:
+  the repair is the form, never a fifth value, and the count is pinned against
+  creep. Found by replaying the doctrine against a real question rather than by
+  reading it.
+
+### Fixed
+- **The behavioural eval driver died on its own scenarios.** `run_behavioral.py`
+  read scenarios as UTF-8 and printed them to a console that, on Windows,
+  defaults to cp1252 — which has no mapping for `→`. The shipped scenario
+  `recall_descends_before_answering.md` has contained that character since 1.7.0,
+  so on a default Windows console that eval was un-runnable and the driver
+  exited before printing its own pass criteria. stdout is now reconfigured to
+  UTF-8 with `errors="replace"`: a console that cannot render a glyph is not a
+  reason to withhold the scenario.
+
+### Not demonstrated
+- **The defect this release was opened to fix does not exist, as stated.** The
+  claim was that the recall's four verdicts all sit downstream of one instrument,
+  so a descent picking the wrong branch declares `kb: no coverage` on a corpus
+  that holds the answer — a false negative indistinguishable from real absence.
+  Two agent-level replays refuted it, including a fixture built to be hostile
+  (eight topics, the answering claim under `gdpr_compliance` while
+  `observability` was the more plausible branch): both returned the right claim,
+  and one ran a `grep` cross-check unprompted. A mandated text probe and a
+  generated claims inventory were therefore abandoned rather than shipped, and no
+  assertion pins them — a probe pinning what was decided against is red by
+  construction. Standing limit: two runs, one subject model, fixtures authored by
+  the session that made the claim. Record in
+  `ai_docs/solutions/SPIKE_kb_recall_second_instrument.md`.
+
 ## [1.15.0] - 2026-09-12
 
 ### Fixed

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "kb-agentic-skill",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "Knowledge-Base & Document-First protocol with risk triage, Vision governance, signal distillation and optional devPNT integration.",
   "author": "Antonio Pinto (https://github.com/Antoneeo)"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antoneeo/kb-agentic-skill",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "Knowledge-Base & Document-First protocol for Claude Code, Gemini CLI, Google Antigravity and Codex with risk triage, Vision governance, signal distillation and optional devPNT integration.",
   "keywords": [
     "claude-code",

package/skills/kb-agentic-skill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: kb-agentic
-version: 1.15.0
+version: 1.16.0
 description: Knowledge-Base & Document-First protocol with risk-proportional triage, Vision as a guide, Signal Distillation, a complete Standalone mode and optional symbiosis with devPNT. Use for user documentation, knowledge extraction, SOPs, research notes, decision logs, knowledge management — and for answering project questions from the claim ledger and topic graph.
 author: Antonio Pinto (https://github.com/Antoneeo)
 copyright: (c) 2026 Antonio Pinto
@@ -171,9 +171,15 @@ twin of the guide consult above.
   cited without naming its successor.
 - **The declared verdict — only when the recall ran**, never a per-turn ritual. Four
   legal values:
-  - `kb: <slug> → N claims cited`
-  - `kb: <slug> → node matched, no claims` — surface the node's `gaps:` when it answers
-    the question: "the KB knows it doesn't know" is a first-class answer.
+  - `kb: <slug>[, <slug> …] → N claims cited` — **every** slug the descent opened, not
+    only the one that answered. The descent is multi-branch by mandate (`taxonomy.md`
+    §1: follow every parent, open the final candidates), so a single-slug form cannot
+    state what a correct descent did: the agent either under-reports the branches it
+    read or invents a shape for them, and both make a thorough descent
+    indistinguishable from a lucky one. Which branches were opened is the part of this
+    verdict a reader can actually check.
+  - `kb: <slug>[, <slug> …] → node matched, no claims` — surface the node's `gaps:` when
+    it answers the question: "the KB knows it doesn't know" is a first-class answer.
   - `kb: no coverage` — index read, nothing fits.
   - `kb: index absent — regenerate (sdlc_check.py index)` — the INDEX is missing, not
     necessarily the graph (nodes routinely exist while the index lags); regenerate and