@paradigma-inc/flywheel 0.1.79 → 0.1.80

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paradigma-inc/flywheel",
-  "version": "0.1.79",
+  "version": "0.1.80",
   "description": "One-command setup for Flywheel MCP hosts",
   "type": "module",
   "files": [

package/skills/flywheel/SKILL.md

@@ -70,3 +70,9 @@ Choose one primary file first, then add at most one supporting file only if need
 - Use `flywheel_compute_release_all` for token-scoped bulk cleanup with the
   active `lease_control_token`; add `force=true` only when the user explicitly
   asks for account-wide cleanup.
+- Respect Flywheel write limits. Current per-user limits are 120 node creates
+  per minute, 2,000 node creates per 24 hours, and 120 graph writes per minute.
+  Graph writes include existing-node edits, parent edge changes, deletes,
+  merges, tag/sharing changes, artifact finalization, artifact deletion, and
+  artifact-note updates. If a write returns `429`, honor `Retry-After` before
+  retrying the same idempotent request; do not spin in a tight retry loop.

package/skills/flywheel/references/flywheel-cli-tool-map.md

@@ -15,6 +15,7 @@ The CLI respects the same contracts the MCP surface enforces. See `flywheel-mcp-
 - Inline JSON payloads can be supplied with `--payload_json=<json>` or read from a file with `--payload_json=@path/to/file.json`.
 - Output format is controlled by `--format json|tsv|csv|table` (default: `json`). Pipe-friendly forms (`tsv`, `csv`) are useful for scripting.
 - For artifact uploads, the CLI offers a one-shot `flywheel artifacts:upload` that internally runs prepare + raw PUT + finalize. The split commands (`flywheel artifacts:upload:prepare`, `flywheel artifacts:upload:finalize`) are available for streaming or chunked uploads.
+- Mutating commands are subject to per-user write limits: 120 node creates per minute, 2,000 node creates per 24 hours, and 120 graph writes per minute. Graph writes include existing-node commits, edge changes, deletes, merges, tags, sharing, artifact finalization, artifact deletion, and artifact-note updates. On `429`, honor `Retry-After` and retry the same idempotent command after waiting.
 - Run `flywheel help <command>` for canonical per-command flags, types, defaults, examples, and related commands.
 
 ## MCP-Equivalent Tool Families

package/skills/flywheel/references/flywheel-mcp-tool-map.md

@@ -22,6 +22,7 @@ Flywheel is a graph-based system for tracking research work, decisions, and evid
 - Empirical workflow is hypothesis-driven: launch execution, inspect outcomes, publish evidence artifacts, and commit only after terminal status.
 - For empirical work, publish evidence with `flywheel_prepare_artifact_uploads`, upload raw file bytes, then `flywheel_finalize_artifact_uploads` before commit.
 - Artifact metadata records expose a non-empty `title` suitable for display labels; title normalization must never derive from `storage_url`.
+- Mutating tools are subject to per-user write limits: 120 node creates per minute, 2,000 node creates per 24 hours, and 120 graph writes per minute. Graph writes include existing-node commits, edge changes, deletes, merges, tags, sharing, artifact finalization, artifact deletion, and artifact-note updates. On `429`, honor `Retry-After` and retry the same idempotent write after waiting.
 
 ## Tool Families