@jayjiang/byoao 2.0.2 → 2.0.3

package/dist/assets/presets/common/AGENTS.md.hbs

@@ -14,6 +14,16 @@ Agent pages: Knowledge pages maintained by the Agent, located in `entities/`, `c
 **Use Obsidian CLI for all note operations** (`obsidian read`, `obsidian search`, `obsidian create`, etc.).
 Do not use bash (`cat`, `grep`, `find`, `sed`, etc.) to manipulate note files directly — Obsidian CLI correctly maintains wikilinks, frontmatter, and file relationships.
 
+## Knowledge Retrieval (Q&A)
+
+For questions that must be answered **from this vault** (not general knowledge), follow this chain. **Authoritative specification: the `/ask` skill** — if this summary diverges, follow `/ask`.
+
+- Read **`INDEX.base`** first when it exists (compiled knowledge map and page discovery).
+- Read **`SCHEMA.md`** when you need tag taxonomy, domain rules, or agent directory conventions.
+- Run **`obsidian search`** with each key concept; merge results across queries.
+- Run **`obsidian read`** on promising paths. Prefer agent pages under `entities/`, `concepts/`, `comparisons/`, and `queries/`, then pages whose tags or `domain` match the question, `status: reviewed` over `draft`, and more recent `updated`.
+- **Synthesize** a direct answer with `[[wikilink]]` citations and explicit gaps. Every claim should be backed by vault notes.
+
 ## Available Skills
 - **/cook** — Digest notes and external sources, compile knowledge pages
 - **/health** — Check knowledge page health (orphans, stale content, contradictions)

package/dist/assets/presets/common/SCHEMA.md.hbs

@@ -55,3 +55,7 @@ See the /cook skill specification for the complete frontmatter schema. Key requi
 ## Custom Fields
 
 No custom fields defined yet. The Agent documents new fields here when first used.
+
+## Retrieval
+
+Taxonomy, directories, and frontmatter support **filtering and ranking** during vault Q&A. The step-by-step protocol is summarized in **Knowledge Retrieval (Q&A)** in `AGENTS.md`; full behavior is defined by the **`/ask`** skill.

package/dist/index.js

@@ -28262,7 +28262,7 @@ async function configureProvider(provider, gcpProjectId) {
 
 // dist/vault/manifest.js
 import path4 from "node:path";
-var PKG_VERSION = "2.0.2";
+var PKG_VERSION = "2.0.3";
 var InfrastructureSchema = external_exports2.object({
   skills: external_exports2.array(external_exports2.string()).default([]),
   commands: external_exports2.array(external_exports2.string()).default([]),

package/dist/vault/manifest.js

@@ -1,7 +1,7 @@
 import { fs } from "../lib/cjs-modules.js";
 import path from "node:path";
 import { z } from "zod";
-const PKG_VERSION = "2.0.2";
+const PKG_VERSION = "2.0.3";
 // ── Schema ──────────────────────────────────────────────────────
 const InfrastructureSchema = z.object({
     skills: z.array(z.string()).default([]),

package/dist/vault/self-update.js

@@ -1,6 +1,6 @@
 import { execSync } from "node:child_process";
 import { semver } from "../lib/cjs-modules.js";
-const PKG_VERSION = "2.0.2";
+const PKG_VERSION = "2.0.3";
 // ── Constants ───────────────────────────────────────────────────
 const PACKAGE_NAME = "@jayjiang/byoao";
 const REGISTRY_TIMEOUT_MS = 5_000;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jayjiang/byoao",
-  "version": "2.0.2",
+  "version": "2.0.3",
   "description": "Build Your Own AI OS — Obsidian + AI Agent",
   "type": "module",
   "engines": {

package/src/assets/presets/common/AGENTS.md.hbs

@@ -14,6 +14,16 @@ Agent pages: Knowledge pages maintained by the Agent, located in `entities/`, `c
 **Use Obsidian CLI for all note operations** (`obsidian read`, `obsidian search`, `obsidian create`, etc.).
 Do not use bash (`cat`, `grep`, `find`, `sed`, etc.) to manipulate note files directly — Obsidian CLI correctly maintains wikilinks, frontmatter, and file relationships.
 
+## Knowledge Retrieval (Q&A)
+
+For questions that must be answered **from this vault** (not general knowledge), follow this chain. **Authoritative specification: the `/ask` skill** — if this summary diverges, follow `/ask`.
+
+- Read **`INDEX.base`** first when it exists (compiled knowledge map and page discovery).
+- Read **`SCHEMA.md`** when you need tag taxonomy, domain rules, or agent directory conventions.
+- Run **`obsidian search`** with each key concept; merge results across queries.
+- Run **`obsidian read`** on promising paths. Prefer agent pages under `entities/`, `concepts/`, `comparisons/`, and `queries/`, then pages whose tags or `domain` match the question, `status: reviewed` over `draft`, and more recent `updated`.
+- **Synthesize** a direct answer with `[[wikilink]]` citations and explicit gaps. Every claim should be backed by vault notes.
+
 ## Available Skills
 - **/cook** — Digest notes and external sources, compile knowledge pages
 - **/health** — Check knowledge page health (orphans, stale content, contradictions)

package/src/assets/presets/common/SCHEMA.md.hbs

@@ -55,3 +55,7 @@ See the /cook skill specification for the complete frontmatter schema. Key requi
 ## Custom Fields
 
 No custom fields defined yet. The Agent documents new fields here when first used.
+
+## Retrieval
+
+Taxonomy, directories, and frontmatter support **filtering and ranking** during vault Q&A. The step-by-step protocol is summarized in **Knowledge Retrieval (Q&A)** in `AGENTS.md`; full behavior is defined by the **`/ask`** skill.