feat(framework): resolve resources shipped with installed plugins
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 15/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Start with plugins/aidd-context/skills/02-project-memory/actions/04-sync.md, where the relative hooks/update_memory.js call assumes the consumer working directory, then read Draft PR #979's standalone rule writer for how it resolves a script beside the loaded skill. The maintainer has not chosen the architectural boundary (CLI, plugin metadata, or host integration), so agree that first. Done means a documented resolution contract with tests for supported installation modes and the failure cases listed in the acceptance criteria.
由索引模型根據 Issue 內容生成。
描述
Problem to solve
A skill cannot reliably locate a resource shipped with its plugin across installation modes and hosts.
This surfaced in project-memory sync: the skill invoked node hooks/update_memory.js --check from the consumer project, although the script belongs to the installed plugin. This relative invocation incorrectly assumes that the plugin's hook is available under the consumer project's working directory. Marketplace caches, managed installs, and flat layouts can place plugin files elsewhere.
Draft PR #992 handles the immediate workflow with explicit manual sync instructions. Those instructions do not claim the executable hook’s protections against hard links or path substitution. A general resource lookup contract remains useful to other skills and plugin resources.
Proposed solution
Define a documented way for a skill or other plugin component to request a plugin-owned resource by plugin identity and source-relative path. It should return a verified installed resource or an explicit unsupported, missing, or ambiguous result.
Leave the architectural boundary open for maintainer input: the contract may involve the CLI, plugin metadata, host integration, or a combination. A CLI command is one option, but it may not cover host-managed installs where the CLI or its provenance is unavailable.
Additional context
Acceptance criteria
- Document the supported installation modes and how plugin-owned resources are located in each.
- Require resource resolution only for installation modes where trustworthy installation provenance or origin can be established. Modes without that evidence must fail explicitly rather than guess.
- For managed installs, use recorded source-to-installed-path provenance where it exists; do not reconstruct historical destinations from current profile settings.
- Resolve resources when invoked from a consumer project outside the framework source tree. Never treat the consumer project root as the plugin root.
- Reject absolute paths, traversal, or symlink resolution that escapes the selected plugin resource boundary.
- Do not execute the target or write to the project as a side effect of resolving it.
- Define explicit behavior for missing resources, incomplete or stale provenance, absent CLI, standalone skills, multiple installed versions, and shared destinations. Ambiguous contexts must fail explicitly rather than guess.
- Cover supported host and installation combinations, plus failure and boundary cases, with reproducible tests.
- Keep resource location distinct from execution-time filesystem safety; resolution alone must not weaken existing hook protections or claim equivalent guarantees.
Prior art in this repo
04-sync.md— the workflow where the working-directory assumption surfaced; Draft PR #992 replaces the immediate invocation.- #914 — Kilo-native generation, where the issue surfaced; this proposal is a separate framework capability.
- #698 and PR #706 — hook delivery and host-specific plugin-root tokens. These address hook installation and hook command paths, not a general way for a skill to locate plugin resources.
- #859 — global installation and distribution concerns. It is closed; its maintainer conclusion assigns host-specific installation surfaces to their owning integrations. It does not define a resource lookup contract.
- PR #778 — documents the boundary between event hooks and capabilities invoked by a person or skill; it does not resolve installed resource paths.
- Draft PR #979 — its standalone rule writer resolves its own script beside the loaded skill. That is relevant precedent, but not a general contract across resource types, installation origins, and versions.
Out of scope
- Expanding Kilo generation in #914 or changing Draft PR #992.
- Adding another rule writer alongside Draft PR #979.
- Hard-coding host-specific directories into generic skills.
- Promising support for every host-managed marketplace without evidence.
- Treating path resolution as proof that later script execution is race-safe.
- Requiring a full architecture redesign before the supported cases are established.
- 主要語言
- TypeScript
- 星號
- 481
- 分支
- 45
- 平均合併
- 1 天 13 小時
- 30 天內合併 PR
- 91
環境準備
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
ai-driven-dev/framework 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 86/100
ai-driven-dev/framework#1311 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 79/100
ai-driven-dev/framework#1244 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
ai-driven-dev/framework#1197 ·
維護者通常 1 天內回覆
-
refactor(aidd-context): apply the new skill template to learn可能已有人在做 @blafourcade 於 3 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
ai-driven-dev/framework#1186 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
ai-driven-dev/framework#1163 · 1 則留言 ·
維護者通常 1 天內回覆
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
難度 1/5 1-3 小時 新手友好度 87/100
維護者通常 1 天內回覆
-
🛠️ dette technique
難度 2/5 1-3 小時 新手友好度 61/100
betagouv/mon-entreprise#4752 · 1 則留言 ·
維護者通常 5 天內回覆
-
type: bug
難度 2/5 1-3 小時 新手友好度 67/100
franciscoBSalgueiro/en-croissant#1111 ·
維護者通常 2 天內回覆
-
area/providers type/feature version/v2
難度 2/5 1-3 小時 新手友好度 68/100
anomalyco/opencode#64845 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆