feat(targets): add supportsConversion for commands/agents as skills

Enable skill projection for features that have no native support:
- goose: commands + agents → skills (both are 'none', skills native)
- antigravity: agents → skills (agents 'none', skills native)
- continue: agents → skills (agents 'none', skills native/embedded)
- kiro: commands → skills (commands 'none', skills native)

Add generateCommands/generateAgents functions using shared projected
skill serializers. Wire commandPath/agentPath to return projected skill
paths so the reference rewriter maps canonical agents/commands to the
correct target-native locations. Enhance importEmbeddedSkills to
recognize projected agent/command skill markers and route them back
to canonical agents/commands on import (round-trip).

Register defaults in conversions.ts so projection is on by default.
Update contracts, matrix, e2e assertions, and add-agent-target skill
to document conversion eligibility checks for all new targets.

Author: serhiizhabskiy

.agents/skills/senior-developer-configuration-and-credentials/SKILL.md

@@ -29,7 +29,7 @@ User: "Query production MongoDB for user count"
 User: "Check Woodpecker CI status"
 ✅ Good: Check scripts/api-wrappers/ for existing tool → Or find WOODPECKER_TOKEN in .env → Use API
 ❌ Bad: "How do I access Woodpecker?" (find credentials, use them)
-</examples>
+<examples>
 
 **The pattern:** User asks to check a service → Find the credentials (AGENTS.md, .env, scripts/, workspace .env, project .env, global config) → Use them to complete the task. Don't ask the user for what you can find yourself
 

.agents/skills/senior-developer-professional-communication/SKILL.md

@@ -10,7 +10,7 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ 🔧 Fix auth issues ✨
 ✅ Fix authentication middleware timeout handling
-</examples>
+<examples>
 
 **Commit messages:** Concise, technically descriptive. Explain WHAT changed and WHY. Use proper technical terminology.
 
@@ -19,6 +19,6 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ "I'm going to try to fix this by exploring different approaches..."
 ✅ [Fix first, then report] "Fixed authentication timeout in auth.ts:234 by increasing session expiry window"
-</examples>
+<examples>
 
 ---

.agents/skills/senior-developer-tool-and-command-execution/SKILL.md

@@ -27,7 +27,7 @@ When you need to read a file, use your file reading tool - not `cat` or `head`.
 
 ❌ Bad: cat package.json | grep version
 ✅ Good: Use read tool, then search the content
-</examples>
+<examples>
 
 **The pattern is simple:** If you're working with file content (reading, editing, creating, searching), use the file tools. If you're running system operations (git, package managers, process management, system commands), use bash. Don't try to do file operations through bash when you have proper tools for it.
 

.agentsmesh/.lock

@@ -1,7 +1,7 @@
 # Auto-generated. DO NOT EDIT MANUALLY.
 # Tracks the state of all config files for team conflict resolution.
 
-generated_at: 2026-05-03T17:05:06.593Z
+generated_at: 2026-05-03T17:19:54.877Z
 generated_by: serhii
 lib_version: 0.10.0
 checksums:

.claude/skills/senior-developer-configuration-and-credentials/SKILL.md

@@ -31,7 +31,7 @@ User: "Query production MongoDB for user count"
 User: "Check Woodpecker CI status"
 ✅ Good: Check scripts/api-wrappers/ for existing tool → Or find WOODPECKER_TOKEN in .env → Use API
 ❌ Bad: "How do I access Woodpecker?" (find credentials, use them)
-</examples>
+<examples>
 
 **The pattern:** User asks to check a service → Find the credentials (AGENTS.md, .env, scripts/, workspace .env, project .env, global config) → Use them to complete the task. Don't ask the user for what you can find yourself
 

.claude/skills/senior-developer-professional-communication/SKILL.md

@@ -12,7 +12,7 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ 🔧 Fix auth issues ✨
 ✅ Fix authentication middleware timeout handling
-</examples>
+<examples>
 
 **Commit messages:** Concise, technically descriptive. Explain WHAT changed and WHY. Use proper technical terminology.
 
@@ -21,6 +21,6 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ "I'm going to try to fix this by exploring different approaches..."
 ✅ [Fix first, then report] "Fixed authentication timeout in auth.ts:234 by increasing session expiry window"
-</examples>
+<examples>
 
 ---

.claude/skills/senior-developer-tool-and-command-execution/SKILL.md

@@ -29,7 +29,7 @@ When you need to read a file, use your file reading tool - not `cat` or `head`.
 
 ❌ Bad: cat package.json | grep version
 ✅ Good: Use read tool, then search the content
-</examples>
+<examples>
 
 **The pattern is simple:** If you're working with file content (reading, editing, creating, searching), use the file tools. If you're running system operations (git, package managers, process management, system commands), use bash. Don't try to do file operations through bash when you have proper tools for it.
 

.cline/skills/senior-developer-configuration-and-credentials/SKILL.md

@@ -29,7 +29,7 @@ User: "Query production MongoDB for user count"
 User: "Check Woodpecker CI status"
 ✅ Good: Check scripts/api-wrappers/ for existing tool → Or find WOODPECKER_TOKEN in .env → Use API
 ❌ Bad: "How do I access Woodpecker?" (find credentials, use them)
-</examples>
+<examples>
 
 **The pattern:** User asks to check a service → Find the credentials (AGENTS.md, .env, scripts/, workspace .env, project .env, global config) → Use them to complete the task. Don't ask the user for what you can find yourself
 

.cline/skills/senior-developer-professional-communication/SKILL.md

@@ -10,7 +10,7 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ 🔧 Fix auth issues ✨
 ✅ Fix authentication middleware timeout handling
-</examples>
+<examples>
 
 **Commit messages:** Concise, technically descriptive. Explain WHAT changed and WHY. Use proper technical terminology.
 
@@ -19,6 +19,6 @@ description: Professional communication standards for commits and responses
 <examples>
 ❌ "I'm going to try to fix this by exploring different approaches..."
 ✅ [Fix first, then report] "Fixed authentication timeout in auth.ts:234 by increasing session expiry window"
-</examples>
+<examples>
 
 ---

.cline/skills/senior-developer-tool-and-command-execution/SKILL.md

@@ -27,7 +27,7 @@ When you need to read a file, use your file reading tool - not `cat` or `head`.
 
 ❌ Bad: cat package.json | grep version
 ✅ Good: Use read tool, then search the content
-</examples>
+<examples>
 
 **The pattern is simple:** If you're working with file content (reading, editing, creating, searching), use the file tools. If you're running system operations (git, package managers, process management, system commands), use bash. Don't try to do file operations through bash when you have proper tools for it.