@jayjiang/byoao 1.1.2 → 2.0.1

package/dist/assets/presets/common/templates/Investigation.md

@@ -1,34 +0,0 @@
----
-title: ""
-type: investigation
-status: draft
-date: {{date}}
-jira: ""
-hypothesis: ""
-conclusion: ""
-tags: [investigation, spike]
----
-
-## Question
-
-What are we trying to find out?
-
-## Hypothesis
-
-What we expect to find and why.
-
-## Method
-
-How we investigated (queries, tools, data sources).
-
-## Findings
-
--
-
-## Conclusion
-
-Summary of what we learned. Does it confirm or refute the hypothesis?
-
-## Next Steps
-
--

package/dist/assets/presets/common/templates/Meeting Notes.md

@@ -1,25 +0,0 @@
----
-title: ""
-type: meeting
-status: active
-date: {{date}}
-participants: []
-meeting-type: ""
-tags: [meeting]
----
-
-## Agenda
-
-1.
-
-## Notes
-
--
-
-## Decisions
-
--
-
-## Action Items
-
-- [ ] @person — task — due date

package/dist/assets/skills/emerge.md

@@ -1,168 +0,0 @@
----
-name: emerge
-description: Surface conclusions, patterns, and insights the vault implies but never explicitly states. Analyzes clusters, orphans, and cross-domain connections. Use when the user asks "what patterns do you see", "what am I missing", "analyze my vault", "find hidden connections", or wants a big-picture review of their knowledge base.
----
-
-# /emerge — Surface Hidden Patterns
-
-You are a pattern recognition analyst. Your job is to read across the user's vault and surface insights that the notes collectively imply but never explicitly state — hidden conclusions, recurring themes, unnoticed contradictions, and latent connections.
-
-## Prerequisites Check
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display the Obsidian CLI availability message (see /weave for the full error text).
-
-## Tool Selection
-
-Use `obsidian` CLI for content operations (read, search, backlinks, properties, tags). Use BYOAO tools (`byoao_search_vault`, `byoao_graph_health`) when Obsidian CLI is unavailable or for graph-level structural queries.
-
-## Parameters
-
-- **scope** (optional): Limit analysis to a folder, domain, or tag. Default: entire vault.
-- **depth** (optional): "quick" (top-level scan) or "deep" (read every note in scope). Default: "quick".
-- **output** (optional): If set, save findings as a note at this path.
-
-## Process
-
-### Sampling Strategy
-
-If a domain or search returns more than 30 notes, prioritize: (1) most recent 10, (2) most-linked 10 (highest backlink count), (3) notes with `status: active`. Read these first, then scan remaining titles and frontmatter to check for outliers before synthesizing.
-
-### Step 1: Map the Vault
-
-Build a structural picture:
-
-```bash
-obsidian list
-obsidian properties sort=count counts
-obsidian tags
-```
-
-Identify:
-- Total notes and their distribution across folders/domains
-- Most-used tags and properties
-- Cluster density (which areas have many interconnected notes vs sparse ones)
-
-### Step 2: Find Structural Signals
-
-Use graph-level queries to identify interesting patterns:
-
-**Orphan notes** — notes with no links in or out:
-Use `byoao_graph_health` or scan notes checking for those with zero wikilinks (no `[[` in content) and zero backlinks.
-Orphans may contain ideas the user hasn't connected yet.
-
-**Dead-end notes** — notes that link out but nobody links to them:
-Scan for notes with outgoing wikilinks but no backlinks.
-
-**Hub notes** — notes with unusually many backlinks:
-```bash
-obsidian backlinks "<note>"
-```
-Hubs reveal what the user's thinking centers around.
-
-**Tag clusters** — tags that always co-occur:
-If `#migration` and `#payments` always appear together, there's an implicit connection.
-
-### Step 3: Cross-Domain Analysis
-
-For each domain (from frontmatter `domain` field or folder grouping):
-
-1. **Read a sample of notes** (5-10 per domain, prioritizing recent and highly-linked)
-2. **Extract key themes** — what topics recur within the domain?
-3. **Look for cross-domain bridges** — concepts mentioned in multiple domains
-4. **Identify tension** — contradictory statements across domains or time periods
-
-### Step 4: Pattern Detection
-
-Look for these specific pattern types:
-
-**Recurring questions**: The same question asked in multiple notes but never answered.
-> "You've asked 'what's our rollback strategy?' in 4 different meeting notes but no note contains an answer."
-
-**Implicit decisions**: A direction was taken without a documented decision.
-> "Notes shifted from Option A to Option B around April, but no decision record exists."
-
-**Convergent threads**: Separate lines of thinking that are heading toward the same conclusion.
-> "Your notes on 'API rate limiting' and 'user quotas' both point toward a tiered access model, but neither note references the other."
-
-**Forgotten threads**: Topics that received attention then went silent.
-> "'Data mesh' appears in 6 notes between Jan-Mar but hasn't been mentioned since."
-
-**Expertise gaps**: The vault references a topic repeatedly but always superficially.
-> "'Kubernetes networking' appears in 12 notes but always as a dependency, never deeply explored."
-
-**Contradictions**: Conflicting statements across notes.
-> "In [[Note A]] you wrote 'we should avoid microservices' but [[Note B]] proposes splitting the monolith."
-
-### Step 5: Synthesize Insights
-
-For each pattern found, formulate an insight:
-
-```markdown
-## Insight: {title}
-
-**Pattern**: {what you observed}
-**Evidence**: {list of notes with brief quotes}
-**Implication**: {what this might mean — phrased as a question, not a conclusion}
-**Suggested action**: {what the user could do — write a note, make a decision, connect notes}
-```
-
-### Step 6: Present Findings
-
-```markdown
-# Emerge: Vault Patterns
-
-Analyzed {N} notes across {M} domains.
-
-## Key Findings
-
-### 1. {Insight title}
-{Pattern, evidence, implication, action}
-
-### 2. {Insight title}
-...
-
-## Structural Observations
-
-- **Most connected**: [[Note]] ({N} backlinks) — your thinking hub
-- **Most isolated**: {N} orphan notes that may contain undeveloped ideas
-- **Busiest domain**: {domain} ({N} notes)
-- **Thinnest domain**: {domain} ({N} notes) — possible blind spot
-
-## Suggested Next Steps
-
-1. {Actionable suggestion — e.g. "Connect [[A]] and [[B]] — they discuss the same problem"}
-2. {Actionable suggestion — e.g. "Write a decision record for the implicit choice between X and Y"}
-3. {Actionable suggestion — e.g. "Run /trace on 'data mesh' to understand why it was abandoned"}
-```
-
-### Step 7: Save (Optional)
-
-At the end of your findings, ask:
-
-> "Would you like me to save this as a note?"
-
-If the user confirms, save with frontmatter:
-
-```yaml
----
-title: "Emerge: Vault Patterns"
-note_type: literature
-type: analysis
-date: <today>
-tags: [emerge, patterns]
----
-```
-
-Use `obsidian create` to save. Ask the user where they'd like it saved.
-
-## Key Principles
-
-- **Show, don't tell**: Always cite specific notes and quotes. Never claim a pattern exists without evidence.
-- **Questions over conclusions**: Frame implications as questions the user should consider, not answers you've decided.
-- **Respect user judgment**: The user may be aware of patterns and have chosen not to act. Present findings neutrally.
-- **Prioritize actionable insights**: "These two notes should link to each other" is more useful than "your vault has 12 orphans."
-- **Deep mode means thorough**: In "deep" mode, read every note in scope. In "quick" mode, use structural signals and sampling.

package/dist/assets/skills/weave.md

@@ -1,287 +0,0 @@
----
-name: weave
-description: Scan vault notes, enrich with frontmatter + wikilinks, suggest permanent concept notes, and create a connected knowledge graph. Use when the user says "connect my notes", "add links", "enrich", "run weave", "weave my vault", or after importing new files into the vault.
----
-
-# /weave — Connect Your Notes
-
-You are a knowledge graph builder. Your job is to scan vault notes, enrich them with frontmatter and wikilinks, suggest permanent concept notes, and create hub notes for frequently referenced topics — turning scattered files into an interconnected knowledge graph inspired by the Zettelkasten method.
-
-## Prerequisites Check
-
-**Before doing anything else**, verify Obsidian CLI is available:
-
-```bash
-obsidian --version
-```
-
-If this fails, STOP and display:
-
-```
-Obsidian CLI is not available. Please ensure:
-1. Obsidian is running
-2. This vault is open in Obsidian
-3. CLI is enabled: Settings → General → Advanced → Command-line interface
-```
-
-Do NOT proceed with degraded results — graph queries are essential.
-
-## Parameters
-
-- **file** (optional): Path to a single file to weave. If omitted, scan the entire vault.
-- **folder** (optional): Path to a folder to scan. If omitted, scan the entire vault.
-- **dry-run** (optional): If set, show proposed changes without applying them.
-
-## File Exclusion Rules
-
-When scanning files, skip:
-
-| Pattern | Reason |
-|---------|--------|
-| `.obsidian/` | Obsidian internal config |
-| `.git/` | Git internals |
-| `.byoao/` | BYOAO internal data |
-| `node_modules/` | Dependencies |
-| `.env`, `credentials.*`, `*.key` | Sensitive files |
-| Binary files (images, PDFs, etc.) | Cannot add frontmatter/wikilinks |
-| `AGENTS.md` | BYOAO-managed file |
-| `*.base` | Obsidian Base files — not user content notes |
-
-Report skipped non-markdown files at the end: "Skipped N non-markdown files".
-
-## Process
-
-Execute these steps in order. Be explicit about each tool call — different LLM providers must execute this consistently.
-
-### Step 1: Build Vault Map
-
-```bash
-obsidian list
-```
-
-This gives you the full list of notes. Also run:
-
-```bash
-obsidian properties sort=count counts
-```
-
-This reveals the vault's structure — which properties are used, how many notes have frontmatter.
-
-### Step 2: Scan Target Files
-
-For each markdown file in scope (respecting exclusion rules):
-
-#### 2a. Read the file
-
-```bash
-obsidian read "<note name>"
-```
-
-#### 2b. Identify entities
-
-Scan the content for concepts using semantic understanding (not a predefined list):
-
-- **People names** — proper nouns that appear to be people
-- **Project/product names** — capitalized multi-word phrases that recur
-- **Domain concepts** — technical terms, acronyms, recurring themes
-- **Tool/system names** — software, services, platforms mentioned
-- **Dates and events** — meetings, deadlines, milestones
-- **Methodologies/frameworks** — named approaches like "Zettelkasten", "Agile", etc.
-
-#### 2c. Cross-reference against existing notes
-
-For each entity found:
-
-1. Does a vault note with this name exist? → Mark as wikilink candidate
-2. Is it a new, unrecognized concept? → Track for permanent note suggestion (Step 4)
-
-#### 2d. Propose frontmatter
-
-If the file has no frontmatter, or has incomplete frontmatter, propose additions:
-
-```yaml
----
-title: "<inferred from content or filename>"
-note_type: <fleeting | literature | permanent>
-type: "<inferred: meeting, idea, reference, daily, project, person, etc>"
-date: YYYY-MM-DD
-domain: "<knowledge area: analytics, infrastructure, design, etc>"
-references:
-  - "[[Related Note]]"
-tags: [<relevant tags>]
-status: <draft | active | completed | archived>
-source: "<URL if this note originates from a cloud document>"
----
-```
-
-**note_type classification (Zettelkasten):**
-
-| `note_type` | When to use |
-|-------------|-------------|
-| `fleeting` | Raw inputs: quick notes, meeting minutes, clipped articles, thoughts not yet processed |
-| `literature` | Processed references: summaries of papers, books, articles, or external sources |
-| `permanent` | Atomic concepts: single-idea notes that synthesize understanding from multiple sources |
-
-If unsure, default to `fleeting` — the user can reclassify later.
-
-**Date resolution (mandatory — never leave empty):**
-
-1. Extract from content — explicit dates in the text, meeting dates, file name patterns (e.g. `2026-03-27-meeting.md`)
-2. If no date in content, get the file creation time:
-   ```bash
-   stat -f '%SB' -t '%Y-%m-%d' "<file path>"   # macOS
-   stat -c '%w' "<file path>"                    # Linux (birth time)
-   ```
-   If birth time is unavailable (`-` or empty), fall back to modification time:
-   ```bash
-   stat -f '%Sm' -t '%Y-%m-%d' "<file path>"    # macOS
-   stat -c '%y' "<file path>"                    # Linux
-   ```
-3. Never leave `date` empty in the proposed frontmatter.
-
-**Source field (optional):**
-
-- Add `source` only when the note clearly originates from a cloud document (e.g. contains Confluence export markers, Google Docs formatting, or a URL in the content pointing to the original).
-- If the file already has a `source` field, always preserve it.
-
-**Frontmatter preservation rules:**
-- **Never overwrite** existing fields
-- **Only add** missing fields
-- **Merge arrays** — if file has `tags: [meeting]` and you suggest `tags: [meeting, migration]`, result is `[meeting, migration]`
-- **Warn on conflicts** — if existing value seems wrong, note it but don't change it
-
-#### 2e. Propose wikilinks
-
-Convert plain text mentions to `[[wikilinks]]`:
-
-- Existing note names → `[[Note Name]]`
-- People → `[[Person Name]]`
-- Domain concepts → `[[Concept Name]]`
-
-Rules:
-- Only link the **first occurrence** of each term in a file
-- Don't link inside code blocks, frontmatter, or existing wikilinks
-- Don't link common English words even if they happen to match a note name
-- Preserve the original text when the casing differs: `rate limiting` → `[[Rate Limiting|rate limiting]]`
-
-### Step 3: Backup Before Modification
-
-Before modifying any file, create a backup:
-
-```bash
-mkdir -p .byoao/backups/<timestamp>
-cp "<file path>" ".byoao/backups/<timestamp>/<filename>"
-```
-
-Use the current date-time as the timestamp (e.g., `2026-03-27T20-45`).
-
-This is critical for existing folder adoption where files are user-created and irreplaceable.
-
-### Step 4: Apply Changes
-
-For each file with proposed changes:
-1. Show the user a summary of proposed changes (frontmatter additions, wikilinks to add)
-2. Wait for confirmation before applying
-3. Apply changes using file edit tools
-
-### Step 5: Suggest Permanent Notes
-
-After scanning all files, analyze concept frequency across the vault:
-
-**When to suggest a permanent note:**
-- A concept appears in 3+ notes
-- No dedicated note exists for that concept
-- The concept has a clear, non-ambiguous definition
-
-For each candidate, present to the user:
-
-```markdown
-### Permanent Note Candidate: [[Concept Name]]
-
-**Appears in:** [[Note A]], [[Note B]], [[Note C]]
-
-**Proposed content:**
-
----
-title: "Concept Name"
-note_type: permanent
-type: reference
-domain: <inferred from source notes>
-date: <today>
-tags: [<inferred>]
-references:
-  - "[[Note A]]"
-  - "[[Note B]]"
----
-
-# Concept Name
-
-*Auto-generated by /weave — this concept appears across multiple notes. Review and refine.*
-
-## Summary
-<1-2 sentence summary synthesized from source notes>
-
-## References
-- [[Note A]] — <context>
-- [[Note B]] — <context>
-```
-
-Ask the user: "Create this permanent note?" Only create if confirmed.
-
-### Step 6: Suggest Note Splitting (Zettelkasten Atomicity)
-
-Check for notes that contain multiple independent concepts. For each candidate:
-
-```markdown
-### Split Suggestion: [[Multi-Concept Note]]
-
-This note appears to cover multiple distinct concepts:
-1. **Concept A** — <brief description>
-2. **Concept B** — <brief description>
-3. **Concept C** — <brief description>
-
-Consider splitting these into separate atomic notes for better knowledge graph connectivity.
-```
-
-**Do NOT split automatically.** Only suggest; the user decides.
-
-### Step 7: Directory Organization (optional)
-
-If the vault has many files in flat or disorganized directories, suggest:
-
-"Your vault has files that could benefit from reorganization.
-Run `/organize` to see a proposed directory structure based on
-the frontmatter metadata we just added. It uses `obsidian move`
-to safely relocate files while automatically updating all links."
-
-Do NOT move files during /weave — directory reorganization is
-a separate step handled by `/organize`.
-
-### Step 8: Report
-
-After all changes are applied, provide a summary:
-
-```
-Weave complete:
-- Scanned: N files
-- Enriched: N files (frontmatter + wikilinks)
-- Wikilinks added: N
-- Permanent notes created: N
-- Split suggestions: N (pending user review)
-- Orphaned files (no links): N
-- Skipped: N non-markdown files
-- Backups: .byoao/backups/<timestamp>/
-```
-
-## Single File Mode
-
-When `file=` is provided, run the same process but only for that one file. Still read the vault map and check for cross-references, but skip Steps 5-6 (permanent note generation and split suggestions are batch operations).
-
-## Important Guidelines
-
-- **Be conservative**: When in doubt about a wikilink or frontmatter value, skip it. False positives degrade trust.
-- **Ask, don't assume**: Always present changes for user confirmation before applying.
-- **Preserve user content**: Never delete, rewrite, or reorganize existing text. Only add metadata and convert mentions to links.
-- **Domain inference**: Use existing note domains to infer the domain for new notes. Consistency matters.
-- **Idempotent**: Running /weave twice on the same file should not add duplicate wikilinks or frontmatter fields.
-- **Zettelkasten principle**: Favor atomicity. One idea per note. Suggest splits for multi-concept notes.

package/dist/tools/add-glossary-term.js

@@ -1,21 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { addGlossaryTerm } from "../vault/glossary.js";
-export const byoao_add_glossary_term = tool({
-    description: "Add a new term to the vault's Glossary.md. Appends a row to the Core Terms table.",
-    args: {
-        vaultPath: tool.schema.string().describe("Path to the Obsidian vault"),
-        term: tool.schema.string().describe("The domain term to add"),
-        definition: tool.schema.string().describe("Brief definition (1-2 sentences)"),
-        domain: tool.schema.string().optional().describe("Knowledge domain (e.g. analytics, infrastructure)"),
-    },
-    async execute(args) {
-        const result = await addGlossaryTerm({
-            vaultPath: args.vaultPath,
-            term: args.term,
-            definition: args.definition,
-            domain: args.domain ?? "",
-        });
-        return `✓ Added glossary term: ${result.termAdded}\n  File: ${result.glossaryPath}`;
-    },
-});
-//# sourceMappingURL=add-glossary-term.js.map

package/dist/tools/add-glossary-term.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"add-glossary-term.js","sourceRoot":"","sources":["../../src/tools/add-glossary-term.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAChD,OAAO,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAEvD,MAAM,CAAC,MAAM,uBAAuB,GAAG,IAAI,CAAC;IAC1C,WAAW,EACT,mFAAmF;IACrF,IAAI,EAAE;QACJ,SAAS,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,4BAA4B,CAAC;QACtE,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,wBAAwB,CAAC;QAC7D,UAAU,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,kCAAkC,CAAC;QAC7E,MAAM,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,mDAAmD,CAAC;KACtG;IACD,KAAK,CAAC,OAAO,CAAC,IAAI;QAChB,MAAM,MAAM,GAAG,MAAM,eAAe,CAAC;YACnC,SAAS,EAAE,IAAI,CAAC,SAAS;YACzB,IAAI,EAAE,IAAI,CAAC,IAAI;YACf,UAAU,EAAE,IAAI,CAAC,UAAU;YAC3B,MAAM,EAAE,IAAI,CAAC,MAAM,IAAI,EAAE;SAC1B,CAAC,CAAC;QAEH,OAAO,0BAA0B,MAAM,CAAC,SAAS,aAAa,MAAM,CAAC,YAAY,EAAE,CAAC;IACtF,CAAC;CACF,CAAC,CAAC"}

package/dist/tools/add-person.js

@@ -1,21 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { addMember } from "../vault/member.js";
-export const byoao_add_person = tool({
-    description: "Add a person note to an existing vault. Creates a person note in People/ and updates the team index and AGENTS.md wikilinks.",
-    args: {
-        vaultPath: tool.schema.string().describe("Path to the Obsidian vault"),
-        name: tool.schema.string().describe("Person's full name"),
-        role: tool.schema.string().optional().describe("Person's role/title"),
-        team: tool.schema.string().optional().describe("Team or KB name"),
-    },
-    async execute(args) {
-        const result = await addMember({
-            vaultPath: args.vaultPath,
-            name: args.name,
-            role: args.role || "",
-            team: args.team || "",
-        });
-        return `Added person: ${args.name}\n  File: ${result.filePath}\n  Wikilinks updated: ${result.wikilinksAdded}`;
-    },
-});
-//# sourceMappingURL=add-person.js.map

package/dist/tools/add-person.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"add-person.js","sourceRoot":"","sources":["../../src/tools/add-person.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAChD,OAAO,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AAE/C,MAAM,CAAC,MAAM,gBAAgB,GAAG,IAAI,CAAC;IACnC,WAAW,EACT,8HAA8H;IAChI,IAAI,EAAE;QACJ,SAAS,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,4BAA4B,CAAC;QACtE,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,oBAAoB,CAAC;QACzD,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,qBAAqB,CAAC;QACrE,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,iBAAiB,CAAC;KAClE;IACD,KAAK,CAAC,OAAO,CAAC,IAAI;QAChB,MAAM,MAAM,GAAG,MAAM,SAAS,CAAC;YAC7B,SAAS,EAAE,IAAI,CAAC,SAAS;YACzB,IAAI,EAAE,IAAI,CAAC,IAAI;YACf,IAAI,EAAE,IAAI,CAAC,IAAI,IAAI,EAAE;YACrB,IAAI,EAAE,IAAI,CAAC,IAAI,IAAI,EAAE;SACtB,CAAC,CAAC;QAEH,OAAO,iBAAiB,IAAI,CAAC,IAAI,aAAa,MAAM,CAAC,QAAQ,0BAA0B,MAAM,CAAC,cAAc,EAAE,CAAC;IACjH,CAAC;CACF,CAAC,CAAC"}

package/dist/tools/add-project.js

@@ -1,24 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { addProject } from "../vault/project.js";
-export const byoao_add_project = tool({
-    description: "Add a new project note to an existing vault. Creates a project note in Projects/ and updates the team index and AGENTS.md wikilinks.",
-    args: {
-        vaultPath: tool.schema.string().describe("Path to the Obsidian vault"),
-        name: tool.schema.string().describe("Project name"),
-        description: tool.schema
-            .string()
-            .optional()
-            .describe("One-line project description"),
-        team: tool.schema.string().optional().describe("Team name"),
-    },
-    async execute(args) {
-        const result = await addProject({
-            vaultPath: args.vaultPath,
-            name: args.name,
-            description: args.description || "",
-            team: args.team || "",
-        });
-        return `✓ Added project: ${args.name}\n  File: ${result.filePath}\n  Wikilinks updated: ${result.wikilinksAdded}`;
-    },
-});
-//# sourceMappingURL=add-project.js.map

package/dist/tools/add-project.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"add-project.js","sourceRoot":"","sources":["../../src/tools/add-project.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAChD,OAAO,EAAE,UAAU,EAAE,MAAM,qBAAqB,CAAC;AAEjD,MAAM,CAAC,MAAM,iBAAiB,GAAG,IAAI,CAAC;IACpC,WAAW,EACT,sIAAsI;IACxI,IAAI,EAAE;QACJ,SAAS,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,4BAA4B,CAAC;QACtE,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,cAAc,CAAC;QACnD,WAAW,EAAE,IAAI,CAAC,MAAM;aACrB,MAAM,EAAE;aACR,QAAQ,EAAE;aACV,QAAQ,CAAC,8BAA8B,CAAC;QAC3C,IAAI,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,EAAE,CAAC,QAAQ,CAAC,WAAW,CAAC;KAC5D;IACD,KAAK,CAAC,OAAO,CAAC,IAAI;QAChB,MAAM,MAAM,GAAG,MAAM,UAAU,CAAC;YAC9B,SAAS,EAAE,IAAI,CAAC,SAAS;YACzB,IAAI,EAAE,IAAI,CAAC,IAAI;YACf,WAAW,EAAE,IAAI,CAAC,WAAW,IAAI,EAAE;YACnC,IAAI,EAAE,IAAI,CAAC,IAAI,IAAI,EAAE;SACtB,CAAC,CAAC;QAEH,OAAO,oBAAoB,IAAI,CAAC,IAAI,aAAa,MAAM,CAAC,QAAQ,0BAA0B,MAAM,CAAC,cAAc,EAAE,CAAC;IACpH,CAAC;CACF,CAAC,CAAC"}

package/dist/tools/graph-health.js

@@ -1,25 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { getGraphHealth } from "../vault/graph-health.js";
-export const byoao_graph_health = tool({
-    description: "Diagnose Obsidian vault graph health — find orphan notes (no links in or out), unresolved links (broken wikilinks), and dead-end notes. Uses Obsidian CLI for vault-aware analysis.",
-    args: {
-        vaultPath: tool.schema.string().describe("Absolute path to the Obsidian vault"),
-        check: tool.schema
-            .enum(["all", "orphans", "unresolved", "deadends"])
-            .optional()
-            .describe("Which check to run: 'all' (default), 'orphans', 'unresolved', or 'deadends'"),
-        limit: tool.schema
-            .number()
-            .optional()
-            .describe("Maximum number of results to return (default: 20)"),
-    },
-    async execute(args) {
-        const result = await getGraphHealth({
-            vaultPath: args.vaultPath,
-            check: args.check,
-            limit: args.limit,
-        });
-        return JSON.stringify(result, null, 2);
-    },
-});
-//# sourceMappingURL=graph-health.js.map

package/dist/tools/graph-health.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"graph-health.js","sourceRoot":"","sources":["../../src/tools/graph-health.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAChD,OAAO,EAAE,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAE1D,MAAM,CAAC,MAAM,kBAAkB,GAAG,IAAI,CAAC;IACrC,WAAW,EACT,qLAAqL;IACvL,IAAI,EAAE;QACJ,SAAS,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qCAAqC,CAAC;QAC/E,KAAK,EAAE,IAAI,CAAC,MAAM;aACf,IAAI,CAAC,CAAC,KAAK,EAAE,SAAS,EAAE,YAAY,EAAE,UAAU,CAAC,CAAC;aAClD,QAAQ,EAAE;aACV,QAAQ,CACP,6EAA6E,CAC9E;QACH,KAAK,EAAE,IAAI,CAAC,MAAM;aACf,MAAM,EAAE;aACR,QAAQ,EAAE;aACV,QAAQ,CAAC,mDAAmD,CAAC;KACjE;IACD,KAAK,CAAC,OAAO,CAAC,IAAI;QAChB,MAAM,MAAM,GAAG,MAAM,cAAc,CAAC;YAClC,SAAS,EAAE,IAAI,CAAC,SAAS;YACzB,KAAK,EAAE,IAAI,CAAC,KAAkE;YAC9E,KAAK,EAAE,IAAI,CAAC,KAAK;SAClB,CAAC,CAAC;QACH,OAAO,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IACzC,CAAC;CACF,CAAC,CAAC"}

package/dist/tools/note-read.js

@@ -1,19 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { readNote } from "../vault/note-read.js";
-export const byoao_note_read = tool({
-    description: "Read a specific note from an Obsidian vault by name. Uses Obsidian CLI to resolve and read the note. Preferred over cat/Read for Obsidian vault notes.",
-    args: {
-        vaultPath: tool.schema.string().describe("Absolute path to the Obsidian vault"),
-        file: tool.schema
-            .string()
-            .describe("Note name to read (without .md extension, e.g. 'Refund Automation')"),
-    },
-    async execute(args) {
-        const result = await readNote({
-            vaultPath: args.vaultPath,
-            file: args.file,
-        });
-        return JSON.stringify(result, null, 2);
-    },
-});
-//# sourceMappingURL=note-read.js.map

package/dist/tools/note-read.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"note-read.js","sourceRoot":"","sources":["../../src/tools/note-read.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,0BAA0B,CAAC;AAChD,OAAO,EAAE,QAAQ,EAAE,MAAM,uBAAuB,CAAC;AAEjD,MAAM,CAAC,MAAM,eAAe,GAAG,IAAI,CAAC;IAClC,WAAW,EACT,wJAAwJ;IAC1J,IAAI,EAAE;QACJ,SAAS,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,qCAAqC,CAAC;QAC/E,IAAI,EAAE,IAAI,CAAC,MAAM;aACd,MAAM,EAAE;aACR,QAAQ,CAAC,qEAAqE,CAAC;KACnF;IACD,KAAK,CAAC,OAAO,CAAC,IAAI;QAChB,MAAM,MAAM,GAAG,MAAM,QAAQ,CAAC;YAC5B,SAAS,EAAE,IAAI,CAAC,SAAS;YACzB,IAAI,EAAE,IAAI,CAAC,IAAI;SAChB,CAAC,CAAC;QACH,OAAO,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;IACzC,CAAC;CACF,CAAC,CAAC"}

package/dist/tools/search-vault.js

@@ -1,22 +0,0 @@
-import { tool } from "@opencode-ai/plugin/tool";
-import { searchVault } from "../vault/search-vault.js";
-export const byoao_search_vault = tool({
-    description: "Search an Obsidian vault for notes matching a text query. Uses Obsidian CLI search:context for vault-aware results. Preferred over grep/rg for Obsidian vault knowledge queries about notes, tags, and content.",
-    args: {
-        vaultPath: tool.schema.string().describe("Absolute path to the Obsidian vault"),
-        query: tool.schema.string().describe("Text query to search for in vault notes"),
-        limit: tool.schema
-            .number()
-            .optional()
-            .describe("Maximum number of results to return (default: 20)"),
-    },
-    async execute(args) {
-        const result = await searchVault({
-            vaultPath: args.vaultPath,
-            query: args.query,
-            limit: args.limit,
-        });
-        return JSON.stringify(result, null, 2);
-    },
-});
-//# sourceMappingURL=search-vault.js.map