@paradigma-inc/flywheel 0.1.15 → 0.1.16

package/package.json

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

package/skills/flywheel/SKILL.md

@@ -50,3 +50,9 @@ Choose one primary file first, then add at most one supporting file only if need
 - Prefer concrete steps and decision points over long narrative explanations.
 - Do not run broad document reads; load only what is required by the current request.
 - Do not start compute-heavy execution before design intent is clear.
+- For managed compute cleanup in autonomous runs, default to releasing only
+  known leases (leases acquired in the current run or explicitly selected by
+  the user).
+- When unknown active leases are present, report and skip by default.
+- Use account-wide release (`flywheel_compute_release_all`) only when the user
+  explicitly asks for account-wide cleanup.

package/skills/flywheel/compute/managed-compute.md

@@ -17,6 +17,11 @@ Flywheel can provision managed GPU instances for you from providers like Lambda
 3. **The agent handles the rest.** It acquires a machine, waits for it to become ready, and gets SSH access automatically. Provisioning typically takes a few minutes — the agent polls for readiness in the background.
 4. **Release when done.** When you're finished, the agent releases the lease. You can also release leases from the WebUI at any time.
 
+For autonomous runs, agents should default to releasing only known leases
+(leases acquired in the current run or explicitly selected by the user). If
+unknown active leases are detected, agents should report and skip those leases
+by default. Use account-wide release only when the user explicitly requests it.
+
 ## [](https://flywheel.paradigma.inc//#managing-machines-in-the-webui)Managing machines in the WebUI
 
 In **Settings > Machines**, you can see all GPU leases across your account — including the provider, state, hourly rate, total spend, and the acquire context that originally launched each lease. You can release individual leases or all at once.

package/skills/flywheel-auto/SKILL.md

@@ -84,7 +84,9 @@ Before execution, recover or establish these inputs:
    - Spawn up to `k` workers for distinct executable frontier nodes.
    - Route additional viable branches sequentially when there are more than `k` worthwhile directions.
    - After each resolved node, refresh the lookahead so the graph remains `n` hops ahead.
-   - Release managed compute with `flywheel_compute_release` or `flywheel_compute_release_all` when a branch is done.
+   - Release managed compute when a branch is done. Default to releasing only
+     known leases. Use `flywheel_compute_release_all` only when the user
+     explicitly requests account-wide cleanup.
    - Stop only when the graph-local terminal condition says to stop, such as: objective met, budget exhausted, or no non-redundant frontier branch is likely to produce enough decision-relevant information to justify the remaining budget and duplication risk.
 9. Commit after the node snapshot is coherent with `flywheel_commit_node`.
    - Commit resolved insight nodes only when they have non-empty `insights`.

package/skills/flywheel-reproduce/SKILL.md

@@ -80,7 +80,9 @@ Before execution, recover or establish these inputs:
    - Prefer explicit validation branches such as baseline checks, mechanism or intermediate-signal checks, ablations, efficiency checks, robustness checks, failure analysis, and follow-up analysis branches after results land.
    - If the branch can run through Flywheel execution directly, use `flywheel_launch_execution` and inspect terminal status before commit.
    - If the branch needs managed compute, use `flywheel_request_compute_grant_approval`, resolve the approved `compute_grant_id` with `flywheel_list_compute_grants` or `flywheel_list_approval_sessions`, then `flywheel_compute_acquire`, poll `flywheel_compute_status`, and use `flywheel_compute_connection` when the lease is ready.
-   - Release managed compute with `flywheel_compute_release` or `flywheel_compute_release_all` when a branch is done.
+   - Release managed compute when a branch is done. Default to releasing only
+     known leases. Use `flywheel_compute_release_all` only when the user
+     explicitly requests account-wide cleanup.
    - Stop when the core claim is resolved or the budget ceiling is reached.
 9. Commit after the node snapshot is coherent with `flywheel_commit_node`.
    - Commit resolved insight nodes only when they have non-empty `insights`.