@codemcp/ade 0.7.0 → 0.8.0

package/.beads/issues.jsonl

@@ -6,6 +6,32 @@
 {"id":"ade-1.3","title":"Fix","description":"Implement the solution based on your analysis:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user  Before implementing, assess the approach: - How critical is this system? What is the blast radius if the fix causes issues? - Should this be a minimal fix or a more comprehensive solution?  Make targeted changes that address the root cause without introducing new issues. Be careful to maintain existing functionality while fixing the bug.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:27:27.697356+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:27:27.697356+01:00","dependencies":[{"issue_id":"ade-1.3","depends_on_id":"ade-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-1.3","depends_on_id":"ade-1.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-1.4","title":"Verify","description":"Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced. Run existing tests, create new ones if needed, and verify the solution is robust.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:27:27.865128+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:27:27.865128+01:00","dependencies":[{"issue_id":"ade-1.4","depends_on_id":"ade-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-1.4","depends_on_id":"ade-1.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-1.5","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review.  **STEP 1: Code Cleanup** Systematically clean up development artifacts: - Remove all temporary debug output statements used during bug investigation (console logging, print statements, debug output functions) - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred - Remove completed TODOs and convert remaining ones to proper issue tracking if needed - Remove temporary debugging code, test code blocks, and commented-out code - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect the bug fix: - If  exists, update it if design details were refined or changed during the fix - Compare documentation against the actual bug fix implementation - Update only the documentation sections that have functional changes - Remove references to investigation iterations, progress notes, and temporary decisions - Ensure documentation describes the final fixed state, not the debugging process - Ask the user to review document updates  **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure bug fix is ready for production - Update task progress and mark completed work as you finalize the bug fix","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:27:28.031667+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:27:28.031667+01:00","dependencies":[{"issue_id":"ade-1.5","depends_on_id":"ade-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-1.5","depends_on_id":"ade-1.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-10","title":"ade: bugfix (development-plan-fix-docset-writing.md)","description":"Responsible vibe engineering session using bugfix workflow for ade","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:23.763416+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:23.763416+01:00"}
+{"id":"ade-10.1","title":"Reproduce","description":"Gather specific information to reliably reproduce the reported bug: - What are the exact OS, browser/runtime versions, and hardware specs? - What is the precise sequence of actions that trigger the bug? - What error messages, logs, or stack traces are available? - Does this happen every time or intermittently? - How many users are affected and what is the business impact?  Create test cases that demonstrate the problem. Document your findings and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:23.906213+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:23.906213+01:00","dependencies":[{"issue_id":"ade-10.1","depends_on_id":"ade-10","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-10.2","title":"Analyze","description":"Examine the code paths involved in the bug, identify the root cause, and understand why the issue occurs. Use debugging tools, add logging, and trace through the problematic code. Document your analysis and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:24.062362+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:24.062362+01:00","dependencies":[{"issue_id":"ade-10.2","depends_on_id":"ade-10","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-10.2","depends_on_id":"ade-10.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-10.3","title":"Fix","description":"Implement the solution based on your analysis:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user  Before implementing, assess the approach: - How critical is this system? What is the blast radius if the fix causes issues? - Should this be a minimal fix or a more comprehensive solution?  Make targeted changes that address the root cause without introducing new issues. Be careful to maintain existing functionality while fixing the bug.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:24.211424+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:24.211424+01:00","dependencies":[{"issue_id":"ade-10.3","depends_on_id":"ade-10","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-10.3","depends_on_id":"ade-10.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-10.4","title":"Verify","description":"Test the fix thoroughly to ensure the original bug is resolved and no new issues were introduced. Run existing tests, create new ones if needed, and verify the solution is robust.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:24.357+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:24.357+01:00","dependencies":[{"issue_id":"ade-10.4","depends_on_id":"ade-10","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-10.4","depends_on_id":"ade-10.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-10.5","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review.  **STEP 1: Code Cleanup** Systematically clean up development artifacts: - Remove all temporary debug output statements used during bug investigation (console logging, print statements, debug output functions) - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred - Remove completed TODOs and convert remaining ones to proper issue tracking if needed - Remove temporary debugging code, test code blocks, and commented-out code - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect the bug fix: - If  exists, update it if design details were refined or changed during the fix - Compare documentation against the actual bug fix implementation - Update only the documentation sections that have functional changes - Remove references to investigation iterations, progress notes, and temporary decisions - Ensure documentation describes the final fixed state, not the debugging process - Ask the user to review document updates  **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure bug fix is ready for production - Update task progress and mark completed work as you finalize the bug fix","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T14:32:24.515977+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T14:32:24.515977+01:00","dependencies":[{"issue_id":"ade-10.5","depends_on_id":"ade-10","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-10.5","depends_on_id":"ade-10.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11","title":"ade: epcc (development-plan-fix-docset-writing.md)","description":"Responsible vibe engineering session using epcc workflow for ade","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:24:52.604251+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:05:42.784077+01:00","closed_at":"2026-03-20T16:05:42.784077+01:00","close_reason":"Closed"}
+{"id":"ade-11.1","title":"Explore","description":"Research the codebase to understand existing patterns and gather context about the problem space.  - If uncertain about conventions or rules, ask the user about them - Read relevant files and documentation - If  exists: Understand and document requirements there - Otherwise: Document requirements in your task management system  Focus on understanding without writing code yet. Document your findings and create tasks as needed.","status":"closed","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:24:52.757158+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:26.864081+01:00","closed_at":"2026-03-20T16:01:26.864081+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.1","depends_on_id":"ade-11","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.2","title":"Plan","description":"Create a detailed implementation strategy based on your exploration:  - If  exists: Base your strategy on requirements from it - Otherwise: Use existing task context  Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges.  - If architectural changes needed and  exists: Document in  - Otherwise: Create tasks to track architectural decisions  - If  exists: Adhere to the design in it - Otherwise: Elaborate design options and present them to the user  Document the planning work thoroughly and create implementation tasks as part of the code phase as needed.","status":"closed","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:24:52.917633+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:26.996449+01:00","closed_at":"2026-03-20T16:01:26.996449+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.2","depends_on_id":"ade-11","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-11.2","depends_on_id":"ade-11.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3","title":"Code","description":"Follow your plan to build the solution:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user - If  exists: Build according to the architecture from it - Otherwise: Elaborate architectural options and present them to the user - If  exists: Ensure requirements from it are met - Otherwise: Ensure existing requirements are met based on your task context  Write clean, well-structured code with proper error handling. Prevent regression by building, linting, and executing existing tests. Stay flexible and adapt the plan as you learn more during implementation. Update task progress and create new tasks as needed.","status":"closed","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:24:53.084958+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:27.09839+01:00","closed_at":"2026-03-20T16:01:27.09839+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3","depends_on_id":"ade-11","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-11.3","depends_on_id":"ade-11.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.1","title":"types.ts: remove Option.docsets, excluded_docsets from UserConfig, add docset to ProvisionWriter","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.105878+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:13.66361+01:00","closed_at":"2026-03-20T16:01:13.66361+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.1","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.10","title":"catalog/catalog.spec.ts: replace .docsets assertions with recipe-entry assertions","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.43139+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.697048+01:00","closed_at":"2026-03-20T16:01:14.697048+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.10","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.11","title":"cli/setup.ts: remove docset confirmation multiselect block","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.575948+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.807776+01:00","closed_at":"2026-03-20T16:01:14.807776+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.11","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.12","title":"cli/setup.spec.ts: remove docset-related tests","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.720793+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.914569+01:00","closed_at":"2026-03-20T16:01:14.914569+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.12","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.13","title":"cli/knowledge.integration.spec.ts: remove excluded_docsets test","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.87583+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:15.018168+01:00","closed_at":"2026-03-20T16:01:15.018168+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.13","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.14","title":"cli/conventions.integration.spec.ts: remove docset multiselect mock calls","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:50.015271+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:15.119845+01:00","closed_at":"2026-03-20T16:01:15.119845+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.14","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.15","title":"Delete dead files: writers/knowledge.ts and knowledge.spec.ts","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:50.151331+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:13.53949+01:00","closed_at":"2026-03-20T16:01:13.53949+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.15","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.2","title":"writers/docset.ts: new docset provision writer","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.271995+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:13.783381+01:00","closed_at":"2026-03-20T16:01:13.783381+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.2","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.3","title":"writers/docset.spec.ts: unit tests for docset writer","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.410045+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:13.883732+01:00","closed_at":"2026-03-20T16:01:13.883732+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.3","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.4","title":"registry.ts: register docsetWriter","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.546387+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:13.996487+01:00","closed_at":"2026-03-20T16:01:13.996487+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.4","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.5","title":"index.ts: export docsetWriter, remove collectDocsets export","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.680198+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.103166+01:00","closed_at":"2026-03-20T16:01:14.103166+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.5","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.6","title":"resolver.ts: remove docset-collection loop, exclusion filtering, collectDocsets()","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.821344+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.209469+01:00","closed_at":"2026-03-20T16:01:14.209469+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.6","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.7","title":"resolver.spec.ts: update docsets fixtures to recipe entries, remove excluded_docsets tests","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:48.957283+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.316194+01:00","closed_at":"2026-03-20T16:01:14.316194+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.7","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.8","title":"catalog/facets/architecture.ts: replace docsets[] with recipe entries (3 options)","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.150947+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.449139+01:00","closed_at":"2026-03-20T16:01:14.449139+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.8","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.3.9","title":"catalog/facets/practices.ts: replace docsets[] with recipe entry (1 option)","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:45:49.294147+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:01:14.582911+01:00","closed_at":"2026-03-20T16:01:14.582911+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.3.9","depends_on_id":"ade-11.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-11.4","title":"Commit","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: 1. **Remove Debug Output**: Search for and remove all temporary debug output statements used during development.    Look for language-specific debug output methods (console logging, print statements, debug output functions).    Remove any debugging statements that were added for development purposes.  2. **Review TODO/FIXME Comments**:    - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred    - Remove completed TODOs    - Convert remaining TODOs to proper issue tracking if needed  3. **Remove Debugging Code Blocks**:    - Remove temporary debugging code, test code blocks, and commented-out code    - Clean up any experimental code that's no longer needed    - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect final implementation: 1. **Update Long-Term Memory Documents**: Based on what was actually implemented:    - If  exists: Update it if requirements changed during development    - If  exists: Update it if architectural impacts were identified    - If  exists: Update it if design details were refined or changed    - Otherwise: Document any changes in the plan file 2. **Compare Against Implementation**: Review documentation against actual implemented functionality 3. **Update Changed Sections**: Only modify documentation sections that have functional changes 4. **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions 5. **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process 6. **Ask User to Review Document Updates** **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure code is ready for production/delivery Update task progress and mark completed work as you finalize the feature.","status":"closed","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T15:24:53.248593+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T16:05:42.649754+01:00","closed_at":"2026-03-20T16:05:42.649754+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-11.4","depends_on_id":"ade-11","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-11.4","depends_on_id":"ade-11.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-2","title":"ade: epcc (development-plan-autonomy-facet.md)","description":"Responsible vibe engineering session using epcc workflow for ade","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:42:24.649306+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:42:24.649306+01:00"}
 {"id":"ade-2.1","title":"Explore","description":"Research the codebase to understand existing patterns and gather context about the problem space.  - If uncertain about conventions or rules, ask the user about them - Read relevant files and documentation - If  exists: Understand and document requirements there - Otherwise: Document requirements in your task management system  Focus on understanding without writing code yet. Document your findings and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:42:24.818903+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:42:24.818903+01:00","dependencies":[{"issue_id":"ade-2.1","depends_on_id":"ade-2","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-2.1.1","title":"Review existing behavior-oriented facets and catalog tests","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-18T08:46:07.923572+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-18T08:46:37.327782+01:00","closed_at":"2026-03-18T08:46:37.327782+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-2.1.1","depends_on_id":"ade-2.1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}

package/.beads/last-touched

@@ -1 +1 @@
-ade-9.3.6
+ade-11.3.15

package/.vibe/beads-state-ade-fix-docset-writing-37fuoj.json

@@ -0,0 +1,29 @@
+{
+  "conversationId": "ade-fix-docset-writing-37fuoj",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-11",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "ade-11.1"
+    },
+    {
+      "phaseId": "plan",
+      "phaseName": "Plan",
+      "taskId": "ade-11.2"
+    },
+    {
+      "phaseId": "code",
+      "phaseName": "Code",
+      "taskId": "ade-11.3"
+    },
+    {
+      "phaseId": "commit",
+      "phaseName": "Commit",
+      "taskId": "ade-11.4"
+    }
+  ],
+  "createdAt": "2026-03-20T14:24:53.678Z",
+  "updatedAt": "2026-03-20T14:24:53.678Z"
+}

package/.vibe/development-plan-fix-docset-writing.md

@@ -0,0 +1,77 @@
+# Development Plan: ade (fix-docset-writing branch)
+
+*Generated on 2026-03-20 by Vibe Feature MCP*
+*Workflow: [epcc](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/epcc)*
+
+## Goal
+
+Refactor: collapse `option.docsets[]` into a `docset` provision writer in the recipe.
+
+**Background:** Currently `Option` has two separate mechanisms for contributing to `knowledge_sources`:
+1. `recipe[]` entries with provision writers (skills, git-hooks, instruction, etc.)
+2. A separate `docsets?: DocsetDef[]` sibling field — with its own confirmation UI, per-item exclusion (`excluded_docsets`), and `collectDocsets()` helper
+
+The `docsets` field was kept separate to support per-docset user confirmation/exclusion. But this is inconsistent with how skills work — skills are presented as a bulk "install N skills?" prompt, not a per-skill multiselect. Docsets should follow the same pattern: a `docset` provision writer in the recipe that contributes to `knowledge_sources`, with a bulk defer prompt (matching skills), and no per-item exclusion UI.
+
+**Target design:**
+- `Option.docsets?: DocsetDef[]` → removed
+- new `docset` provision writer → pushes a `KnowledgeSource` to `knowledge_sources[]`
+- confirmation/exclusion multiselect in `setup.ts` → removed
+- `excluded_docsets` in `UserConfig` → removed
+- `collectDocsets()` → removed
+
+## Explore
+<!-- beads-phase-id: ade-11.1 -->
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Plan
+<!-- beads-phase-id: ade-11.2 -->
+
+### Phase Entrance Criteria
+- [ ] All usages of `docsets`, `collectDocsets`, `excluded_docsets` are catalogued
+- [ ] Scope and approach are clearly understood
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Code
+<!-- beads-phase-id: ade-11.3 -->
+
+### Phase Entrance Criteria
+- [ ] Plan is complete and agreed
+- [ ] New `docset` writer shape is defined
+- [ ] All affected files are identified
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Commit
+<!-- beads-phase-id: ade-11.4 -->
+
+### Phase Entrance Criteria
+- [ ] All tests pass
+- [ ] No references to `docsets`, `collectDocsets`, or `excluded_docsets` remain in production code
+
+### Tasks
+- [ ] Squash WIP commits: `git reset --soft <first commit of this branch>`. Then, create a conventional commit. In the message, first summarize the intentions and key decisions from the development plan. Then, add a brief summary of the key changes and their side effects and dependencies.
+
+*Tasks managed via `bd` CLI*
+
+## Key Decisions
+
+- `docsets` as a sibling field on `Option` exists solely to support per-item confirmation/exclusion — a UI concern, not a data model concern
+- Skills set the right precedent: bulk defer prompt, no per-item opt-out
+- The `docset` provision writer config shape should match `DocsetDef`: `{ id, label, origin, description }`
+- Mapping: writer config `id` → `KnowledgeSource.name`, `description` → `KnowledgeSource.description`, `origin` → `KnowledgeSource.origin`
+
+## Notes
+
+- Previous WIP commit on `fix-docset-writing`: removed `knowledge` writer, wired `installKnowledge` into setup/install
+- The `knowledge.ts` writer file still exists on disk (dead code) — can be deleted as part of this refactor
+
+---
+*This plan is maintained by the LLM and uses beads CLI for task management. Tool responses provide guidance on which bd commands to use for task management.*

package/.vibe/docs/architecture.md

@@ -0,0 +1,201 @@
+# ADE — System Architecture (C4 Model)
+
+## 1. System Context (C4 Level 1)
+
+### System Overview
+
+ADE (Agentic Development Environment) is a CLI tool that lets engineering teams declare _what_ their project needs for agentic development — workflow conventions, skills, knowledge sources, tools — and generates the correct agent-specific configuration files for whichever coding agent they use. It bridges the gap between a team's abstract preferences and the per-agent config formats each AI coding assistant requires.
+
+### Users and Personas
+
+- **Individual developer**: Runs `ade setup` once to configure a project, then `ade install` on subsequent machines or CI environments to reproduce the setup.
+- **Tech lead / platform team**: Authors a shared `ade.extensions.mjs` that encodes org-specific conventions (custom skills, internal docsets, proprietary harnesses) and distributes it via a template repository.
+- **CI/CD pipeline**: Calls `ade install` to ensure a reproducible agent environment before agentic tasks run.
+
+### External Systems
+
+- **`@codemcp/skills`**: Manages SKILL.md files and the skills lock file. ADE calls its programmatic API (`runAdd`) to install skills into the project.
+- **`@codemcp/knowledge`**: Manages `.knowledge/config.yaml` and docset artifacts. ADE calls `createDocset` + `initDocset` to register and download knowledge sources.
+- **`@codemcp/workflows-server`** (and other MCP servers): Runtime servers registered as MCP server entries in the generated agent config. ADE writes the config; it does not start or manage these servers.
+- **Coding agents** (Claude Code, OpenCode, Copilot, Cursor, Kiro, etc.): Consumers of ADE's generated config files. Each has its own format; ADE's harness writers know the details.
+- **Skills server** (e.g. `mrsimpson/skills-coding`): External source for skill definitions referenced in catalog options.
+
+### System Boundaries
+
+- **Inside ADE**: Catalog, resolver, provision writers, harness writers, CLI TUI, lock file management, skills installer, knowledge installer.
+- **Outside ADE**: Runtime MCP servers, agent execution, skill content authoring, docset content management, the agents themselves.
+
+### Context Diagram
+
+```
+┌─────────────────────────────────────────────────────────┐
+│                        Developer                        │
+└─────────────────────────┬───────────────────────────────┘
+                          │ ade setup / ade install
+┌─────────────────────────▼───────────────────────────────┐
+│                   ADE CLI (@codemcp/ade)                 │
+│  Interactive TUI + resolver + file generators           │
+└──────┬──────────────────┬──────────────────┬────────────┘
+       │ programmatic API │                  │ writes config files
+       ▼                  ▼                  ▼
+@codemcp/skills   @codemcp/knowledge   Agent config files
+(skills lock,     (.knowledge/         (AGENTS.md,
+ SKILL.md files)   config.yaml,         .mcp.json,
+                   docset artifacts)    opencode.json, …)
+```
+
+---
+
+## 2. Container Architecture (C4 Level 2)
+
+### Containers
+
+#### `@codemcp/ade-core` (`packages/core`)
+
+- **Technology**: TypeScript, pure functions, no I/O except config file reads/writes
+- **Responsibilities**: All types, catalog definitions, resolution logic, provision writers, writer registry
+- **Interfaces**: Public TypeScript API (`index.ts`) — exported types, `resolve()`, `createDefaultRegistry()`, `mergeExtensions()`, catalog accessors, config read/write utilities
+- **Data storage**: None at runtime; reads/writes `config.yaml` and `config.lock.yaml` via helper functions
+
+#### `@codemcp/ade-cli` (`packages/cli`)
+
+- **Technology**: TypeScript, `@clack/prompts` for TUI, `tsup` bundle
+- **Responsibilities**: Argument parsing, interactive TUI, extensions loading, skills installation, knowledge installation, command routing
+- **Interfaces**: CLI binary (`ade setup [dir]`, `ade install [dir]`); programmatic entry points `runSetup()` and `runInstall()` (used in tests)
+- **Data storage**: None; delegates to core for file I/O
+
+#### `@codemcp/ade-harnesses` (`packages/harnesses`)
+
+- **Technology**: TypeScript
+- **Responsibilities**: Per-agent config file writers (AGENTS.md, .mcp.json, opencode.json, .kiro/, etc.)
+- **Interfaces**: `allHarnessWriters`, `getHarnessWriter()`, `buildHarnessWriters()`, `installSkills()`, `writeInlineSkills()`
+- **Data storage**: Writes agent-specific config files to the project root
+
+### Container Interactions
+
+```
+ade setup/install
+  │
+  ├─► loadExtensions()        [cli → disk: ade.extensions.mjs]
+  ├─► mergeExtensions()       [cli → core]
+  ├─► resolve()               [cli → core: UserConfig + Catalog → LogicalConfig]
+  ├─► writeLockFile()         [cli → core → disk: config.lock.yaml]
+  ├─► harness.install()       [cli → harnesses → disk: agent config files]
+  ├─► installSkills()         [cli → harnesses → @codemcp/skills]
+  └─► installKnowledge()      [cli → @codemcp/knowledge API]
+```
+
+### Deployment
+
+ADE is a developer tool — it runs locally (`npx @codemcp/ade`) or in CI. There is no persistent service. The generated output files are checked into the project repository.
+
+---
+
+## 3. Component Architecture (C4 Level 3)
+
+### `@codemcp/ade-core` Components
+
+#### Catalog
+
+- **Responsibilities**: Declares all built-in facets and options as TypeScript objects; provides `getDefaultCatalog()`, `mergeExtensions()`, `sortFacets()`, `getVisibleOptions()`
+- **Key files**: `catalog/index.ts`, `catalog/facets/{process,architecture,practices,backpressure,autonomy}.ts`
+- **Design pattern**: Static data objects; no runtime state
+
+#### Resolver
+
+- **Responsibilities**: Expands `UserConfig` choices against the `Catalog` using the `WriterRegistry`; produces `LogicalConfig`; deduplicates MCP servers and skills by key; auto-adds `@codemcp/knowledge-server` when `knowledge_sources` are non-empty
+- **Key files**: `resolver.ts`
+- **Design pattern**: Pure function `resolve(userConfig, catalog, registry): Promise<LogicalConfig>`
+
+#### Writer Registry
+
+- **Responsibilities**: Maps writer IDs to `ProvisionWriterDef` instances; `createDefaultRegistry()` pre-registers all built-in writers; open for runtime extension
+- **Key files**: `registry.ts`
+- **Design pattern**: `Map`-based registry; open/closed principle — new writers added without modifying core
+
+#### Provision Writers (built-in)
+
+| Writer | File | Output |
+|---|---|---|
+| `workflows` | `writers/workflows.ts` | `mcp_servers[]` entry |
+| `skills` | `writers/skills.ts` | `skills[]` entries |
+| `docset` | `writers/docset.ts` | `knowledge_sources[]` entry |
+| `instruction` | `writers/instruction.ts` | `instructions[]` entry |
+| `git-hooks` | `writers/git-hooks.ts` | `git_hooks[]` entries |
+| `permission-policy` | `writers/permission-policy.ts` | `permission_policy` |
+| `setup-note` | `writers/setup-note.ts` | `setup_notes[]` entry |
+| `mcp-server` | `writers/mcp-server.ts` | `mcp_servers[]` entry |
+
+Each writer receives `Record<string, unknown>` config and narrows internally; the registry contract stays generic.
+
+#### Types
+
+- **Responsibilities**: Single source of truth for all shared interfaces — `Catalog`, `Facet`, `Option`, `Provision`, `LogicalConfig`, `KnowledgeSource`, `DocsetPreset`, `SkillDefinition`, `UserConfig`, `LockFile`, `WriterRegistry`, `AdeExtensions`, and their Zod validation schemas
+- **Key file**: `types.ts`
+
+### `@codemcp/ade-cli` Components
+
+#### Entry Point / Router (`index.ts`)
+
+Parses `process.argv`, loads extensions, builds catalog and harness writers, delegates to `runSetup` or `runInstall`.
+
+#### `runSetup` (`commands/setup.ts`)
+
+Walks the user through the TUI facet-by-facet, resolves choices, writes `config.yaml` + `config.lock.yaml`, runs harness writers, installs skills and offers knowledge initialization.
+
+#### `runInstall` (`commands/install.ts`)
+
+Reads `config.lock.yaml`, runs harness writers, installs skills, and calls `installKnowledge` — no re-resolution.
+
+#### Extensions Loader (`extensions.ts`)
+
+Finds and loads `ade.extensions.{ts,mjs,js}` from the project root. Uses `jiti` for TypeScript files. Validates with `AdeExtensionsSchema`.
+
+#### Knowledge Installer (`knowledge-installer.ts`)
+
+Wraps `createDocset` + `initDocset` from `@codemcp/knowledge`. Handles "already exists" gracefully (proceeds to `initDocset`). Passes `preset` from `KnowledgeSource` (default: `"git-repo"`).
+
+---
+
+## 4. Architecture Decisions
+
+### Docsets as `docset` provision writer (not `Option.docsets[]`)
+
+**Decision**: Documentation sources are declared as `{ writer: "docset", config: { id, label, origin, description, preset? } }` recipe entries, identical in structure to skills provisions.
+
+**Rationale**: The old `Option.docsets[]` sibling field was a parallel mechanism that bypassed the writer registry, required a separate opt-out multiselect prompt, and introduced `excluded_docsets` in `UserConfig`. The writer model is already the right abstraction — using it for docsets makes the catalog uniform, removes per-item opt-out UX, and lets extensions contribute docsets with the same syntax as everything else.
+
+**Consequences**: `DocsetDef`, `collectDocsets()`, and `excluded_docsets` removed. Setup prompt simplified to a single opt-in confirm.
+
+### Two-package split: `core` + `cli`
+
+**Decision**: All types, logic, and writers live in `@codemcp/ade-core`. The CLI is a thin shell.
+
+**Rationale**: Core can be imported programmatically (CI scripts, tests, extensions) without pulling in TUI dependencies. It also enables the harnesses package to depend on core without depending on the CLI.
+
+### `LogicalConfig` as the stable contract
+
+**Decision**: Provision writers produce `Partial<LogicalConfig>`; harness writers consume `LogicalConfig`. Neither knows about the other.
+
+**Rationale**: Decouples the catalog / resolution side from the file-generation side. Adding a new harness requires no changes to writers; adding a new writer requires no changes to harnesses.
+
+### Lock file is the install source of truth
+
+**Decision**: `ade install` reads `config.lock.yaml` directly; it never re-resolves from `config.yaml`.
+
+**Rationale**: Mirrors `npm ci` / `package-lock.json`. Makes installs deterministic and reviewable. `config.lock.yaml` is checked in, so CI produces exactly what was reviewed.
+
+### Open registry for extensibility
+
+**Decision**: `WriterRegistry` is a `Map`-based runtime registry, not a discriminated union.
+
+**Rationale**: A discriminated union is a closed set — adding a writer from an extension package would require modifying core. The registry is open: any package can register a writer before `resolve()` runs.
+
+---
+
+## 5. References
+
+- Existing CLI design doc: `docs/CLI-design.md`
+- Existing CLI PRD: `docs/CLI-PRD.md`
+- Extensions guide: `docs/guide/extensions.md`
+- Example extension: `ade.extensions.mjs`

package/.vibe/docs/design.md

@@ -0,0 +1,179 @@
+<!--
+DESIGN DOCUMENT TEMPLATE - TIERED BY PROJECT COMPLEXITY
+
+PURPOSE: Document design principles, patterns, and standards that guide implementation.
+NOTE: Technology stack decisions belong in the Architecture Document, not here.
+
+PROJECT COMPLEXITY GUIDE:
+🚀 ESSENTIAL (Startup/MVP, 1-3 developers, <6 months): Sections 1-2 only
+🏢 CORE (Small team, 2-5 developers, 6-18 months): Sections 1-4
+🏗️ ADVANCED (Enterprise, 5+ developers, 18+ months): Sections 1-5
+⚡ SPECIALIZED (Mission-critical, high reliability): All sections + custom
+
+WHAT TO INCLUDE:
+✅ Design principles and patterns
+✅ Naming conventions and standards
+✅ Component design approaches
+✅ Data modeling principles
+✅ Quality attribute design strategies
+❌ Technology stack choices (goes in Architecture doc)
+❌ Concrete class names or implementations
+❌ Code snippets or method signatures
+
+START SMALL: Begin with Essential sections, add more as project matures.
+
+IMPORTANT: DO NOT REMOVE THIS COMMENT HOW TO USE THE TEMPLATE!
+-->
+
+# ADE — Design Document
+
+## 1. Naming Conventions
+
+### Types and Interfaces
+
+- **PascalCase** for all TypeScript interfaces, type aliases, and enums: `LogicalConfig`, `KnowledgeSource`, `DocsetPreset`, `ProvisionWriterDef`.
+- Suffix `Def` for writer definition interfaces: `ProvisionWriterDef`, `AgentWriterDef`.
+- Suffix `Schema` for Zod validation schemas: `AdeExtensionsSchema`, `OptionSchema`.
+- Suffix `Writer` for instances of writers registered in the registry: `docsetWriter`, `skillsWriter`, `workflowsWriter`.
+- Suffix `Facet` for exported catalog facet objects: `architectureFacet`, `practicesFacet`.
+
+### Functions
+
+- **camelCase** throughout. Factory functions prefixed `create`: `createDefaultRegistry()`, `createRegistry()`. Reader/writer pairs prefixed `read`/`write`: `readLockFile()`, `writeLockFile()`. Accessor functions prefixed `get`: `getFacet()`, `getOption()`, `getProvisionWriter()`.
+- CLI entry points prefixed `run`: `runSetup()`, `runInstall()`.
+
+### Files
+
+- One primary export per file; file name matches the export name in kebab-case: `docset.ts` exports `docsetWriter`, `knowledge-installer.ts` exports `installKnowledge`.
+- Test files co-located: `docset.ts` → `docset.spec.ts`. Integration tests suffixed `.integration.spec.ts`.
+
+### Writer IDs
+
+- Kebab-case string IDs matching the file name: `"docset"`, `"git-hooks"`, `"permission-policy"`, `"setup-note"`.
+
+---
+
+## 2. Error Handling Design
+
+### Provision Writers
+
+Writers throw on invalid config. The resolver does not catch writer errors — a bad catalog entry or extension config fails loudly at setup time, not silently at runtime.
+
+### Knowledge Installer
+
+`createDocset` "already exists" errors are swallowed and execution falls through to `initDocset` (idempotency). All other `createDocset` errors and all `initDocset` errors are logged as warnings and skipped — one failing source does not block the rest.
+
+### Extensions Loading
+
+`AdeExtensionsSchema.safeParse()` on loaded extension data. On failure, a descriptive error is thrown before any resolution runs: _"Invalid ade.extensions file at …"_.
+
+### Unknown Writer IDs
+
+`resolve()` throws if a recipe provision references a writer ID not present in the registry. This is a catalog authoring error and should fail loudly.
+
+### TUI Cancellation
+
+`clack.isCancel()` is checked after every prompt. On cancel, `clack.cancel()` is called and the function returns early (no partial writes).
+
+---
+
+## 3. Architecture Patterns & Principles
+
+### Registry Pattern for Open Extensibility
+
+The `WriterRegistry` is a `Map`-based runtime dispatch table. New provision writers are registered with `registerProvisionWriter(registry, writerDef)` before `resolve()` runs. This keeps the system open for extension without modifying core — any package contributing via `ade.extensions.mjs` can register custom writers.
+
+### Pure Function Resolution
+
+`resolve()` is a pure async function: `(UserConfig, Catalog, WriterRegistry) → LogicalConfig`. It has no side effects and no I/O. This makes it trivially testable and usable in non-CLI contexts.
+
+### Stable Interface Seam: `LogicalConfig`
+
+All provision writers produce `Partial<LogicalConfig>`. All harness writers consume `LogicalConfig`. This seam is the only contract between the two sides — writers don't know about agents, agents don't know about writers.
+
+### Data-Driven Catalog
+
+The catalog is plain TypeScript data (no classes, no inheritance). Facets and options are literal objects conforming to the `Facet` and `Option` interfaces. This makes the catalog easily serializable, diffable, and extensible via `mergeExtensions()`.
+
+### Opt-In Confirmation for Side Effects
+
+Long-running or network-bound operations (skills installation, knowledge init) are never performed silently. The TUI asks the user with a `confirm` prompt (default: `false` for knowledge, `true` for skills). `ade install` performs these unconditionally since it is non-interactive and the lock file represents the user's prior decision.
+
+---
+
+## 4. Component Design Strategy
+
+### Component Boundary Principles
+
+- **`core`** has zero runtime I/O except config file reads/writes. No TUI, no network, no process spawning.
+- **`cli`** is the I/O layer: TUI prompts, extension file loading, subprocess/API calls to `@codemcp/skills` and `@codemcp/knowledge`.
+- **`harnesses`** knows all agent config formats but nothing about how selections were made.
+
+### Responsibility Assignment
+
+Each provision writer is responsible for exactly one `LogicalConfig` field group. It receives an untyped `config` record and narrows internally — the registry contract stays generic while the implementation is specific.
+
+### Interface Design
+
+Writers are `interface`-typed (open contracts), not `class`-based. This allows any object literal conforming to the interface to be registered — no inheritance required, no framework needed.
+
+### Dependency Direction
+
+```
+cli → core ← harnesses
+cli → harnesses
+```
+
+`core` has no upward dependencies. `harnesses` depends on `core` for types. `cli` depends on both.
+
+---
+
+## 5. Data Design Approach
+
+### Two-File Config Model
+
+- **`config.yaml`** (user-facing): stores `choices` and optional `custom` overrides. CLI-managed except the `custom` block. Checked into the repo as a team-shared declaration.
+- **`config.lock.yaml`** (generated): stores the fully resolved `LogicalConfig` snapshot. Never hand-edited. The install source of truth — `ade install` reads this, never re-resolves.
+
+### LogicalConfig as Intermediate Representation
+
+`LogicalConfig` is agent-agnostic. It is the normalised representation of what the project needs, before it is translated into any agent's format. Fields are append-only lists (MCP servers, skills, knowledge sources, instructions) deduplicated by a stable key.
+
+### Deduplication Keys
+
+- MCP servers: deduplicated by `ref`
+- Skills: deduplicated by `name`
+- Knowledge sources: deduplicated by `name`
+
+### `DocsetPreset` Typing
+
+`KnowledgeSource.preset` uses the same literal union as `@codemcp/knowledge`'s `DocsetPreset` (`"git-repo" | "local-folder" | "archive"`), keeping the types aligned without re-exporting the dependency's internal types directly.
+
+---
+
+## 9. Extension and Evolution Strategy
+
+### Extension Points
+
+1. **`facetContributions`** — append options to existing facets (most common)
+2. **`facets`** — add entirely new facets
+3. **`provisionWriters`** — register custom writers for custom `config` shapes
+4. **`harnessWriters`** — add support for new coding agents
+
+All four are declared in `ade.extensions.{mjs,ts}` in the project root. The CLI loads and validates this file before every `setup` or `install` run.
+
+### Versioning Strategy
+
+The `config.lock.yaml` carries a `version: 1` field. Breaking changes to the lock file format increment this version. `ade install` can detect a stale lock file and prompt the user to re-run `ade setup`.
+
+### Catalog Evolution
+
+Built-in catalog options can be updated in place. Extension options that `replaces` a built-in skill name override it at resolution time without modifying the upstream catalog.
+
+---
+
+# Implementation Notes
+
+- Tests import `runSetup` / `runInstall` directly; the CLI binary entry point is thin enough to not need its own tests.
+- Integration tests mock `@clack/prompts` (TUI) and `@codemcp/knowledge` (network I/O) via `vi.mock`. All `confirm` mock return values must be set explicitly per test — `vi.clearAllMocks()` resets them to `undefined` (falsy).
+- The `ProvisionWriter` union in `types.ts` is a type-level hint; the real runtime guard is the registry. Adding a new writer requires registering it in `createDefaultRegistry()` and the union.

package/.vibe/docs/requirements.md

@@ -0,0 +1,17 @@
+# Requirements Placeholder
+
+This is a placeholder document. The user has chosen not to maintain separate requirements documentation for this project.
+
+## INSTRUCTIONS FOR LLM
+
+**DO NOT EDIT THIS FILE**
+
+- Use the current development plan file to specify requirements for ongoing development
+- Reference requirements from the plan file context when needed
+- Focus requirements discussion in the plan file's "Goal" and relevant task sections
+- When requirements clarification is needed, document them in the plan file rather than here
+- This placeholder ensures the workflow variables work correctly while respecting the user's choice
+
+## User's Choice
+
+The user has explicitly chosen not to use dedicated requirements documentation for this project. Please respect this decision and work with the plan file for requirements-related information.

package/ade.extensions.mjs

@@ -40,24 +40,22 @@ export default {
             }
           },
           {
-            writer: "knowledge",
+            writer: "docset",
             config: {
-              sources: [
-                {
-                  name: "sap-abap-docs",
-                  origin: "https://your-serialized-version-of-abap-docs.git",
-                  description: "Official SAP ABAP Cloud development guide"
-                }
-              ]
+              id: "sap-btp-docs",
+              label: "SAP BTP",
+              origin: "https://your-serialized-version-of-btp-docs.git",
+              description: "SAP Business Technology Platform documentation"
             }
-          }
-        ],
-        docsets: [
+          },
           {
-            id: "sap-btp-docs",
-            label: "SAP BTP",
-            origin: "https://your-serialized-version-of-btp-docs.git",
-            description: "SAP Business Technology Platform documentation"
+            writer: "docset",
+            config: {
+              id: "sap-abap-docs",
+              label: "SAP ABAP Cloud",
+              origin: "https://your-serialized-version-of-abap-docs.git",
+              description: "Official SAP ABAP Cloud development guide"
+            }
           }
         ]
       }