chore(release): 0.2.8

- Bump version and changelog for Antigravity, Continue general.md rules,
  and target-descriptor registration.
- Sync package description/keywords with supported targets.
- Fix Continue e2e tree expectations for rules/general.md.
- Refresh lock and e2e last-run report after generate.

Made-with: Cursor

Author: serhiizhabskiy

.agentsmesh/.lock

@@ -1,9 +1,9 @@
 # Auto-generated. DO NOT EDIT MANUALLY.
 # Tracks the state of all config files for team conflict resolution.
 
-generated_at: 2026-03-29T08:57:28.949Z
+generated_at: 2026-03-29T10:20:37.442Z
 generated_by: serhii
-lib_version: 0.2.6
+lib_version: 0.2.8
 checksums:
   agents/code-debugger.md: sha256:707132841c606f117c83491d53ce101be0117eb50abe2861bcf93bdd45a56daf
   agents/code-documenter.md: sha256:faa66b16d2e86578985e817d60e6705ae0e34a716c1f5c29411739a6d659fb96

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.2.8
+
+### Patch Changes
+
+- Add Antigravity as a supported target, emit Continue root rules as `.continue/rules/general.md` (while still importing legacy `_root.md`), register built-in targets through target descriptors, and align Continue e2e contracts with the new rule filename.
+
 ## 0.2.6
 
 ### Patch Changes

package.json

@@ -1,7 +1,7 @@
 {
   "name": "agentsmesh",
-  "version": "0.2.6",
-  "description": "One canonical source for AI coding agent rules, commands, skills, MCP, hooks, and permissions — synced across Claude Code, Cursor, Copilot, Continue, Junie, Gemini CLI, Cline, Codex CLI, and Windsurf.",
+  "version": "0.2.8",
+  "description": "One canonical source for AI coding agent rules, commands, skills, MCP, hooks, and permissions — synced across Claude Code, Cursor, Copilot, Continue, Junie, Gemini CLI, Cline, Codex CLI, Windsurf, and Antigravity.",
   "type": "module",
   "main": "./dist/cli.js",
   "author": "sampleXbro",
@@ -63,6 +63,7 @@
     "cline",
     "codex",
     "windsurf",
+    "antigravity",
     "developer-tools",
     "devtools",
     "code-assistant",

tasks/lessons.md

@@ -1,5 +1,6 @@
 # Lessons Learned
 
+- **`execSync` shell must exist on Linux CI**: A lint integration test passed `shell: '/bin/zsh'` to merge stderr; GitHub Actions `ubuntu-latest` has no `/bin/zsh` → `spawnSync /bin/zsh ENOENT`. Root cause: macOS dev shells were assumed for all runners. Rule: for shell features like `2>&1` in integration tests, use `/bin/sh` (or omit `shell` and avoid shell-only syntax), never hardcode zsh-only paths unless the job installs zsh.
 - **When test fixtures grow required manifest fields, update callback expectations in the same pass**: I added `source_kind` and `features` to `InstallManifestEntry` fixtures in `tests/unit/install/install-sync.test.ts`, which made standalone TypeScript clean, but the full Vitest run still failed because the `reinstall` assertions were still expecting the old `{ name, source }` payload. Root cause: I repaired the typed fixture shape without sweeping downstream expectations that compare the same object at runtime. Rule: whenever a test helper or fixture type gains required fields, update all `toHaveBeenCalledWith` / deep-equality assertions that observe that payload before calling the pass complete.
 - **Repo typecheck that excludes tests must be supplemented when touching typed test fixtures**: A user still saw `TS2741` in `tests/unit/canonical/extend-load.test.ts` even though `pnpm typecheck` was green, because `tsconfig.json` excludes `**/*.test.ts` and the failing `ResolvedExtend` fixture only existed in a test file. Root cause: I relied on the repo typecheck gate without checking whether the touched file was inside the compiler include set. Rule: whenever a fix touches typed test files in this repo, run a standalone `tsc --noEmit ... <test-file>` (or an equivalent test-aware TS config) on the affected tests, especially for editor-reported TS errors.
 - **If ESLint rules target tests, the lint script must target tests too**: Warning cleanup surfaced unused vars and return-type warnings in `tests/` even though `pnpm lint` was green, because the script only ran `eslint src/` while `eslint.config.js` defined rules for `tests/**/*.ts` as well. Root cause: lint command scope drifted from the configured file scope, so test warnings accumulated outside the default verification path. Rule: whenever ESLint config includes `tests/**` or other first-class source trees, keep the `lint` script aligned with those paths and ignore only generated artifacts explicitly.

tests/e2e/agents-last-run.md

@@ -1,6 +1,6 @@
 # Agents E2E Last Run Report
 
-_Generated: 2026-03-29T08:29:04.394Z_
+_Generated: 2026-03-29T10:20:16.744Z_
 
 ## Initial — `.agentsmesh/agents/` (canonical fixture)
 

tests/e2e/continue-content-contract.e2e.test.ts

@@ -38,7 +38,7 @@ features:
       'prompts/',
       'prompts/review.md',
       'rules/',
-      'rules/_root.md',
+      'rules/general.md',
       'rules/typescript.md',
       'skills/',
       'skills/api-generator/',

tests/e2e/generate-capabilities.e2e.test.ts

@@ -532,7 +532,7 @@ features: [rules, commands, skills, mcp]
       'prompts/',
       'prompts/review.md',
       'rules/',
-      'rules/_root.md',
+      'rules/general.md',
       'rules/typescript.md',
       'skills/',
       'skills/api-generator/',

tests/integration/lint.integration.test.ts

@@ -74,7 +74,7 @@ Lib rules
     const out = execSync(`node ${CLI_PATH} lint 2>&1`, {
       cwd: TEST_DIR,
       encoding: 'utf-8',
-      shell: '/bin/zsh',
+      shell: '/bin/sh',
     });
     expect(out).toContain('match 0 files');
     expect(out).toContain('warning');