@goondocks/myco 0.14.4 → 0.15.1

package/dist/{setup-llm-G5UG5N3T.js → setup-llm-C3IGFLRN.js}

@@ -2,25 +2,25 @@ import { createRequire as __cr } from 'node:module'; const require = __cr(import
 import {
   withEmbedding
 } from "./chunk-SODRR3HE.js";
-import "./chunk-BCKYVLUZ.js";
+import "./chunk-6GG2IVNV.js";
 import {
   parseStringFlag
 } from "./chunk-SAKJMNSR.js";
-import "./chunk-TNCBMGWB.js";
+import "./chunk-X5IXK5KO.js";
 import "./chunk-HHZ3RTEI.js";
 import {
   loadConfig,
   updateConfig
-} from "./chunk-PSYLKCWQ.js";
+} from "./chunk-4BQ5QE76.js";
 import "./chunk-MYX5NCRH.js";
-import "./chunk-UZ5Y6XMP.js";
-import "./chunk-TFBAV3PV.js";
+import "./chunk-4O3QNM5I.js";
+import "./chunk-BFM6AM6R.js";
 import "./chunk-LPUQPDC2.js";
 import "./chunk-TRA3R4EC.js";
-import "./chunk-S6I62FAH.js";
+import "./chunk-CUADDHHU.js";
 import "./chunk-D7TYRPRM.js";
 import "./chunk-E4VLWIJC.js";
-import "./chunk-KH64DHOY.js";
+import "./chunk-GDY63YAW.js";
 import "./chunk-PZUWP5VK.js";
 
 // src/cli/setup-llm.ts
@@ -79,4 +79,4 @@ async function run(args, vaultDir) {
 export {
   run
 };
-//# sourceMappingURL=setup-llm-G5UG5N3T.js.map
+//# sourceMappingURL=setup-llm-C3IGFLRN.js.map

package/dist/src/agent/definitions/tasks/full-intelligence.yaml

@@ -17,7 +17,7 @@ description: >
   regenerates digest extracts.
 agent: myco-agent
 isDefault: true
-maxTurns: 130
+maxTurns: 150
 timeoutSeconds: 1800
 model: claude-sonnet-4-6
 
@@ -77,6 +77,7 @@ phases:
       - vault_report
     maxTurns: 6
     required: true
+    readOnly: true
 
   - name: extract
     dependsOn: [read-state]
@@ -235,7 +236,7 @@ phases:
       - vault_create_spore
       - vault_resolve_spore
       - vault_report
-    maxTurns: 22
+    maxTurns: 25
     required: false
 
   - name: graph
@@ -293,7 +294,7 @@ phases:
       - vault_create_entity
       - vault_create_edge
       - vault_report
-    maxTurns: 25
+    maxTurns: 35
     required: false
 
   # ---- Digest: assess + 3 parallel tier writes ----
@@ -362,7 +363,7 @@ phases:
       - vault_search_semantic
       - vault_read_digest
       - vault_report
-    maxTurns: 8
+    maxTurns: 10
     required: true
 
   - name: digest-10000
@@ -394,7 +395,7 @@ phases:
       - vault_read_digest
       - vault_write_digest
       - vault_report
-    maxTurns: 7
+    maxTurns: 9
     required: false
 
   - name: digest-5000
@@ -425,7 +426,7 @@ phases:
       - vault_read_digest
       - vault_write_digest
       - vault_report
-    maxTurns: 5
+    maxTurns: 7
     required: false
 
   - name: digest-1500
@@ -456,7 +457,7 @@ phases:
       - vault_read_digest
       - vault_write_digest
       - vault_report
-    maxTurns: 3
+    maxTurns: 5
     required: false
 
   - name: report

package/dist/src/agent/definitions/tasks/skill-evolve.yaml

@@ -2,106 +2,66 @@ name: skill-evolve
 displayName: Skill Evolution
 description: >-
   Evaluate and evolve existing Myco-managed skills based on new
-  vault knowledge and usage patterns.
+  vault knowledge. Only assesses skills with new knowledge since
+  their last assessment, throttled to once per assess_interval_hours.
 agent: myco-agent
 prompt: >-
-  Assess all active Myco-managed skills for staleness, conflicts,
-  and oversized scope. Evolve skills that need it.
+  Assess and update skills that have new knowledge since their last
+  assessment. The instruction contains pre-filtered skills with their
+  current content and new spore IDs.
 isDefault: false
 model: claude-sonnet-4-6
-maxTurns: 60
-timeoutSeconds: 1800
+maxTurns: 40
+timeoutSeconds: 1200
 schedule:
   enabled: false
   intervalSeconds: 900
   runIn:
     - idle
   preCondition: has-active-skills
+params:
+  assess_interval_hours: 24
+  max_skills_per_run: 5
 phases:
   - name: assess
     prompt: |
-      Evaluate every active Myco-managed skill to determine if it
-      needs updating.
-
-      For EACH active skill (vault_skill_records action: list, status: active):
-
-      1. READ THE CURRENT SKILL CONTENT.
-         Get the skill record (vault_skill_records action: get), then
-         read the latest lineage entry's content_snapshot to see what
-         the skill currently says. You MUST read the actual content
-         before you can assess accuracy.
-
-      2. SEARCH FOR NEW KNOWLEDGE since the skill was last updated.
-         Use vault_search_semantic with the skill's topic/keywords.
-         Use vault_search_fts with specific file paths, function names,
-         and technical terms mentioned in the skill.
-         Use vault_spores to check for recent wisdom, decisions, and
-         gotchas related to the skill's domain.
-
-         Compare what you find to what the skill currently says.
-         Does the skill miss anything important? Does it say anything
-         that's now wrong or outdated?
-
-      3. CHECK SOURCE SPORE STATUS.
-         For each source spore ID in the skill's source_ids, check if
-         it's been superseded (vault_spores, status: superseded).
-         Superseded sources mean the skill may contain outdated advice.
-
-      4. ASSESS SKILL SCOPE.
-         Is the skill trying to cover too many distinct procedures?
-         A skill over 400 lines or covering 3+ independent workflows
-         is a candidate for splitting.
-
-      Classify each skill — bias toward CURRENT. A rewrite has
-      real cost (can lose valuable detail, regress triggering quality).
-      Only classify as STALE/CONFLICTED when the delta is substantive:
-
-      - **CURRENT**: Content is still accurate. Minor phrasing
-        differences between the skill and new knowledge do NOT make
-        it stale. If the skill already covers the topic correctly
-        — even if newer spores phrase it differently — it is CURRENT.
-      - **STALE**: New *factual* knowledge exists that the skill
-        genuinely misses — a new concrete step, a changed file path,
-        a new gotcha that would cause real failure, a new pattern
-        that replaces one the skill teaches. The new knowledge must
-        be specific and actionable, not a rephrasing of existing
-        content. Note specifically WHAT is new/changed.
-      - **CONFLICTED**: New knowledge directly contradicts the skill's
-        current content (a decision was reversed, a pattern was
-        abandoned, a file was deleted). Note the contradiction.
-      - **OVERSIZED**: Covers too many distinct procedures. Note
-        how it should be split.
-
-      When in doubt, classify as CURRENT. A skill that is 90%
-      accurate and well-structured is better left alone than
-      rewritten with the risk of losing detail.
-
-      NOTE: Skip usage-based retirement for now — usage tracking is
-      not yet active. Do not classify skills as UNUSED.
-
-      Store classifications using vault_set_state with key
-      'skill-evolve-classifications' and value as a JSON object:
-      ```json
-      {
-        "skill-name": {
-          "classification": "CURRENT|STALE|CONFLICTED|OVERSIZED",
-          "rationale": "what changed and why",
-          "new_knowledge": ["list of specific new findings"]
-        }
-      }
-      ```
-
-      Report classifications via vault_report.
+      The instruction contains skills that have new knowledge since
+      their last assessment. For each skill listed:
+
+      1. Read the new spores: fetch each ID from new_spore_ids via
+         vault_spores. Understand what changed.
+
+      2. Verify code references: use vault_search_fts to check 3-5
+         key file paths and function names from the skill content.
+         Are they still valid? This is bounded — check specific
+         claims, do not search broadly.
+
+      3. Classify:
+         - CURRENT — new knowledge doesn't affect this skill's procedures
+         - STALE — new knowledge changes a specific step, path, or gotcha.
+           Note exactly WHAT is new.
+         - DEPRECATED — key code references are gone or the procedure
+           is no longer relevant. Note what's missing.
+
+      Bias toward CURRENT. A skill that is 90% accurate is better
+      left alone than rewritten with the risk of losing detail.
+
+      4. Update the skill's properties with the new watermark:
+         vault_skill_records (action: update, id: <skill_id>,
+         properties: '{"last_assessed_at": <now>, "knowledge_watermark": <now>, "last_classification": "<classification>"}')
+
+      5. Store classifications via vault_set_state
+         (key: skill-evolve-classifications) as JSON.
+
+      Report via vault_report.
+
+      If the instruction says "No skills need assessment", report
+      skip via vault_report and finish immediately.
     tools:
-      - vault_skill_records
       - vault_spores
-      - vault_sessions
       - vault_search_fts
-      - vault_search_semantic
-      - vault_read_digest
-      - vault_state
+      - vault_skill_records
       - vault_set_state
-      - vault_edges
       - vault_report
     maxTurns: 20
     required: true
@@ -111,77 +71,44 @@ phases:
       Read classifications from vault_state
       (key: skill-evolve-classifications). Parse the JSON.
 
-      For each skill classified as STALE, CONFLICTED, or OVERSIZED:
+      For each skill classified as STALE or DEPRECATED:
 
-      ## STALE or CONFLICTED — Rewrite the skill
+      ## STALE — Targeted update
 
       1. Read the current skill content from vault_skill_records
-         (action: get) to see the current version.
-
-      2. Gather the new knowledge: read the specific spores, sessions,
-         or search results identified in the assessment.
-
-      3. Rewrite using vault_write_skill. The rewrite MUST:
-         - Preserve ALL existing frontmatter fields — read the current
-           content first and carry every field forward (name, description,
-           managed_by, user-invocable, allowed-tools). The quality gate
-           rejects writes missing any required frontmatter field.
-
-         - **DO NOT shorten the description.** The description is the
-           PRIMARY triggering mechanism — Claude Code reads it to decide
-           whether to load the skill. A shorter description means fewer
-           matches and worse triggering. Only change the description if
-           it contains factually wrong information. Never condense it
-           for brevity.
-
-         - **allowed-tools must list Claude Code tool names**, NOT vault
-           agent tools. These skills run in developer Claude Code sessions,
-           not in the agent pipeline. Valid values are:
-           Read, Edit, Write, Bash, Grep, Glob
-           If the existing allowed-tools lists vault_* tools (like
-           vault_search_fts, vault_spores, vault_state, etc.), that is
-           WRONG — replace with the appropriate Claude Code tools.
-           Most procedural skills need: Read, Edit, Write, Bash, Grep, Glob
-           Read-only informational skills need: Read, Bash, Grep, Glob
-
-         - Preserve all content that is still accurate — do NOT
-           restructure or rephrase sections that are correct. Only
-           modify the specific sections affected by the new knowledge.
-         - Incorporate the new knowledge identified in assessment
-         - Follow the same SKILL.md format:
-           - Prerequisites, Steps, Common Pitfalls structure
-         - Stay under 500 lines
-         - Include a rationale parameter explaining WHAT changed:
-           e.g., "Updated: added hookFields normalization step from
-           session dd5bc83a, corrected Windsurf MCP path"
-
-         vault_write_skill automatically bumps the generation and
-         creates a lineage entry with the rationale.
-
-      ## OVERSIZED — Split into focused sub-skills
-
-      1. Identify distinct procedures within the skill.
-      2. Write each as a new skill via vault_write_skill.
-         Each sub-skill gets its own name, description, and content.
-      3. Retire the parent via vault_skill_records
-         (action: update, status: retired).
-
-      ## CURRENT — No action needed. Skip.
-
-      Report a summary of all actions taken via vault_report:
-      - Which skills were updated (with rationale)
-      - Which skills were split (into what)
-      - Which skills were left as CURRENT
+         (action: get).
+
+      2. START from the existing content as-is. Copy it verbatim.
+         Then make ONLY the specific changes needed — insert new
+         sections, update incorrect facts, add missing steps.
+
+         The diff between old and new should be MINIMAL.
+
+         Protected frontmatter rules (vault_write_skill enforces
+         these and will REJECT writes that violate them):
+         - user-invocable: copy EXACT value from existing skill
+         - allowed-tools: copy EXACT value from existing skill
+         - description: do not shorten (>10% reduction is rejected)
+
+      3. Write via vault_write_skill with a rationale explaining
+         what specifically changed.
+
+      ## DEPRECATED — Retire the skill
+
+      1. vault_skill_records (action: update, status: retired)
+      2. vault_skill_records (action: delete)
+
+      ## CURRENT — No action. Skip.
+
+      Report all actions via vault_report.
     tools:
       - vault_write_skill
       - vault_skill_records
       - vault_skill_candidates
       - vault_state
-      - vault_spores
       - vault_search_fts
-      - vault_search_semantic
       - vault_report
-    maxTurns: 35
+    maxTurns: 20
     required: true
     dependsOn:
       - assess

package/dist/src/agent/definitions/tasks/skill-generate.yaml

@@ -6,11 +6,11 @@ description: >-
 agent: myco-agent
 prompt: >-
   Generate ONE project-specific skill from the next approved candidate.
-  Process only the first approved candidate found — do not batch multiple
-  skills in a single run. The schedule will pick up the next one.
+  The instruction contains the candidate metadata and pre-assembled
+  source material. Write the skill, then validate it.
 isDefault: false
 model: claude-sonnet-4-6
-maxTurns: 35
+maxTurns: 30
 timeoutSeconds: 900
 schedule:
   enabled: false
@@ -19,62 +19,12 @@ schedule:
     - idle
   preCondition: has-approved-candidates
 phases:
-  - name: gather
-    prompt: |
-      You are generating ONE skill. Find the first approved candidate
-      that doesn't have a skill yet.
-
-      If an instruction provides a candidate ID, use that specific one.
-      Otherwise, use vault_skill_candidates (action: list, status: approved)
-      and pick the FIRST result. Process ONLY that one candidate —
-      do not attempt to generate multiple skills in this run.
-
-      Read the candidate. If its skill_id is set or status is 'generated',
-      it already has a skill — report "already generated" and STOP.
-      Do NOT skip based on similar topics. The user approved it.
-
-      If no skill exists, gather ALL source material for this candidate:
-
-      1. Read each source item referenced in the candidate's source_ids.
-         Use vault_spores to fetch spore IDs, vault_sessions to fetch
-         session IDs. These contain the detailed knowledge.
-
-      2. Search for additional context using vault_search_semantic with
-         the candidate's topic as the query. This may surface plans,
-         artifacts, and sessions not in the source_ids.
-
-      3. Search vault_search_fts for specific file paths, function names,
-         or config keys mentioned in the source material.
-
-      4. Check vault_entities for related entities — these often link
-         to additional spores via edges.
-
-      For each source, extract:
-      - Concrete steps (what to do, in what order)
-      - File paths and code patterns (specific to this project)
-      - Gotchas and pitfalls (things that went wrong)
-      - Decisions and rationale (why this approach, not another)
-      - Prerequisites (what must be true before starting)
-
-      Be thorough — the skill quality depends entirely on how much
-      concrete detail you gather here.
-    tools:
-      - vault_skill_candidates
-      - vault_spores
-      - vault_sessions
-      - vault_search_fts
-      - vault_search_semantic
-      - vault_read_digest
-      - vault_entities
-      - vault_edges
-    maxTurns: 10
-    required: true
-
   - name: draft
     prompt: |
-      Write a SKILL.md from the gathered material. The skill must be a
-      procedural how-to guide that teaches an agent how to accomplish
-      a specific task in THIS project.
+      Write a SKILL.md from the source material in the instruction.
+      The instruction contains the candidate ID, topic, rationale,
+      and the full text of each source spore and session. Do NOT
+      call any search or read tools — the material is already here.
 
       ## SKILL.md Format
 
@@ -151,16 +101,14 @@ phases:
       - display_name: human-readable title
       - description: the frontmatter description text
       - content: the full SKILL.md including frontmatter
-      - candidate_id: the candidate ID from the gather phase
-      - source_ids: JSON array of source item IDs used
+      - candidate_id: the candidate ID from the instruction
+      - source_ids: JSON array of source item IDs from the instruction
       - rationale: "Initial generation from candidate survey"
     tools:
       - vault_write_skill
       - vault_skill_records
     maxTurns: 10
     required: true
-    dependsOn:
-      - gather
 
   - name: validate
     prompt: |
@@ -209,7 +157,7 @@ phases:
       - vault_spores
       - vault_search_fts
       - vault_report
-    maxTurns: 8
+    maxTurns: 15
     required: true
     dependsOn:
       - draft