@codemcp/ade 0.5.0 → 0.6.1

package/.beads/issues.jsonl

@@ -60,3 +60,27 @@
 {"id":"ade-5.1","title":"Explore","description":"Understand the problem, analyze existing patterns, and design your approach. Consider the scope and impact of the change. **STEP 1: Analyze Requirements** - If  exists: Use it to understand the required changes - Otherwise: Document requirements in your task management system **STEP 2: Review Design Approach** - If  exists: Respect the design approach documented in  - Otherwise: Design your approach based on the problem analysis **STEP 3: Document Decisions** - Document your analysis and design decisions - Create tasks to guide implementation - Focus on analysis and design only - do not write any code yet","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.459272+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.459272+01:00","dependencies":[{"issue_id":"ade-5.1","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-5.2","title":"Implement","description":"Write clean, focused code for the minor enhancement, test your changes, and prepare for commit. **STEP 1: Review Design and Requirements** - If  exists: Follow your design from  - Otherwise: Elaborate design options and present them to the user - If  exists: Ensure the relevant requirements from  are met - Otherwise: Ensure existing requirements are met based on your task context **STEP 2: Implement Changes** - Write clean, focused code for the minor enhancement - Test your changes to ensure they work correctly and don't break existing functionality **STEP 3: Prepare for Finalization** - Update task progress as needed - Prepare documentation and commit when ready","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.597501+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.597501+01:00","dependencies":[{"issue_id":"ade-5.2","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-5.2","depends_on_id":"ade-5.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"ade-5.3","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: - **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.  - **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  - **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: - **Update Long-Term Memory Documents**: Based on what was actually implemented:   - If  exists: Update  if requirements changed during development   - If  exists: Update  if design details were refined or changed - **Compare Against Implementation**: Review documentation against actual implemented functionality - **Update Changed Sections**: Only modify documentation sections that have functional changes - **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions - **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process - **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 minor enhancement is ready for delivery - Update task progress and mark completed work as you finalize the minor enhancement","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T11:33:13.733496+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T11:33:13.733496+01:00","dependencies":[{"issue_id":"ade-5.3","depends_on_id":"ade-5","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-5.3","depends_on_id":"ade-5.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6","title":"ade: epcc (development-plan.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-19T16:48:54.346525+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T20:46:05.46088+01:00","closed_at":"2026-03-19T20:46:05.46088+01:00","close_reason":"Closed"}
+{"id":"ade-6.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-19T16:48:54.522007+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T20:46:05.255704+01:00","closed_at":"2026-03-19T20:46:05.255704+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.1","depends_on_id":"ade-6","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.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-19T16:48:54.661272+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T20:46:05.353452+01:00","closed_at":"2026-03-19T20:46:05.353452+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.2","depends_on_id":"ade-6","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.2","depends_on_id":"ade-6.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.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-19T16:48:54.813402+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T19:29:11.362541+01:00","closed_at":"2026-03-19T19:29:11.362541+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3","depends_on_id":"ade-6","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3","depends_on_id":"ade-6.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.1","title":"Add AdeExtensions interface and AdeExtensionsSchema (Zod) to packages/core/src/types.ts","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.210558+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.234448+01:00","closed_at":"2026-03-19T17:48:15.234448+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.1","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.2","title":"Add mergeExtensions() to packages/core/src/catalog/index.ts","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.382003+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.336955+01:00","closed_at":"2026-03-19T17:48:15.336955+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.2","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.2","depends_on_id":"ade-6.3.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.3","title":"Export AdeExtensions, AdeExtensionsSchema, mergeExtensions from packages/core/src/index.ts","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.523449+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.438591+01:00","closed_at":"2026-03-19T17:48:15.438591+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.3","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.3","depends_on_id":"ade-6.3.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.3","depends_on_id":"ade-6.3.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.4","title":"Add jiti as CLI dependency and zod as core dependency","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.663512+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.53763+01:00","closed_at":"2026-03-19T17:48:15.53763+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.4","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.5","title":"Create packages/cli/src/extensions.ts with loadExtensions(projectRoot)","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.81068+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.632037+01:00","closed_at":"2026-03-19T17:48:15.632037+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.5","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.5","depends_on_id":"ade-6.3.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.5","depends_on_id":"ade-6.3.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.6","title":"Wire extension loading into packages/cli/src/index.ts (setup + install commands)","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:05.953907+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:19.642615+01:00","closed_at":"2026-03-19T17:48:19.642615+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.6","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.6","depends_on_id":"ade-6.3.5","type":"blocks","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.6","depends_on_id":"ade-6.3.7","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.7","title":"Expose buildHarnessWriters(extensions) in packages/harnesses/src/index.ts","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:06.106652+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:15.854204+01:00","closed_at":"2026-03-19T17:48:15.854204+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.7","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.3.8","title":"Create ade.extensions.mjs SAP example in repo root","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T17:10:06.230083+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T17:48:19.753233+01:00","closed_at":"2026-03-19T17:48:19.753233+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.3.8","depends_on_id":"ade-6.3","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.3.8","depends_on_id":"ade-6.3.6","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.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-19T16:48:54.960844+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T19:37:20.65686+01:00","closed_at":"2026-03-19T19:29:11.477044+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.4","depends_on_id":"ade-6","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-6.4","depends_on_id":"ade-6.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-6.4.1","title":"e2e integration test: extension option produces skills + knowledge in setup output","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-19T19:30:47.327614+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-19T19:32:06.768961+01:00","closed_at":"2026-03-19T19:32:06.768961+01:00","close_reason":"Closed","dependencies":[{"issue_id":"ade-6.4.1","depends_on_id":"ade-6.4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-7","title":"ade: minor (development-plan-partially-skilled.md)","description":"Responsible vibe engineering session using minor workflow for ade","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T08:36:47.537604+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:36:47.537604+01:00"}
+{"id":"ade-7.1","title":"Explore","description":"Understand the problem, analyze existing patterns, and design your approach. Consider the scope and impact of the change. **STEP 1: Analyze Requirements** - If  exists: Use it to understand the required changes - Otherwise: Document requirements in your task management system **STEP 2: Review Design Approach** - If  exists: Respect the design approach documented in  - Otherwise: Design your approach based on the problem analysis **STEP 3: Document Decisions** - Document your analysis and design decisions - Create tasks to guide implementation - Focus on analysis and design only - do not write any code yet","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T08:36:47.694345+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:36:47.694345+01:00","dependencies":[{"issue_id":"ade-7.1","depends_on_id":"ade-7","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-7.2","title":"Implement","description":"Write clean, focused code for the minor enhancement, test your changes, and prepare for commit. **STEP 1: Review Design and Requirements** - If  exists: Follow your design from  - Otherwise: Elaborate design options and present them to the user - If  exists: Ensure the relevant requirements from  are met - Otherwise: Ensure existing requirements are met based on your task context **STEP 2: Implement Changes** - Write clean, focused code for the minor enhancement - Test your changes to ensure they work correctly and don't break existing functionality **STEP 3: Prepare for Finalization** - Update task progress as needed - Prepare documentation and commit when ready","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T08:36:47.863047+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:36:47.863047+01:00","dependencies":[{"issue_id":"ade-7.2","depends_on_id":"ade-7","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-7.2","depends_on_id":"ade-7.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-7.3","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: - **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.  - **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  - **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: - **Update Long-Term Memory Documents**: Based on what was actually implemented:   - If  exists: Update  if requirements changed during development   - If  exists: Update  if design details were refined or changed - **Compare Against Implementation**: Review documentation against actual implemented functionality - **Update Changed Sections**: Only modify documentation sections that have functional changes - **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions - **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process - **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 minor enhancement is ready for delivery - Update task progress and mark completed work as you finalize the minor enhancement","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-20T08:36:48.033779+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:36:48.033779+01:00","dependencies":[{"issue_id":"ade-7.3","depends_on_id":"ade-7","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-7.3","depends_on_id":"ade-7.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-8","title":"ade: bugfix (development-plan-fix-zod.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-20T08:52:50.196761+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.196761+01:00"}
+{"id":"ade-8.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-20T08:52:50.355911+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.355911+01:00","dependencies":[{"issue_id":"ade-8.1","depends_on_id":"ade-8","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-8.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-20T08:52:50.505675+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.505675+01:00","dependencies":[{"issue_id":"ade-8.2","depends_on_id":"ade-8","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-8.2","depends_on_id":"ade-8.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-8.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-20T08:52:50.645347+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.645347+01:00","dependencies":[{"issue_id":"ade-8.3","depends_on_id":"ade-8","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-8.3","depends_on_id":"ade-8.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-8.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-20T08:52:50.824002+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.824002+01:00","dependencies":[{"issue_id":"ade-8.4","depends_on_id":"ade-8","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-8.4","depends_on_id":"ade-8.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"ade-8.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-20T08:52:50.99667+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-20T08:52:50.99667+01:00","dependencies":[{"issue_id":"ade-8.5","depends_on_id":"ade-8","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"ade-8.5","depends_on_id":"ade-8.4","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}

package/.beads/last-touched

@@ -1 +1 @@
-ade-5.3
+ade-8.5

package/.vibe/beads-state-ade-fix-zod-7eypxn.json

@@ -0,0 +1,34 @@
+{
+  "conversationId": "ade-fix-zod-7eypxn",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-8",
+  "phaseTasks": [
+    {
+      "phaseId": "reproduce",
+      "phaseName": "Reproduce",
+      "taskId": "ade-8.1"
+    },
+    {
+      "phaseId": "analyze",
+      "phaseName": "Analyze",
+      "taskId": "ade-8.2"
+    },
+    {
+      "phaseId": "fix",
+      "phaseName": "Fix",
+      "taskId": "ade-8.3"
+    },
+    {
+      "phaseId": "verify",
+      "phaseName": "Verify",
+      "taskId": "ade-8.4"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "ade-8.5"
+    }
+  ],
+  "createdAt": "2026-03-20T07:52:51.502Z",
+  "updatedAt": "2026-03-20T07:52:51.502Z"
+}

package/.vibe/beads-state-ade-main-iazal7.json

@@ -0,0 +1,29 @@
+{
+  "conversationId": "ade-main-iazal7",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-6",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "ade-6.1"
+    },
+    {
+      "phaseId": "plan",
+      "phaseName": "Plan",
+      "taskId": "ade-6.2"
+    },
+    {
+      "phaseId": "code",
+      "phaseName": "Code",
+      "taskId": "ade-6.3"
+    },
+    {
+      "phaseId": "commit",
+      "phaseName": "Commit",
+      "taskId": "ade-6.4"
+    }
+  ],
+  "createdAt": "2026-03-19T15:48:55.317Z",
+  "updatedAt": "2026-03-19T15:48:55.317Z"
+}

package/.vibe/beads-state-ade-partially-skilled-ywlqhb.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "ade-partially-skilled-ywlqhb",
+  "projectPath": "/Users/oliverjaegle/projects/privat/codemcp/ade",
+  "epicId": "ade-7",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "ade-7.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "ade-7.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "ade-7.3"
+    }
+  ],
+  "createdAt": "2026-03-20T07:36:48.277Z",
+  "updatedAt": "2026-03-20T07:36:48.277Z"
+}

package/.vibe/development-plan-extensibility.md

@@ -0,0 +1,169 @@
+# Development Plan: ade (main branch)
+
+*Generated on 2026-03-19 by Vibe Feature MCP*
+*Workflow: [epcc](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/epcc)*
+
+## Goal
+
+Make the ADE project extensible so that forks/downstream consumers can add new facets, options, and harness writers without modifying the upstream source files. The goal is upstream-compatibility — consumers should be able to pull upstream changes without merge conflicts caused by modifications to core catalog or registry files.
+
+## Explore
+<!-- beads-phase-id: ade-6.1 -->
+### Tasks
+- [x] Explore codebase structure: packages/core, packages/harnesses, packages/cli
+- [x] Understand how catalog, registry, and writers are wired together
+- [x] Identify all the places consumers currently need to modify to extend
+
+### Findings
+
+**Current extension points require modifying upstream files:**
+1. **Adding a new facet/option** → must edit `packages/core/src/catalog/index.ts` (`getDefaultCatalog()`) and add a new file in `catalog/facets/`
+2. **Adding a new provision writer** → must edit `packages/core/src/registry.ts` (`createDefaultRegistry()`) 
+3. **Adding a new harness writer** → must edit `packages/harnesses/src/index.ts` (`allHarnessWriters` array + `getHarnessWriter` + `getHarnessIds`)
+4. **Wiring it all into the CLI** → `packages/cli/src/index.ts` calls `getDefaultCatalog()` and relies on `allHarnessWriters` from harnesses
+
+**Existing infrastructure that's already extensible:**
+- `WriterRegistry` + `registerProvisionWriter/registerAgentWriter` already exist as a general-purpose registry
+- `Catalog` and `Facet` types are public and composable
+- `createRegistry()` + `createDefaultRegistry()` already allow building custom registries
+- `resolve()` accepts a `Catalog` and `WriterRegistry` — so it's already injection-ready
+- `runSetup(projectRoot, catalog)` already takes a `catalog` parameter
+
+**Key insight:** The CLI's `index.ts` is the main wiring point. It hardcodes `getDefaultCatalog()` and `allHarnessWriters`. The CLI needs a plugin/extension loading mechanism so forks can inject their extensions without modifying the upstream entry point.
+
+## Plan
+<!-- beads-phase-id: ade-6.2 -->
+
+### Phase Entrance Criteria:
+- [x] The codebase has been thoroughly explored
+- [x] Current extension points and blockers are identified
+- [x] It's clear what's in scope and what's out of scope
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Code
+<!-- beads-phase-id: ade-6.3 -->
+
+### Phase Entrance Criteria:
+- [ ] Design is documented and reviewed
+- [ ] Scope is agreed upon: what changes are needed and where
+- [ ] No open design questions remain
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Commit
+<!-- beads-phase-id: ade-6.4 -->
+
+### Phase Entrance Criteria:
+- [ ] All code changes are implemented and tested
+- [ ] Existing tests pass
+- [ ] The extension mechanism works end-to-end (catalog + writers + harnesses injectable)
+
+### 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
+
+### KD-1: Extension model — `ade.extensions.mjs` with declarative contributions
+
+A consumer creates `ade.extensions.mjs` (or `.js`) in their project (or in a forked CLI's src dir).
+The CLI loads it via dynamic `import()` at startup and merges contributions before resolving.
+
+The extension file exports a default object conforming to `AdeExtensions`:
+
+```ts
+interface AdeExtensions {
+  // Contribute new options into existing facets (e.g. add "SAP" to "architecture")
+  facetContributions?: Record<string, Option[]>
+  // Register entirely new facets
+  facets?: Facet[]
+  // Register new provision writers (e.g. a "sap-config" writer)
+  provisionWriters?: ProvisionWriterDef[]
+  // Register new harness writers (e.g. a custom IDE)
+  harnessWriters?: HarnessWriter[]
+}
+```
+
+**Why this model:**
+- `facetContributions` (keyed by facet id) is the right primitive for the SAP use case:
+  SAP is a new *option* inside the existing `architecture` facet, not a new facet.
+- `facets` covers the case where a consumer wants to add a completely new facet (e.g. "cloud-provider").
+- `provisionWriters` and `harnessWriters` cover the writer extension cases.
+- The consumer never needs to modify upstream files.
+- Dynamic `import()` means no build step required for `.mjs` extensions.
+
+### KD-2: Loading location
+
+The extension file is resolved relative to the **project root** passed to the CLI.
+Search order: `ade.extensions.mjs` → `ade.extensions.js` (first match wins).
+This works for both the "consumer uses npx @codemcp/ade setup" case and the "fork scenario".
+
+### KD-3: Type exports
+
+`AdeExtensions`, `HarnessWriter` (re-exported from harnesses), and all catalog/writer types
+are already exported from `@codemcp/ade-core`. We need to add `AdeExtensions` to the exports.
+No breaking changes to existing APIs.
+
+### KD-4: SAP example placement
+
+The SAP example (`sap` option on the `architecture` facet) will be implemented as a concrete
+`ade.extensions.mjs` example file **in the repo root** (not bundled into the catalog).
+This doubles as the integration test and documentation for the extension mechanism.
+
+### KD-5: Type safety for extension loading → documented in `docs/adrs/0002-extension-file-type-safety.md`
+
+Runtime Zod validation (always) + `jiti` for `.ts` extension files + `AdeExtensions` type export for JSDoc consumers.
+
+## Notes
+
+**SAP Architecture option shape** (what the consumer writes):
+```js
+// ade.extensions.mjs
+import { } from '@codemcp/ade-core'  // types only if needed
+
+const sapOption = {
+  id: 'sap',
+  label: 'SAP',
+  description: 'SAP development with ABAP, CAP (Cloud Application Programming model), and BTP',
+  recipe: [
+    {
+      writer: 'skills',
+      config: {
+        skills: [
+          { name: 'sap-architecture', description: '...', body: '...' },
+          { name: 'sap-design', description: '...', body: '...' },
+        ]
+      }
+    }
+  ],
+  docsets: [
+    { id: 'cap-docs', label: 'SAP CAP', origin: 'https://github.com/SAP/cloud-sdk.git', description: '...' }
+  ]
+}
+
+export default {
+  facetContributions: {
+    architecture: [sapOption]
+  }
+}
+```
+
+The CLI then calls `mergeExtensions(catalog, registry, extensions)` before running setup/install.
+
+**Files to create/modify:**
+1. `packages/core/src/types.ts` — add `AdeExtensions` type
+2. `packages/core/src/catalog/index.ts` — add `mergeExtensions(catalog, extensions)` function
+3. `packages/core/src/index.ts` — export `AdeExtensions` and `mergeExtensions`
+4. `packages/cli/src/extensions.ts` — new file: `loadExtensions(projectRoot)` using dynamic import
+5. `packages/cli/src/index.ts` — load extensions and pass merged catalog/registry to setup/install
+6. `packages/harnesses/src/index.ts` — expose `mergeHarnessWriters` or accept additional writers
+7. `ade.extensions.mjs` — example file in repo root with the SAP architecture option
+
+---
+*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/development-plan-fix-zod.md

@@ -0,0 +1,72 @@
+# Development Plan: ade (fix-zod branch)
+
+*Generated on 2026-03-20 by Vibe Feature MCP*
+*Workflow: [bugfix](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/bugfix)*
+
+## Goal
+Fix the packaged version of `@codemcp/ade` CLI failing with `ERR_MODULE_NOT_FOUND` for `zod` after the latest extensibility enhancement.
+
+## Reproduce
+<!-- beads-phase-id: ade-8.1 -->
+### Tasks
+
+- [ ] Identify where `zod` was introduced in the codebase
+- [ ] Understand whether `zod` is listed as a dependency or devDependency
+- [ ] Confirm the build/bundle configuration to determine if it should be bundled or declared external
+
+## Analyze
+<!-- beads-phase-id: ade-8.2 -->
+
+### Phase Entrance Criteria:
+- [ ] The bug is reproducible or the root cause is clear from code inspection
+- [ ] The affected code path is identified
+
+### Tasks
+
+- [ ] Determine why `zod` is not bundled into the CLI dist output
+- [ ] Check build configuration (tsup / rollup / esbuild)
+- [ ] Identify whether `zod` should be bundled or added as a runtime dependency
+
+## Fix
+<!-- beads-phase-id: ade-8.3 -->
+
+### Phase Entrance Criteria:
+- [ ] Root cause is clearly understood and documented
+- [ ] Fix strategy is decided (bundle vs. add dependency)
+
+### Tasks
+
+- [ ] Apply fix (either bundle zod or add it as a real dependency)
+- [ ] Verify the dist output includes or correctly references zod
+
+## Verify
+<!-- beads-phase-id: ade-8.4 -->
+
+### Phase Entrance Criteria:
+- [ ] Fix has been applied
+- [ ] Build has been re-run
+
+### Tasks
+
+- [ ] Build the CLI package
+- [ ] Verify the packaged CLI starts without `ERR_MODULE_NOT_FOUND`
+
+## Finalize
+<!-- beads-phase-id: ade-8.5 -->
+
+### Phase Entrance Criteria:
+- [ ] All verify tasks pass
+- [ ] No regressions introduced
+
+### 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
+
+## Key Decisions
+- **Bundle `zod` into CLI dist**: `zod` was added to `@codemcp/ade-core` for runtime validation of the new extension API (`AdeExtensionsSchema` in `types.ts`). The core package is built with plain `tsc`, leaving a bare `import { z } from "zod"` in its dist output. Since the CLI's tsup config inlines core via `noExternal`, but tsup does not recursively bundle core's own external deps, `zod` ended up as an unbundled external reference in the CLI output — causing `ERR_MODULE_NOT_FOUND` when installed globally via npx. Fix: add `"zod"` to `noExternal` in `packages/cli/tsup.config.ts` so tsup bundles it alongside the other inlined packages.
+
+## Notes
+- The `yaml` package is in core's dependencies too — it also gets pulled in transitively. Currently yaml is also listed as a direct dep of CLI and appears to be handled differently (likely already bundled or handled via noExternal path). Worth monitoring if the same pattern would affect yaml in future.
+- Bundle size went from ~1.26 MB to ~1.32 MB after adding zod (expected, zod is ~50 KB minified).
+
+---
+*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/development-plan-partially-skilled.md

@@ -0,0 +1,44 @@
+# Development Plan: ade (partially-skilled branch)
+
+*Generated on 2026-03-20 by Vibe Feature MCP*
+*Workflow: [minor](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/minor)*
+
+## Goal
+Add a new "CodeMCP Workflows (Skilled)" option to the process facet that includes the `VIBE_WORKFLOW_DOMAINS=skilled` env variable and all necessary skills (starting-project, architecture, design, coding, testing) as writers in the recipe.
+
+## Explore
+<!-- beads-phase-id: ade-7.1 -->
+
+### Phase Entrance Criteria
+- (initial phase, no entrance criteria)
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Implement
+<!-- beads-phase-id: ade-7.2 -->
+
+### Phase Entrance Criteria
+- [ ] The current state of `process.ts` and available skill IDs are understood
+- [ ] The new option's recipe structure is clear (which skills to include, what env vars to set)
+
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Finalize
+<!-- beads-phase-id: ade-7.3 -->
+### 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
+*Important decisions will be documented here as they are made*
+
+## Notes
+*Additional context and observations*
+
+---
+*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/ade.extensions.mjs

@@ -0,0 +1,66 @@
+/**
+ * ade.extensions.mjs — SAP BTP / ABAP architecture extension example
+ *
+ * Place this file in your project root to extend the default ADE catalog
+ * without modifying any upstream source files.
+ *
+ * This file serves as both documentation and an integration example.
+ * It is by no means functional! It's about providing options with dependent
+ * skills and documentation sources.
+ * TypeScript consumers can use ade.extensions.ts with full IDE type-checking.
+ *
+ * @type {import('@codemcp/ade-core').AdeExtensions}
+ */
+export default {
+  facetContributions: {
+    architecture: [
+      {
+        id: "sap-abap",
+        label: "SAP BTP / ABAP",
+        description:
+          "SAP Business Technology Platform with ABAP Cloud development",
+        recipe: [
+          {
+            writer: "skills",
+            config: {
+              skills: [
+                {
+                  name: "sap-abap-architecture",
+                  source: "your-org/ade-sap/skills/sap-abap-architecture"
+                },
+                {
+                  name: "sap-abap-code",
+                  source: "your-org/ade-sap/skills/sap-abap-code"
+                },
+                {
+                  name: "sap-abap-testing",
+                  source: "your-org/ade-sap/skills/sap-abap-testing"
+                }
+              ]
+            }
+          },
+          {
+            writer: "knowledge",
+            config: {
+              sources: [
+                {
+                  name: "sap-abap-docs",
+                  origin: "https://your-serialized-version-of-abap-docs.git",
+                  description: "Official SAP ABAP Cloud development guide"
+                }
+              ]
+            }
+          }
+        ],
+        docsets: [
+          {
+            id: "sap-btp-docs",
+            label: "SAP BTP",
+            origin: "https://your-serialized-version-of-btp-docs.git",
+            description: "SAP Business Technology Platform documentation"
+          }
+        ]
+      }
+    ]
+  }
+};

package/docs/adr/0002-extension-file-type-safety.md

@@ -0,0 +1,97 @@
+# ADR 0002: Type Safety Strategy for Extension File Loading
+
+## Status
+
+Proposed
+
+## Context
+
+ADE is being made extensible: consumers who fork the repository or use it as an upstream
+can place an `ade.extensions.mjs` (or `.js`, `.ts`) file in their project root to contribute
+new catalog options, facets, provision writers, and harness writers without modifying
+upstream files.
+
+The CLI loads this file at runtime via dynamic `import()`. This creates a type safety gap:
+
+- `import()` returns `Promise<unknown>`, so the loaded module has no compile-time shape
+  guarantee on the CLI side.
+- Consumers writing `.mjs`/`.js` extension files have no TypeScript compiler checking their
+  exported object against the `AdeExtensions` interface.
+- Shape errors (wrong property name, wrong recipe format, missing required field) would
+  surface as confusing runtime failures deep inside `resolve()` or a writer, not at the
+  point of authoring the extension.
+
+Three levels of type safety are available:
+
+**Level 1 — JSDoc `@type` annotation (authoring-time, opt-in)**
+The consumer annotates their JS extension file with
+`/** @type {import('@codemcp/ade-core').AdeExtensions} */`.
+This provides IDE autocompletion and type hints in editors with JSDoc awareness (VS Code).
+No build step. No CLI-side guarantee — the annotation is advisory only and silently ignored
+if the consumer doesn't use it.
+
+**Level 2 — Runtime Zod validation (load-time, mandatory)**
+The CLI validates the loaded module against a Zod schema derived from `AdeExtensions`
+immediately after import. Rejects invalid extensions with a structured, actionable error
+message before any catalog or registry mutation happens.
+No authoring-time feedback, but errors surface at `ade setup` time rather than
+mid-resolution.
+
+**Level 3 — TypeScript extension files via `jiti` (authoring-time, opt-in)**
+The CLI's extension loader also accepts `ade.extensions.ts`. Loading it requires an
+in-process TypeScript runner. `jiti` (by the Nuxt/unjs team) is the established solution:
+it strips types at load time using `oxc-transform` (zero native binaries, fast, ESM-native).
+Consumers writing `.ts` extension files get full TypeScript compiler checking and IDE
+support. `jiti` is already used by Vite, Nuxt, and most of the unjs ecosystem.
+
+These levels are not mutually exclusive. The fork scenario (consumer edits source TypeScript
+directly in a forked CLI) already has full compile-time safety through the TypeScript
+compiler — no additional mechanism needed there.
+
+## Decision
+
+We will implement **Level 2 (Zod runtime validation) combined with Level 3 (`.ts` support
+via `jiti`)**, and export the `AdeExtensions` type from `@codemcp/ade-core` to enable
+Level 1 as a zero-cost baseline for JS consumers.
+
+Concretely:
+
+1. `AdeExtensions` is defined as a TypeScript interface in `@codemcp/ade-core` and exported
+   from its public index.
+
+2. A corresponding `AdeExtensionsSchema` Zod schema is defined alongside the interface.
+   The CLI's `loadExtensions(projectRoot)` function validates every loaded extension object
+   against this schema and throws a structured error if validation fails.
+
+3. The extension loader searches for files in this order:
+   `ade.extensions.ts` → `ade.extensions.mjs` → `ade.extensions.js`
+   The first match is loaded. `.ts` files are loaded via `jiti`; `.mjs`/`.js` files via
+   native `import()`.
+
+4. `jiti` is added as a production dependency of `@codemcp/ade-cli`.
+
+## Consequences
+
+**Easier:**
+
+- Consumers writing `ade.extensions.ts` get full IDE type checking and compile-time errors
+  — the same authoring experience as editing the upstream source directly.
+- All consumers (JS and TS) get clear, structured error messages at `ade setup` time if
+  their extension file is malformed, rather than cryptic failures during resolution.
+- The `AdeExtensions` type and JSDoc `@type` path give JS consumers a zero-friction
+  upgrade path toward type safety without requiring a build step.
+- The fork scenario (editing CLI TypeScript source directly) retains full compile-time
+  safety with no additional tooling.
+
+**More difficult / trade-offs:**
+
+- Adding `jiti` as a dependency introduces a transitive dependency surface (~400 kB
+  unpacked, no native binaries). This is a deliberate trade-off accepted in exchange for
+  `.ts` extension support.
+- Zod must be kept as a runtime dependency of `@codemcp/ade-core` (it already is, or will
+  be added). The `AdeExtensionsSchema` must be kept in sync with the `AdeExtensions`
+  interface — a dual-maintenance surface. A build-time `zod-to-ts` or `ts-to-zod` step
+  could eliminate this in the future if drift becomes a problem.
+- Dynamic loading of arbitrary user files (via `import()` or `jiti`) means the CLI cannot
+  be fully type-checked end-to-end at its own build time. The Zod boundary is the explicit
+  trust boundary between upstream-typed code and user-supplied code.