SuavePlan/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated skills

Browse Source
This commit is contained in:
admin
2026-06-09 21:06:27 +01:00
parent db1ce43ee1
commit 427a5bd919
1283 changed files with 24684 additions and 2313 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
plugins/document-navigator/docs/devtools/tooling/sandbox/README.md
View File

@@ -105,4 +105,3 @@ engine-level boundary.
Server (`node:vm` / `node:worker_threads` / `node:child_process` / `node:crypto`).
Targets Node ≥ 20 (and Bun, which provides the same APIs).

2
plugins/document-navigator/docs/devtools/tooling/sandbox/src/resource-limiter/resource-limiter.md
View File

@@ -8,7 +8,7 @@ _(no submodules)_
`ResourceLimiter` enforces two complementary controls on the sandbox boundary: a sliding-window rate limit (so a single caller cannot exhaust the engine with rapid-fire executions) and an output-size cap (so log capture cannot grow unbounded inside long-running scripts). Both controls operate against an injectable `Clock` so tests can advance time deterministically rather than relying on `setTimeout` and observed wall-clock drift.
The limiter has no opinion about *what* it limits — the same instance is reused across executions, and the rate-limit window slides naturally as time passes. When the configured `maxExecutionsPerWindow` is `undefined`, the limiter is effectively a no-op for rate control; the output truncation still applies.
The limiter has no opinion about _what_ it limits — the same instance is reused across executions, and the rate-limit window slides naturally as time passes. When the configured `maxExecutionsPerWindow` is `undefined`, the limiter is effectively a no-op for rate control; the output truncation still applies.
## Features