t3528: address PR #317 review feedback (node-helpers.md + FTS5 probe)

.agents/scripts/onboarding-helper.sh

@@ -334,9 +334,13 @@
 	# Context7 is MCP-only, no auth needed
 	print_service "Context7" "ready" "MCP (no auth needed)"
 
-	# sqlite3 is required for memory system
+	# sqlite3 is required for memory system (FTS5 required for full-text search)
 	if is_installed "sqlite3"; then
-		print_service "sqlite3" "ready" "memory system ready"
+		if sqlite3 :memory: 'CREATE VIRTUAL TABLE t USING fts5(content);' &>/dev/null; then
+			print_service "sqlite3" "ready" "memory system ready"
+		else
+			print_service "sqlite3" "partial" "installed, missing FTS5 (required for memory)"
+		fi
 	else
 		print_service "sqlite3" "needs-setup" "required for memory system"
 	fi
@@ -1123,9 +1127,15 @@
 	is_installed "auggie" && json+='true' || json+='false'
 	json+=',"authenticated":'
 	is_cli_authenticated "auggie" && json+='true' || json+='false'
-	json+='},"sqlite3":{"installed":'
-	is_installed "sqlite3" && json+='true' || json+='false'
-	json+='}},'
+	local _sqlite3_installed=false _sqlite3_fts5=false
+	if is_installed "sqlite3"; then
+		_sqlite3_installed=true
+		sqlite3 :memory: 'CREATE VIRTUAL TABLE t USING fts5(content);' &>/dev/null && _sqlite3_fts5=true
+	fi
+	json+="},"
+	json+="$(jq -n --argjson inst "$_sqlite3_installed" --argjson fts5 "$_sqlite3_fts5" \
+		'"sqlite3":{"installed":$inst,"fts5":$fts5}')"
+	json+='},'
 
 	# Containers
 	json+='"containers":{'

.agents/tools/build-agent/build-agent.md

@@ -501,14 +501,8 @@ Where agents reference `npm` or `npx`, consider if `bun` would be faster:
 - Prefer `bunx` over `npx` for one-off executions
 
 **Node.js-based helper scripts:**
-If your helper script uses `node -e` with globally installed npm packages, add this near the top:
-
-```bash
-# Set NODE_PATH so Node.js can find globally installed modules
-export NODE_PATH="$(npm root -g):$NODE_PATH"
-```
-
-This is required because Node.js doesn't automatically search the global npm prefix when using inline evaluation (`node -e`).
+If your helper script uses `node -e` with globally installed npm packages, set `NODE_PATH` near the top of the script.
+See `tools/build-agent/node-helpers.md:13` for the snippet and explanation.
 
 ### Information Quality (All Domains)
 

.agents/tools/build-agent/node-helpers.md

@@ -0,0 +1,30 @@
+# Node.js Helper Script Patterns
+
+Reference for common patterns used in Node.js-based helper scripts.
+
+## NODE_PATH for globally installed npm packages
+
+When a helper script uses `node -e` with globally installed npm packages, Node.js
+does not automatically search the global npm prefix for inline evaluation. Set
+`NODE_PATH` near the top of the script so CommonJS `require()` can resolve global
+modules:
+
+```bash
+# Set NODE_PATH so Node.js can find globally installed modules
+export NODE_PATH="$(npm root -g):$NODE_PATH"
+```
+
+This is required because `node -e` evaluates code in CommonJS mode, and without
+`NODE_PATH` pointing at the global prefix, `require('some-global-package')` will
+fail with `MODULE_NOT_FOUND` even when the package is installed globally.
+
+> **Note:** `NODE_PATH` only affects CommonJS `require()`. ESM `import` specifiers
+> are not resolved via `NODE_PATH` — use explicit paths or local installs for ESM.
+
+## Prefer bun for performance
+
+Where scripts reference `npm` or `npx`, consider `bun` for faster execution:
+
+- `bun` is significantly faster for package operations
+- Compatible with most npm packages
+- Prefer `bunx` over `npx` for one-off executions