From bca2a58e36277a1c2cad7ae91642488b75305be6 Mon Sep 17 00:00:00 2001 From: gsxdsm Date: Tue, 14 Apr 2026 08:42:10 -0700 Subject: [PATCH] docs(FN-1513): update memory with skill resolver diagnostics distinction - Document excludedSkillPaths tracking for disabled skills - Document the three-case diagnostic distinction (allowed/disabled/missing) - Note the console.error logging pattern for diagnostics --- .fusion/memory.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.fusion/memory.md b/.fusion/memory.md index aafa6fb08..6499ed8aa 100644 --- a/.fusion/memory.md +++ b/.fusion/memory.md @@ -1023,6 +1023,12 @@ The skill selection resolver (`packages/engine/src/skill-resolver.ts`) computes - `filterActive: false` means no filtering (all discovered skills pass through); `filterActive: true` means filtering is active - `createSkillsOverrideFromSelection()` returns the `skillsOverride` callback for `DefaultResourceLoader` - `skillsOverride` is only set when `skillSelection` is provided in `AgentOptions`; omitting it preserves existing behavior +- `SkillSelectionResult` includes `excludedSkillPaths` to track skills explicitly disabled by `-` patterns +- Filtering distinguishes three cases: + 1. **Allowed skills**: skills matching `allowedSkillPaths` pass through + 2. **Disabled skills**: skills matching `excludedSkillPaths` are filtered out and produce warnings + 3. **Missing skills**: configured paths not matching any discovered skill produce warnings +- The `createSkillsOverrideFromSelection` callback filters skills and produces diagnostic messages via `console.error` with `[pi] [skills]` prefix **Settings format:** ```json