valent-pipeline 0.1.11 → 0.1.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "valent-pipeline",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "v3 multi-agent AI pipeline for software development lifecycle",
   "type": "module",
   "bin": {

package/pipeline/prompts/knowledge.md

@@ -36,13 +36,11 @@ Read all files in `{curated_files_path}`. Build in-memory index of file names, s
 ### Step 3: Connect to Knowledge Database (Conditional)
 
 **If `{knowledge_mode}` is `sqlite`:**
-Open `{sqlite_db_path}`. Query patterns:
-- Metadata: `SELECT content FROM artifacts WHERE story_id = ? AND artifact_type = ?`
-- Full-text: `SELECT * FROM artifacts_fts WHERE artifacts_fts MATCH ?`
-- Directives: `SELECT * FROM correction_directives WHERE target_agent = ? AND status = 'active'`
-- Cross-story: `SELECT * FROM artifacts WHERE artifact_type = 'bugs' AND created_at > ?`
-
-If database missing or empty, operate in curated-only mode.
+Verify the database is accessible by running:
+```bash
+npx tsx .valent-pipeline/scripts/query-kb.ts --stories
+```
+If it returns results or "No stories in database", the DB is accessible. If the command fails, operate in curated-only mode.
 
 **If `{knowledge_mode}` is `local-docker` or `connect-to-existing` (legacy):**
 Verify ChromaDB at `{chromadb_host}` using v2 API. Base path: `{chromadb_host}/api/v2/tenants/default_tenant/databases/default_database`. If connection fails, operate in curated-only mode.
@@ -54,7 +52,14 @@ Verify ChromaDB at `{chromadb_host}` using v2 API. Base path: `{chromadb_host}/a
 For each incoming query:
 1. Search correction directives for relevant entries
 2. Search curated knowledge files for matching sections
-3. If database connected: use FTS (SQLite) or collection query (ChromaDB)
+3. If database connected (SQLite mode): query using the CLI tool and read stdout for results:
+   - Fetch a specific artifact: `npx tsx .valent-pipeline/scripts/query-kb.ts --artifact --story KANBAN-001 --type reqs-brief`
+   - Fetch directives for an agent: `npx tsx .valent-pipeline/scripts/query-kb.ts --directives --agent BEND`
+   - Full-text search: `npx tsx .valent-pipeline/scripts/query-kb.ts --search "acceptance criteria"`
+   - List artifacts for a story: `npx tsx .valent-pipeline/scripts/query-kb.ts --list --story KANBAN-001`
+   - List all stories: `npx tsx .valent-pipeline/scripts/query-kb.ts --stories`
+   - Cross-story bug search: `npx tsx .valent-pipeline/scripts/query-kb.ts --bugs-since 2026-03-01`
+   If ChromaDB mode: use collection query (ChromaDB)
 4. Compose response: targeted, SHORT (aim ~200 tokens, max 500)
 5. Include source reference: `Source: curated/{file}#section` or `Source: sqlite:artifacts/{story_id}/{type}` or `Source: correction-directives#{directive-id}`
 

package/pipeline/prompts/lead.md

@@ -144,6 +144,12 @@ Before validating story inputs, read `{backlog_path}` and check whether the curr
 
 For `bug` type items (no story input directory), skip Steps 1-3 of kick-off. Instead, read the bug's `description`, `file_ref`, and `source_story` from the backlog. Spawn a targeted agent subset (BEND + CRITIC + QA-B) to fix and verify the bug. After the fix ships, mark the bug `shipped` in the backlog and return to next-item selection.
 
+### Step 0b: Verify Knowledge Database
+
+If `{knowledge_mode}` is `sqlite`, check that `.valent-pipeline/pipeline.db` exists. If it does not exist:
+1. Escalate to user: "Knowledge database not found. Run `/valent-setup-backlog` to initialize the knowledge base and create the database."
+2. Do NOT proceed with story execution until the database exists.
+
 ### Step 1: Validate Story Input
 
 Read story input files from `{story_input_dir}`. Validate against the input contract:

package/skills/valent-setup-backlog/SKILL.md

@@ -170,6 +170,13 @@ All three agents run in parallel using `model: "haiku"` to minimize cost. Collec
 
 If the repo is empty or brand new (no source code yet), skip the subagents and create minimal placeholder files noting "No existing code detected — Knowledge Agent will update these as stories ship."
 
+### Step 7b: Initialize and Populate Knowledge Database
+
+After writing the curated knowledge files:
+1. Run `valent-pipeline db init` to create the SQLite database if it doesn't exist
+2. Run `npx tsx .valent-pipeline/scripts/embed-sqlite.ts --rebuild --db-path .valent-pipeline/pipeline.db --stories-dir ./stories` to index any existing story artifacts
+3. The database is now ready for the Knowledge Agent to query during story execution
+
 ## Step 8: Report
 
 After writing all files, summarize: