kibi-opencode 0.5.0 → 0.5.1

package/README.md

@@ -29,10 +29,10 @@ The plugin provides context-aware prompt guidance based on recent edits and work
 
 ### Targeted Validation Checks
 
-After KB-document edits, the plugin queues targeted `kibi check` rules to run after sync:
+After KB-document edits, the plugin queues targeted validation rules to run via background sync operations:
 
-- **Must-priority requirement edits**: `kibi check --rules required-fields,no-dangling-refs,must-priority-coverage`
-- **Other requirement/scenario/test/ADR/fact edits**: `kibi check --rules required-fields,no-dangling-refs`
+- **Must-priority requirement edits**: elevated validation including coverage checks
+- **Other requirement/scenario/test/ADR/fact edits**: standard validation for required fields and dangling references
 
 The plugin inspects requirement frontmatter to detect `priority: must` and schedules elevated validation for critical requirements. Runs in background after sync completes, non-blocking. Can be disabled via `guidance.targetedChecks.enabled: false`.
 
@@ -42,7 +42,7 @@ When `guidance.warnOnKbEdits` is enabled (default: `true`), manual edits to file
 
 - Logs warning immediately
 - Injects prompt guidance discouraging manual `.kb` edits
-- Directs agents toward MCP/CLI tools (`kb_upsert`, `kb_query`, etc.)
+- Directs agents toward public MCP tools (`kb_upsert`, `kb_query`, etc.)
 
 ### Session Tracking and Pattern Detection
 
@@ -96,9 +96,9 @@ The plugin injects guidance into OpenCode sessions to improve agent grounding. U
 
 OpenCode exposes Kibi MCP prompts as slash commands. The `/init-kibi` command runs the retroactive bootstrap workflow using only public MCP tools.
 
-### Debounced Sync
+### Background Sync Operations
 
-Automatically runs `kibi sync` after relevant file edits:
+Internal maintenance automatically syncs the knowledge base after relevant file edits:
 
 - Single-flight scheduler (no overlapping syncs)
 - Debounce window (default: 2000ms)
@@ -183,10 +183,10 @@ This repository's OpenCode setup dogfoods local built artifacts. `opencode.json`
 
 ## Architecture
 
-This is a thin bridge layer:
+This is a thin bridge layer per ADR-016:
 
-- Reuses `kibi` CLI for sync operations
-- Reuses existing MCP tools (`kb_query`, `kb_check`, etc.)
+- **Agent-visible guidance**: Public MCP tools (`kb_query`, `kb_upsert`, `kb_check`, etc.) and sanctioned slash commands (`/init-kibi`)
+- **Internal maintenance**: Background sync operations handle KB synchronization; agents do NOT run sync commands directly
 - Does NOT own KB storage, parsing, or validation
 
 ### Future: File-Context Virtual Injection

package/dist/prompt.js

@@ -3,14 +3,14 @@ const SENTINEL = "<!-- kibi-opencode -->";
 /**
  * Build prompt guidance block based on path kind.
  */
-// implements REQ-opencode-kibi-plugin-v1
+// implements REQ-opencode-kibi-plugin-v1, REQ-opencode-agent-mcp-only
 function buildContextualGuidance(context) {
     const parts = [SENTINEL];
     if (context.hasRecentKbEdit) {
         parts.push(`
 ⚠️  **WARNING: Do not edit .kb/** files manually.**
 
-The Kibi knowledge base is managed through MCP and CLI tools. Direct manual edits to files under .kb/** can cause inconsistencies and should be avoided.
+The Kibi knowledge base is managed through public MCP tools and internal maintenance flows. Direct manual edits to files under .kb/** can cause inconsistencies and should be avoided.
 
 Instead:
 - Use kb_upsert to create/update entities
@@ -22,10 +22,11 @@ Instead:
         parts.push(`
 🔧 **Bootstrap required**
 
-This repository does not appear to have Kibi initialized. Consider running:
-- \`/init-kibi\` for retroactive bootstrap of existing repos
-- \`kibi init\` for new repos
-- \`kibi doctor\` to verify your environment
+This repository does not appear to have Kibi initialized. Agents should:
+- Use \`/init-kibi\` for retroactive bootstrap of existing repos (preferred MCP command)
+- Ask the user/operator to run setup or repair outside this session if \`/init-kibi\` is insufficient
+
+Do not run \`kibi\` CLI commands directly; use the MCP tools (kb_query, kb_upsert, kb_delete, kb_check).
 `);
     }
     const codeEdits = context.recentEdits.filter((e) => e.kind === "code");
@@ -121,7 +122,7 @@ Preferred structure:
 
 When editing KB documentation:
 1. **Maintain traceability** - Link entities using relationships: specified_by (req→scenario), verified_by (req→test), etc.
-2. **Validate** - Run \`kibi check\` after making changes to catch integrity issues.
+2. **Validate** - Use \`kb_check\` after making changes to catch integrity issues.
 3. **Follow entity patterns** - Ensure each entity has proper frontmatter with required fields.
 `);
     }
@@ -144,6 +145,8 @@ Dogfood note for this repo: OpenCode here uses local built \`kibi-mcp\` and \`ki
 
 **Public Kibi tools only:** kb_query, kb_upsert, kb_delete, kb_check.
 
+Do not invoke Kibi CLI commands directly from the agent.
+
 Bootstrap existing repos: use \`/init-kibi\` to run the retroactive initialization workflow.`);
     }
     return parts.join("\n\n").trim();
@@ -170,6 +173,8 @@ Dogfood note for this repo: OpenCode here uses local built \`kibi-mcp\` and \`ki
 
 **Public Kibi tools only:** kb_query, kb_upsert, kb_delete, kb_check.
 
+Do not invoke Kibi CLI commands directly from the agent.
+
 Bootstrap existing repos: use \`/init-kibi\` to run the retroactive initialization workflow.`;
 /**
  * Build prompt with contextual guidance based on recent edits and workspace state.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kibi-opencode",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Kibi OpenCode plugin - thin adapter to integrate Kibi with OpenCode sessions",
   "type": "module",
   "main": "dist/index.js",