@vpxa/aikit 0.1.99 → 0.1.101

package/scaffold/dist/definitions/protocols.mjs

@@ -99,15 +99,15 @@ Past decisions, conventions, and patterns are stored in curated knowledge. Auto-
 
 \`\`\`
 search("keywords about the feature/area you're changing")  // check for past decisions
-list({ category: "decisions" })   // scan recent decisions that might apply
-list({ category: "conventions" }) // see project conventions (includes auto-captured)
+knowledge({ action: "list", category: "decisions" })   // scan recent decisions that might apply
+knowledge({ action: "list", category: "conventions" }) // see project conventions (includes auto-captured)
 scope_map("what you need")        // generates a reading plan
 \`\`\`
 
 **Rules:**
 - If results exist → **READ them and FOLLOW** established patterns. Do not silently override.
 - If results conflict with the current task → **surface the conflict** to the user/orchestrator.
-- If no results → proceed, but **\`remember()\` your decisions** afterward for future recall.
+- If no results → proceed, but **persist your decisions with \`knowledge({ action: "remember", ... })\`** afterward for future recall.
 - Never assume "there's nothing stored" — always search first.
 
 ### Step 3: Real-time Exploration (only
@@ -199,7 +199,7 @@ Before making changes, establish expected scope. Flag deviations early.
 
 ## MANDATORY: Memory Persistence Before Completing
 
-**Before finishing ANY task**, you MUST call \`remember()\` if ANY of these apply:
+**Before finishing ANY task**, you MUST call \`knowledge({ action: "remember", ... })\` if ANY of these apply:
 
 - ✅ You discovered how something works that wasn't in onboard artifacts
 - ✅ You made an architecture or design decision
@@ -207,9 +207,10 @@ Before making changes, establish expected scope. Flag deviations early.
 - ✅ You identified a pattern, convention, or project-specific gotcha
 - ✅ You encountered and resolved an error that others might hit
 
-**How to remember:**
+**How to persist knowledge:**
 \`\`\`
-remember({
+knowledge({
+  action: "remember",
   title: "Short descriptive title",
   content: "Detailed finding with context",
   category: "patterns" | "conventions" | "decisions" | "troubleshooting"
@@ -217,13 +218,13 @@ remember({
 \`\`\`
 
 **Examples:**
-- \`remember({ title: "Auth uses JWT refresh tokens with 15min expiry", content: "Access tokens expire in 15 min, refresh in 7 days. Middleware at src/auth/guard.ts validates.", category: "patterns" })\`
-- \`remember({ title: "Build requires Node 20+", content: "Uses Web Crypto API — Node 18 fails silently on crypto.subtle calls.", category: "conventions" })\`
-- \`remember({ title: "Decision: LanceDB over Chroma for vector store", content: "LanceDB is embedded (no Docker), supports WASM, better for user-level MCP.", category: "decisions" })\`
+- \`knowledge({ action: "remember", title: "Auth uses JWT refresh tokens with 15min expiry", content: "Access tokens expire in 15 min, refresh in 7 days. Middleware at src/auth/guard.ts validates.", category: "patterns" })\`
+- \`knowledge({ action: "remember", title: "Build requires Node 20+", content: "Uses Web Crypto API — Node 18 fails silently on crypto.subtle calls.", category: "conventions" })\`
+- \`knowledge({ action: "remember", title: "Decision: LanceDB over Chroma for vector store", content: "LanceDB is embedded (no Docker), supports WASM, better for user-level MCP.", category: "decisions" })\`
 
 **If you complete a task without remembering anything, you likely missed something.** Review what you learned.
 
-For outdated AI Kit entries → \`update(path, content, reason)\`
+For outdated AI Kit entries → \`knowledge({ action: "update", path, content, reason })\`
 
 ---
 
@@ -239,14 +240,14 @@ For outdated AI Kit entries → \`update(path, content, reason)\`
 
 | Phase | What to do | Compress after? |
 |-------|-----------|----------------|
-| **Understand** | Search KB, read summaries, trace symbols | Yes — \`digest\` findings before planning |
+| **Understand** | Search AI Kit, read summaries, trace symbols | Yes — \`digest\` findings before planning |
 | **Plan** | Design approach, identify files to change | Yes — \`stash\` the plan, compact analysis |
 | **Execute** | Make changes, one sub-task at a time | Yes — compact between independent sub-tasks |
 | **Verify** | \`check\` + \`test_run\` + \`blast_radius\` | — |
 
 **Rules:**
 - **Never compact mid-operation** — finish the current sub-task first
-- **Recycle context to files** — save analysis results via \`stash\` or \`remember\`, not just in conversation
+- **Recycle context to files** — save analysis results via \`stash\` or \`knowledge({ action: "remember", ... })\`, not just in conversation
 - **Decompose monolithic work** — break into independent chunks, pass results via artifact files between sub-tasks
 - **One-shot sub-tasks** — for self-contained changes, provide all context upfront to avoid back-and-forth
 
@@ -435,7 +436,7 @@ scope_map("what you need to investigate")
 for code exploration (graph FIRST for module relationships)
 - Use \`graph({ action: 'neighbors' })\` to understand cross-module dependencies before diving into symbol details
 - Use \`file_summary\`, \`compact\` for efficient file reading
-- Use \`analyze_structure\`, \`analyze_dependencies\` for package-level understanding
+- Use \`analyze({ aspect: "structure", ... })\`, \`analyze({ aspect: "dependencies", ... })\` for package-level understanding
 - Use \`web_search\`, \`web_fetch\` for external documentation
 
 ### Phase 3: Synthesis
@@ -454,21 +455,22 @@ Return structured findings. Always include:
 
 ### Phase 5: MANDATORY — Persist Discoveries
 
-**Before returning your report**, you MUST call \`remember()\` for:
+**Before returning your report**, you MUST call \`knowledge({ action: "remember", ... })\` for:
 - ✅ Architecture insights not already in onboard artifacts
 - ✅ Non-obvious findings, gotchas, or edge cases
 - ✅ Trade-off analysis and recommendations made
 - ✅ External knowledge gathered from web_search/web_fetch
 
 \`\`\`
-remember({
+knowledge({
+  action: "remember",
   title: "Short descriptive title",
   content: "Detailed finding with context",
   category: "patterns" | "conventions" | "decisions" | "troubleshooting"
 })
 \`\`\`
 
-**If you complete research without remembering anything, you wasted tokens.** Your research should enrich the knowledge base for future sessions.
+**If you complete research without persisting anything, you wasted tokens.** Your research should enrich the AI Kit knowledge store for future sessions.
 
 ---
 
@@ -561,7 +563,7 @@ Workflow;
 1 ** AI;
 Kit;
 Recall** —
-\`search("conventions relevant-area")\` + \`list()\`
+\`search("conventions relevant-area")\` + \`knowledge({ action: "list" })\`
 for past review findings, patterns
 2. **Blast
 Radius** —
@@ -572,8 +574,9 @@ Radius** —
 6. **Report** — Structured findings
 with verdict
 7. **Persist** —
-\`remember(
+\`knowledge(
 {
+  action: "remember",
   title: 'Review: <finding>', content;
   : "<details>", category: "patterns"
 }
@@ -736,16 +739,17 @@ Workflow;
 1 ** AI;
 Kit;
 Recall** —
-\`search("architecture decisions boundaries")\` + \`list()\`
+\`search("architecture decisions boundaries")\` + \`knowledge({ action: "list" })\`
 for past ADRs, patterns
 2. **Analyze** —
-\`analyze_structure\`, \`analyze_dependencies\`, \`blast_radius\`
+\`analyze({ aspect: "structure", ... })\`, \`analyze({ aspect: "dependencies", ... })\`, \`blast_radius\`
 3. **Evaluate** — Check all dimensions below
 4. **Report** — Structured findings
 with verdict
 5. **Persist** —
-\`remember(
+\`knowledge(
 {
+  action: "remember",
   title: 'Architecture: <finding>', content;
   : "<details>", category: "decisions"
 }
@@ -971,7 +975,7 @@ The Orchestrator synthesizes BOTH layers (original research + peer reviews) into
 Then:
 1. **Present** the verdict using \`present(format: "html" )\` with comparison blocks
 2. **Produce an ADR** via the \`adr-skill\`
-3. **\`remember\`** the decision for future recall
+3. **\`knowledge({ action: "remember", ... })\`** the decision for future recall
 
 ## When to Use (Auto-Trigger Rules)
 
@@ -993,14 +997,14 @@ Trigger the decision protocol when there is an **unresolved non-trivial technica
 - Never make a non-trivial technical decision without multi-model analysis
 - Always present the verdict visually using \`present\`
 - **Produce an ADR** after every decision resolution
-- \`remember\` the decision for future recall
+- \`knowledge({ action: "remember", ... })\` the decision for future recall
 
 ## Shortcut: Floor-Tier Decisions
 
 For decisions classified as **Floor tier** (blast_radius ≤ 2, single concern):
 - Skip Phase 2 (peer review) — synthesis directly from Phase 1
 - Verdict format still required but can be abbreviated
-- ADR is optional (use \`remember\` at minimum)
+- ADR is optional (use \`knowledge({ action: "remember", ... })\` at minimum)
 `,"forge-protocol":`# FORGE Protocol — Quality Overlay
 
 > Follow the FORGE (Fact-Oriented Reasoning with Graduated Evidence) protocol for all code generation and modification tasks.