feat(warp): add Warp as a new built-in target

Author: serhiizhabskiy

.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-04T15:49:22.108Z
+generated_at: 2026-05-04T17:34:45.131Z
 generated_by: serhii
 lib_version: 0.10.0
 checksums:

.amp/settings.json

@@ -0,0 +1,25 @@
+{
+  "amp.mcpServers": {
+    "context7": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "-y",
+        "@upstash/context7-mcp"
+      ],
+      "env": {}
+    },
+    "github": {
+      "description": "GitHub MCP server for repo operations",
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "-y",
+        "@modelcontextprotocol/server-github"
+      ],
+      "env": {
+        "GITHUB_TOKEN": "$GITHUB_TOKEN"
+      }
+    }
+  }
+}

.changeset/add-warp-target.md

@@ -0,0 +1,14 @@
+---
+"agentsmesh": minor
+---
+
+feat(warp): add Warp as a new built-in target
+
+Warp is an agentic development environment by Warp.dev. This adds project and global mode support:
+
+- **Rules**: `AGENTS.md` (root + embedded additional rules); legacy `WARP.md` supported on import
+- **Skills**: `.warp/skills/` with YAML frontmatter skill bundles
+- **MCP**: `.mcp.json` at project root (standard format, shared with Claude Code)
+- **Commands/Agents**: projected as skills via `supportsConversion`
+- **Global mode**: `~/.warp/skills/` (skills only — global rules are UI-managed via Warp Drive)
+- Lint warnings for unsupported features (hooks, ignore, permissions)

.husky/pre-commit

@@ -1 +1 @@
-pnpm lint-staged
+pnpm build && pnpm test && pnpm lint-staged

.rules

@@ -0,0 +1,94 @@
+# Operational Guidelines
+
+## Session Start
+
+- Read `tasks/lessons.md` before doing any work. Apply relevant lessons.
+
+## Workflow
+
+### Planning
+
+- Enter plan mode for any non-trivial task (3+ steps or architectural decisions). Write plan to `tasks/todo.md`.
+- If something goes sideways, STOP and re-plan — don't keep pushing.
+- Check in before starting implementation. Mark items complete as you go.
+
+### Subagents
+
+- Use subagents liberally for research, exploration, and parallel analysis. One tack per subagent.
+
+### Lessons
+
+- **When**: user correction, test failure, CI failure, code review feedback, or any other mistake signal.
+- **How**: add a bullet to `tasks/lessons.md` with (1) what went wrong, (2) root cause, (3) a rule that prevents recurrence.
+- This is the primary cross-session memory — ruthlessly iterate until mistake rate drops.
+
+### Verification
+
+- Never mark a task complete without proving it works — run tests, check logs, demonstrate correctness.
+- After every feature/story: use `post-feature-qa` skill (`skills/post-feature-qa/`).
+- Ask yourself: "Would a staff engineer approve this?"
+
+### Elegance
+
+- For non-trivial changes: pause and ask "is there a more elegant way?"
+- Skip this for simple, obvious fixes — don't over-engineer.
+
+### Bug Fixing
+
+- When given a bug report: just fix it. Find root cause, point at logs/errors, resolve. Zero hand-holding.
+
+## Skills
+
+- **post-feature-qa** — Apply after every feature/story. Senior QA: verify edge-case coverage and story alignment.
+- **add-agent-target** — Use when adding a new AI agent target. Covers research, implementation, fixtures, full test coverage, docs.
+- **add-global-mode-target** — Use when adding or extending **global mode** (`--global`, `.agentsmesh`) for an existing target. Covers descriptor.global wiring, import/generate paths, reference rewriting, tests, and matrix docs.
+
+
+## Core Principles
+
+- **Simplicity**: Make every change as simple as possible. Only touch what's necessary.
+- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
+
+## Project Rules
+
+- **Architecture baseline**: Read `docs/architecture/review.md` before architectural or multi-file changes.
+- **Core flow to preserve**: canonical `.agentsmesh` content -> descriptor-driven generation/import (`src/targets/<id>/index.ts`) -> shared reference rewrite/lock checks -> strict artifact verification.
+- **Scale limitations to account for**: avoid target-name hardcoding in shared/core code, avoid duplicated per-target helper logic, and keep capability variance expressed in descriptors (not ad-hoc generator branches).
+- **Global mode discipline**: treat global support as one cohesive contract (layout + capabilities + detection + scope extras), not scattered one-off hooks.
+- **TDD mandatory**: Write failing tests FIRST, then implement.
+- **Max file size**: 200 lines. Split by responsibility if larger.
+- **No classes unless stateful**: Prefer pure functions + types.
+- **No `any`**: Use `unknown` + narrowing.
+- **Config source of truth**: `.agentsmesh` directory. Generated files are artifacts.
+- **Test naming**: `{module}.test.ts` colocated with source. Integration tests in `tests/integration/`.
+- **Generated artifact tests must be strict**: Assert exact file paths, exact file counts, and exact referenced wrapper/script sets. No loose checks (`some(...)`, prefix-only, "at least one").
+- **Commit format**: conventional commits — `feat|fix|test|refactor(scope): message`
+- **Docs must stay current**: Any change to CLI commands, flags, config schema, supported targets, or canonical file formats **must** be reflected in both `README.md` and the website (`website/src/content/docs/`) before the task is marked complete.
+- **Target data single source of truth** — do **not** hardcode target lists or support levels outside this chain:
+  1. `src/targets/catalog/target-ids.ts` (`TARGET_IDS`) = canonical target ID list. Each target's `capabilities` in `src/targets/<name>/index.ts` = feature support levels.
+  2. `src/core/matrix/data.ts` (`SUPPORT_MATRIX`) = built dynamically from descriptors. Never hardcode.
+  3. `website/src/content/docs/reference/supported-tools.mdx` = **single docs page** for per-target support. All other pages link here — no duplicate tables.
+  4. `README.md` matrix must stay in sync with code capabilities.
+  5. No hardcoded target counts or enumerations on homepage, CLI overview, or other pages. Use generic language and link to the matrix.
+  6. Adding/changing a target: update `target-ids.ts` + descriptor → `supported-tools.mdx` → `README.md` matrix. No other docs pages should need changes.
+- **CLI display paths must use forward slashes**: Any CLI output displaying file paths to users must normalize with `.replaceAll('\\', '/')` before printing. Tests assert forward-slash paths unconditionally; native `node:path` separators leak platform differences into output.
+- **Refer to PRD**: `docs/prd-v2-complete.md` for architecture decisions
+- **Refer to tasks**: `docs/agentsmesh-ai-first-tasks.md` for current task specs
+
+<!-- agentsmesh:embedded-rules:start -->
+<!-- agentsmesh:embedded-rule:start {"source":"rules/typescript.md","description":"TypeScript-specific coding standards","globs":["src/**/*.ts","tests/**/*.ts"],"targets":[]} -->
+## TypeScript-specific coding standards
+# TypeScript Standards
+
+- Use strict mode
+- Prefer `unknown` over `any`
+- Use explicit return types for public functions
+- Prefer `interface` over `type` for object shapes
+<!-- agentsmesh:embedded-rule:end -->
+<!-- agentsmesh:embedded-rules:end -->
+
+<!-- agentsmesh:root-generation-contract:start -->
+## AgentsMesh Generation Contract
+
+`agentsmesh.yaml` selects targets/features (`agentsmesh.local.yaml` overrides locally), and `.agentsmesh` is the only place to add or edit canonical items: `rules/_root.md`, `rules/*.md`, `commands/*.md`, `agents/*.md`, `skills/*/SKILL.md` plus supporting files, `mcp.json`, `hooks.yaml`, `permissions.yaml`, and `ignore`; if missing run `agentsmesh init`, use `agentsmesh import --from <tool>` for native configs, `agentsmesh install <source>` or `install --sync` for reusable packs, then run `agentsmesh generate`. Use `diff`, `lint`, `check`, `watch`, `matrix`, and `merge` as needed; never edit generated tool files.
+<!-- agentsmesh:root-generation-contract:end -->

.warp/skills/add-agent-target/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: add-agent-target
+description: Use when adding support for a new AI agent target to agentsmesh. Covers official format research, canonical mapping, importer/generator/linter work, realistic fixtures, unit/integration/e2e coverage, matrix/docs updates, and final verification. Includes both project and global mode from day one.
+---
+
+# Add Agent Target
+
+Use this skill when the task is to add a brand-new supported agent target to this repository (built-in) or as an external plugin package.
+
+**Primary reference**: `docs/add-new-target-playbook.md` is the step-by-step workflow (phases 1–9, file templates, verification gates). Open it first and follow it. This skill file is the contract — the non-negotiable rules, touchpoints, and completion bar. The playbook is how; this file is what and why.
+
+**Companion skill**: `add-global-mode-target` — use only when extending global-mode support into an existing target that was built before global was a first-class contract. For new targets, global mode is part of this skill (scaffold wires it automatically).
+
+## When To Use
+
+- The task is to add a tool not currently in `src/targets/catalog/target-ids.ts`
+- Scope covers both `project` and `global` modes unless the target has no meaningful global surface
+- Delivery is either built-in (in this repo) or external plugin (standalone npm package)
+
+## Do Not Use This Skill For
+
+- Extending global-mode coverage on an existing target — use `add-global-mode-target`
+- Changing capability levels for an existing target — update the target's descriptor directly
+- Plugin feature work that doesn't add a new target id
+
+## Non-Negotiable Rules
+
+### MUST
+
+- Search the internet for the target's current official file structure, config files, and example content before changing code.
+- Prefer official docs and other primary sources. Use vendor examples or source code only when official docs are incomplete, and call that out explicitly.
+- Separate the target product from the current assistant runtime before making format decisions. Do not confuse a generated target like `codex-cli` with Codex desktop/chat, or local CLI MCP config with app-managed connectors.
+- Capture the target's real capability map for every canonical feature: rules, additionalRules, commands, agents, skills, mcp, hooks, ignore, permissions.
+- When a feature is `none` but `skills` is `native` or `embedded`, evaluate whether `supportsConversion` should project that feature as skills. If the target reads skill bundles, commands and agents with no native surface should be projected as skills via `supportsConversion: { commands: true, agents: true }` and registered in `src/config/core/conversions.ts` with `DEFAULT_*_TO_SKILLS`. Do not add lint warnings for features that are projected as skills — only warn for features that are truly dropped.
+- Start from `agentsmesh target scaffold <id>` when building a built-in target. Do not hand-write the 10 skeleton files the scaffold produces.
+- Write failing tests first for every new behavior. Do not implement first and backfill later.
+- Add unit, integration, and e2e coverage for the complete import and generate flow, including global scope when applicable.
+- Add rich and realistic fixtures for the new target. Fixtures must resemble real projects, not toy placeholders.
+- Cover all edge cases for the new target, including legacy paths, fallbacks, malformed files, partial support, and unsupported features.
+- Wire descriptor capabilities for both project and global scope. New targets must include global mode unless the target has no global config surface at all, and that absence must be documented.
+- Update every affected command surface and user-facing document so the new target is discoverable and accurately described.
+- Update the compatibility matrix to reflect native, embedded, partial, or unsupported features. The matrix auto-builds from descriptor capabilities; `pnpm matrix:verify` must pass.
+- Update init detection and import empty-state messaging for the new target when native files exist.
+- Reuse existing capability-focused tests where possible; extend them instead of duplicating assertions across multiple files.
+- Preserve the canonical `.agentsmesh/` contract. If the target cannot represent a feature natively, model that explicitly instead of inventing fake native output.
+- Ensure every internal file link or reference inside generated or imported Markdown artifacts is convertible through the shared reference-rewrite pipeline, just like the existing targets. Do not ship a new target unless canonical `.agentsmesh/` references round-trip cleanly across that target's Markdown surfaces.
+- Run the full verification stack, including the packaging gates (`pnpm attw`, `pnpm publint`, `pnpm consumer-smoke`), before claiming completion.
+- Run the `post-feature-qa` skill before marking the task done.
+
+### MUST NOT
+
+- Do not infer the target format from old fixtures, README text, or memory alone.
+- Do not add placeholder fixtures with `SYNTHETIC` markers or obviously fake content.
+- Do not add shallow smoke tests as a substitute for feature coverage.
+- Do not silently skip unsupported features; document and test the chosen behavior.
+- Do not leave commands, schema enums, init detection, matrix output, or docs partially updated.
+- Do not hardcode target-specific branches in shared code when a descriptor field can carry the behavior.
+
+## Workflow (detailed in `docs/add-new-target-playbook.md`)
+
+1. **Research** — §1 of the playbook. Answer every research-checklist item from primary sources before writing code.
+2. **Scaffold** — §2 of the playbook. Run `pnpm exec agentsmesh target scaffold <id>`, then register the id in the three catalog files listed there.
+3. **Constants and capabilities** — §3. Fill in paths and capability levels for both project and global scope.
+4. **Conversion eligibility** — For each feature marked `none` in capabilities, check if the target supports skills (`native` or `embedded`). If so, add `supportsConversion` to the descriptor for those features, register defaults in `src/config/core/conversions.ts`, and omit lint warnings for those features (they become `embedded` via skill projection). Only emit lint warnings for features that are truly dropped with no fallback.
+5. **Tests first** — §4. Add realistic fixtures under `tests/e2e/fixtures/<id>-project/` and write failing unit/integration/e2e tests.
+5. **Implement generators, importers, and reference maps** — §5. Feature-by-feature, using existing targets as reference implementations.
+6. **Global mode** — §6. Fill in `descriptor.global`, `rewriteGeneratedPath`, and any `skillMirror` or `sharedArtifacts` needs.
+7. **Plugin packaging** — §7. Only if shipping as an external plugin rather than a built-in.
+8. **Matrix and docs** — §8. Run `pnpm schemas:generate && pnpm matrix:generate` and update `website/src/content/docs/reference/supported-tools.mdx`.
+9. **Verification** — §9. Run the full stack (see below). All must pass.
+
+Refer to `./references/target-addition-checklist.md` for the concrete audit list of touchpoints, tests, fixtures, and edge cases.
+
+## Required Verification
+
+Before claiming completion, every command must pass:
+
+- `pnpm typecheck`
+- `pnpm lint`
+- `pnpm test`
+- `pnpm test:e2e`
+- `pnpm matrix:verify`
+- `pnpm publint`
+- `pnpm attw`
+- `pnpm consumer-smoke`
+
+If a narrower command is useful during iteration, run it first, but do not skip the full stack at the end.
+
+## Completion Standard
+
+The task is not done until all of the following are true:
+
+- The target appears in `agentsmesh matrix` CLI output and passes `pnpm matrix:verify`.
+- Import and generate behavior are both covered for every supported feature, in both project and global scope where applicable.
+- Unsupported or lossy features are documented in `website/src/content/docs/reference/supported-tools.mdx` and tested.
+- Fixtures under `tests/e2e/fixtures/<id>-project/` are rich enough to exercise real parsing branches (rules, skills, MCP, hooks, ignore as applicable).
+- Round-trip import → generate preserves content byte-for-byte where the format permits.
+- README matrix and website supported-tools page are in sync.
+- All verification commands listed above pass.
+- `post-feature-qa` skill has been applied and any gaps closed.