@squadrules/mcp 5.9.7 → 5.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/.tsbuildinfo +1 -1
- package/dist/embed-docs/mem/adapter-migration.md +1 -1
- package/dist/embed-docs/mem/author-adapter.md +1 -1
- package/dist/embed-docs/mem/bulk-insert-adapters-via-cli.md +1 -1
- package/dist/embed-docs/mem/challenge-type-guide.md +56 -1
- package/dist/embed-docs/mem/create-new-protocol.md +1 -1
- package/dist/embed-docs/mem/critic-loop-guide.md +1 -1
- package/dist/embed-docs/mem/critic-loop.md +1 -1
- package/dist/embed-docs/mem/phase-critic-guide.md +1 -1
- package/dist/embed-docs/mem/phase-critic.md +1 -1
- package/dist/embed-docs/mem/protocol-linking-guide.md +1 -1
- package/dist/embed-docs/mem/refine-search.md +1 -1
- package/dist/embed-docs/mem/skill-format-guide.md +1 -1
- package/dist/resources/embedded-mcp-resources.js +12 -12
- package/dist/resources/embedded-mcp-resources.js.map +1 -1
- package/dist/services/metrics/agent-metrics.d.ts +1 -1
- package/dist/services/metrics/agent-metrics.d.ts.map +1 -1
- package/dist/services/metrics/agent-metrics.js +1 -1
- package/dist/services/metrics/agent-metrics.js.map +1 -1
- package/dist/services/metrics/anomaly-metrics.d.ts +1 -1
- package/dist/services/metrics/anomaly-metrics.d.ts.map +1 -1
- package/dist/services/metrics/anomaly-metrics.js +1 -1
- package/dist/services/metrics/anomaly-metrics.js.map +1 -1
- package/dist/services/metrics/embedding-metrics.d.ts +1 -1
- package/dist/services/metrics/embedding-metrics.d.ts.map +1 -1
- package/dist/services/metrics/embedding-metrics.js +1 -1
- package/dist/services/metrics/embedding-metrics.js.map +1 -1
- package/dist/services/metrics/export-metrics.d.ts +1 -1
- package/dist/services/metrics/export-metrics.d.ts.map +1 -1
- package/dist/services/metrics/export-metrics.js +1 -1
- package/dist/services/metrics/export-metrics.js.map +1 -1
- package/dist/services/metrics/http-metrics.d.ts +1 -1
- package/dist/services/metrics/http-metrics.d.ts.map +1 -1
- package/dist/services/metrics/http-metrics.js +1 -1
- package/dist/services/metrics/http-metrics.js.map +1 -1
- package/dist/services/metrics/mcp-metrics.d.ts +1 -1
- package/dist/services/metrics/mcp-metrics.d.ts.map +1 -1
- package/dist/services/metrics/mcp-metrics.js +1 -1
- package/dist/services/metrics/mcp-metrics.js.map +1 -1
- package/dist/services/metrics/memory-metrics.d.ts +1 -1
- package/dist/services/metrics/memory-metrics.d.ts.map +1 -1
- package/dist/services/metrics/memory-metrics.js +1 -1
- package/dist/services/metrics/memory-metrics.js.map +1 -1
- package/dist/services/metrics/qdrant-metrics.d.ts +1 -1
- package/dist/services/metrics/qdrant-metrics.d.ts.map +1 -1
- package/dist/services/metrics/qdrant-metrics.js +1 -1
- package/dist/services/metrics/qdrant-metrics.js.map +1 -1
- package/dist/services/metrics/registry.d.ts +2 -2
- package/dist/services/metrics/registry.d.ts.map +1 -1
- package/dist/services/metrics/registry.js +1 -1
- package/dist/services/metrics/registry.js.map +1 -1
- package/dist/services/metrics/system-metrics.d.ts +3 -3
- package/dist/services/metrics/system-metrics.d.ts.map +1 -1
- package/dist/services/metrics/system-metrics.js +1 -1
- package/dist/services/metrics/system-metrics.js.map +1 -1
- package/dist/services/proof-of-work-store.d.ts +1 -1
- package/dist/services/proof-of-work-store.d.ts.map +1 -1
- package/dist/tools/activate.d.ts.map +1 -1
- package/dist/tools/activate.js +16 -4
- package/dist/tools/activate.js.map +1 -1
- package/dist/tools/activate_schema.d.ts +4 -0
- package/dist/tools/activate_schema.d.ts.map +1 -1
- package/dist/tools/activate_schema.js +2 -1
- package/dist/tools/activate_schema.js.map +1 -1
- package/dist/tools/forward-helpers.d.ts.map +1 -1
- package/dist/tools/forward-helpers.js +2 -0
- package/dist/tools/forward-helpers.js.map +1 -1
- package/dist/tools/forward-view.d.ts +2 -0
- package/dist/tools/forward-view.d.ts.map +1 -1
- package/dist/tools/forward-view.js +21 -16
- package/dist/tools/forward-view.js.map +1 -1
- package/dist/tools/forward_schema.d.ts +12 -0
- package/dist/tools/forward_schema.d.ts.map +1 -1
- package/dist/tools/forward_schema.js +28 -30
- package/dist/tools/forward_schema.js.map +1 -1
- package/dist/tools/next-pow-challenge-shape.d.ts.map +1 -1
- package/dist/tools/next-pow-challenge-shape.js +5 -0
- package/dist/tools/next-pow-challenge-shape.js.map +1 -1
- package/dist/tools/next-pow-helpers.d.ts.map +1 -1
- package/dist/tools/next-pow-helpers.js +18 -4
- package/dist/tools/next-pow-helpers.js.map +1 -1
- package/dist/tools/next-proof-types.d.ts +3 -0
- package/dist/tools/next-proof-types.d.ts.map +1 -1
- package/dist/tools/next_schema.d.ts +17 -0
- package/dist/tools/next_schema.d.ts.map +1 -1
- package/dist/tools/next_schema.js +11 -4
- package/dist/tools/next_schema.js.map +1 -1
- package/dist/tools/tool-registry.d.ts +10 -0
- package/dist/tools/tool-registry.d.ts.map +1 -1
- package/dist/types/memory.d.ts +4 -1
- package/dist/types/memory.d.ts.map +1 -1
- package/dist/ui/assets/{AccountPage-dY43Vecz.js → AccountPage-BsXHbykS.js} +1 -1
- package/dist/ui/assets/{index-pezhxMb9.js → index-BlAqndNJ.js} +2 -2
- package/dist/ui/index.html +1 -1
- package/package.json +2 -2
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
version: "5.
|
|
2
|
+
version: "5.10.0"
|
|
3
3
|
slug: challenge-type-guide
|
|
4
4
|
title: Challenge Type Selection Guide
|
|
5
5
|
---
|
|
@@ -206,6 +206,61 @@ to avoid collisions between parallel sessions.
|
|
|
206
206
|
- Reward Signal cleans it up
|
|
207
207
|
- never write credentials or secrets to files
|
|
208
208
|
|
|
209
|
+
### Resolving `project://` and `user://` URI hints
|
|
210
|
+
|
|
211
|
+
The server returns relative URI hints — it never names an absolute path on its
|
|
212
|
+
own filesystem. Resolve on your machine:
|
|
213
|
+
|
|
214
|
+
| Scheme | Resolution | Example |
|
|
215
|
+
|--------|-----------|--------|
|
|
216
|
+
| `project://<rel>` | `<IDE project root>/<rel>` | `project://.local/squadrules/work` → `/home/user/repos/my-project/.local/squadrules/work` |
|
|
217
|
+
| `user://<rel>` | `<$XDG_CONFIG_HOME or $HOME>/<rel>` | `user://.config/squadrules/work` → `/home/user/.config/squadrules/work` |
|
|
218
|
+
|
|
219
|
+
When your session spans multiple projects, prefer `user://` to avoid ambiguity
|
|
220
|
+
about which project root applies. When you have exactly one project context,
|
|
221
|
+
`project://` is fine.
|
|
222
|
+
|
|
223
|
+
### Worktree placement (for task-isolation adapters)
|
|
224
|
+
|
|
225
|
+
When an adapter requires a git worktree for isolation, the worktree path MUST
|
|
226
|
+
be **outside** every existing checkout. A common mistake is placing the worktree
|
|
227
|
+
inside `$REPO_ROOT` (e.g. `$REPO_ROOT/.mcp.worktrees/...`), which the setup
|
|
228
|
+
script correctly rejects.
|
|
229
|
+
|
|
230
|
+
**Correct placement — absolute path examples:**
|
|
231
|
+
|
|
232
|
+
```
|
|
233
|
+
REPO_ROOT=/home/user/repos/my-project
|
|
234
|
+
# RIGHT: sibling of the repo, not inside it
|
|
235
|
+
WT=/home/user/repos/mcp.worktrees/<task-id>
|
|
236
|
+
|
|
237
|
+
# WRONG: inside the checkout (rejected by setup script)
|
|
238
|
+
# WT=/home/user/repos/my-project/.mcp.worktrees/<task-id>
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
**Common mistakes:**
|
|
242
|
+
- `$REPO_ROOT/.mcp.worktrees/...` — inside checkout, rejected
|
|
243
|
+
- `./mcp.worktrees/...` — relative path resolves inside checkout
|
|
244
|
+
- `$REPO_ROOT/../mcp.worktrees/...` — correct only if `..` actually exits the repo
|
|
245
|
+
|
|
246
|
+
**Rule of thumb:** `$(dirname "$REPO_ROOT")/mcp.worktrees/<task-id>`
|
|
247
|
+
|
|
248
|
+
### IDE worktree access limitations
|
|
249
|
+
|
|
250
|
+
Most IDE file tools (Write, Read, Edit) scope operations to the open project
|
|
251
|
+
root. They **cannot** reach worktrees placed outside `$REPO_ROOT`. When working
|
|
252
|
+
in an IDE:
|
|
253
|
+
|
|
254
|
+
1. Use the **terminal/shell tool** (not IDE file tools) to read/write files in
|
|
255
|
+
external worktrees.
|
|
256
|
+
2. Shell commands: `cat`, `tee`, `cp`, or your editor's CLI mode work on any
|
|
257
|
+
absolute path.
|
|
258
|
+
3. If you need to edit a worktree file with IDE assistance, open the worktree
|
|
259
|
+
as a separate project window or use `code <worktree-path>` to add it to the
|
|
260
|
+
workspace.
|
|
261
|
+
4. The `squadrules export` MCP tool can retrieve adapter content without
|
|
262
|
+
filesystem access to the worktree.
|
|
263
|
+
|
|
209
264
|
```json
|
|
210
265
|
{"contract":{"type":"comment","comment":{"min_length":30},"required":true}}
|
|
211
266
|
```
|