bitfab-cli 0.2.269 → 0.2.270

package/dist/index.js

@@ -28415,7 +28415,7 @@ var saveTemplate = {
 var saveTracePlan = {
   name: "save_trace_plan",
   title: "Save Trace Plan",
-  description: "Create or update a tracing instrumentation plan. CREATE: omit `planId` and send `language`, the full `tree`, `capturedNodeIds`, and usually `traceFunctionKey`; this creates a reviewable plan and returns its id, Studio URL, initial capture count, and expiry. UPDATE: pass `planId`; use targeted `capture` / `uncapture` and/or `mockOnReplayByNodeId` changes without restating the tree, or send `tree` plus `capturedNodeIds` together for a structural replacement. A structural replacement may change `tree.rootId` when the trace boundary moves or is replaced. Targeted changes preserve status; a structural change to a confirmed plan reopens it to `awaiting`. Never create a second plan when one already exists for the work in hand: save it by `planId` instead. The captured set must stay one connected sub-tree with exactly one entry point, and that entry point always re-runs live and can never be mocked. Updates return the current plan summary, including the final captured set and replay/mock decisions.",
+  description: 'Create or update a tracing instrumentation plan. CREATE: omit `planId` and send `language`, the full `tree`, `capturedNodeIds`, and usually `traceFunctionKey`; this creates a reviewable plan and returns its id, Studio URL, initial capture count, and expiry. UPDATE: pass `planId`; use targeted `capture` / `uncapture` and/or `mockOnReplayByNodeId` changes without restating the tree, or send `tree` plus `capturedNodeIds` together for a structural replacement. A structural replacement may change `tree.rootId` when the trace boundary moves or is replaced. Targeted changes preserve status; a structural change to a confirmed plan reopens it to `awaiting`. Never create a second plan when one already exists for the work in hand: save it by `planId` instead, and find that id with `list_trace_plans({ traceFunctionKey, status: "awaiting" })` when you do not already hold it (get_trace_plan by key answers only for confirmed plans, so its miss does not mean the key is free). A cancelled plan is the one thing you cannot save onto: create fresh. An expired one needs no special handling, saving it revives it. The captured set must stay one connected sub-tree with exactly one entry point, and that entry point always re-runs live and can never be mocked. Updates return the current plan summary, including the final captured set and replay/mock decisions.',
   inputSchema: {
     planId: external_exports.string().optional().describe("Existing trace plan id to update. Omit to create a new plan. Do not send creation-only fields `language`, `source`, or `agentRunId` when this is supplied."),
     language: external_exports.enum(["python", "typescript", "ruby", "go"]).optional().describe("CREATE mode. Source language of the user's code. Required when `planId` is omitted."),
@@ -28446,7 +28446,7 @@ var confirmTracePlan = {
 var getTracePlan = {
   name: "get_trace_plan",
   title: "Get Trace Plan",
-  description: "Read a trace plan. Two modes: pass `planId` to read a specific plan (use this after save_trace_plan + browser confirmation to learn whether the user confirmed, cancelled, or is still pending); or pass `traceFunctionKey` to fetch the latest *confirmed* plan for that key. At the start of a Modify cycle, treat that confirmed plan as historical intent and reconcile its tree and captured nodes with current code; never assume the stored snapshot proves current instrumentation or use it to skip rereading code. Returns the full plan including the tree as JSON.",
+  description: 'Read a trace plan. Two modes: pass `planId` to read a specific plan (use this after save_trace_plan + browser confirmation to learn whether the user confirmed, cancelled, or is still pending); or pass `traceFunctionKey` to fetch the latest *confirmed* plan for that key. A key lookup that reports no plan has ruled out a confirmed one only: unconfirmed plans for that key (an analyze-repo draft, or one whose confirmation never landed) are found with `list_trace_plans({ traceFunctionKey, status: "awaiting" })`, and saving onto one of those beats creating a rival plan for the same key. At the start of a Modify cycle, treat that confirmed plan as historical intent and reconcile its tree and captured nodes with current code; never assume the stored snapshot proves current instrumentation or use it to skip rereading code. Returns the full plan including the tree as JSON.',
   inputSchema: {
     planId: external_exports.string().optional().describe("The trace plan id returned by save_trace_plan."),
     traceFunctionKey: external_exports.string().optional().describe("Trace function key. Returns the latest confirmed plan for this key in the caller's organization, or a 'no prior plan' message if none exists.")
@@ -28455,13 +28455,22 @@ var getTracePlan = {
 var listTracePlans = {
   name: "list_trace_plans",
   title: "List Trace Plans",
-  description: 'List existing trace plans for this organization, newest first. The primary use is surfacing the unconfirmed draft plans an earlier `analyze-repo` run uploaded (pass `source: "analyze_repo"`, `status: "awaiting"`) so an Instrument cycle can reuse them instead of re-scanning the codebase and re-drafting. Each entry includes the plan id (pass it to get_trace_plan / openTracePlan), the trace function key, the root name and file, language, the recommended captured-node count, status, source, and age. Expired plans are omitted. Use this before asking the user what to instrument.',
+  description: 'List existing trace plans for this organization, newest first. Two main uses. (1) Surfacing the unconfirmed draft plans an earlier `analyze-repo` run uploaded (pass `source: "analyze_repo"`, `status: "awaiting"`) so an Instrument cycle can reuse them instead of re-scanning the codebase and re-drafting. (2) Finding the plan that already exists for a trace function you are about to save (pass `traceFunctionKey`, and `status: "awaiting"` for the unconfirmed ones get_trace_plan by key does not return), so you update it by `planId` instead of creating a competing plan for the same key. Each entry includes the plan id (pass it to get_trace_plan / save_trace_plan / openTracePlan), the trace function key, the root name and file, language, the recommended captured-node count, status, source, and age. Expired plans are omitted. Use this before asking the user what to instrument.',
   inputSchema: {
+    traceFunctionKey: external_exports.string().min(1).optional().describe("Filter to plans saved under this exact trace function key. Omit for every key."),
     source: external_exports.enum(["interactive", "analyze_repo"]).optional().describe("Filter by how the plan was produced. 'analyze_repo' returns the non-interactive batch drafts; 'interactive' returns plans from a normal Instrument/Modify cycle. Omit for both."),
     status: external_exports.enum(["awaiting", "confirmed", "cancelled"]).optional().describe("Filter by plan status. 'awaiting' is an unconfirmed draft (the reusable ones), 'confirmed' has been accepted in Studio, 'cancelled' was dropped. Omit for any."),
     limit: external_exports.preprocess(parseJsonString, external_exports.number().min(1).max(50)).optional().describe("Max plans to return (default 20, max 50)")
   }
 };
+var cancelTracePlan = {
+  name: "cancel_trace_plan",
+  title: "Cancel Trace Plan",
+  description: "Retire an `awaiting` trace plan nobody will act on, so it stops coming back from list_trace_plans as a reusable draft. Use it when a draft is moot: its workflow is already instrumented under that key, or the user declined it. Only an awaiting plan can be cancelled, and cancelling is final (a cancelled plan cannot be updated or revived; re-plan the same work with a fresh save_trace_plan). A confirmed plan is the record of what the code captures and is never cancelled. When the draft is worth keeping but wrong, update it with save_trace_plan and its `planId` instead of cancelling and recreating.",
+  inputSchema: {
+    planId: external_exports.string().describe("The trace plan id to cancel. Must still be `awaiting`.")
+  }
+};
 var saveExperimentGroup = {
   name: "save_experiment_group",
   title: "Save Experiment Group",
@@ -28559,7 +28568,8 @@ var ALL_TOOL_CONTRACTS = [
   saveTracePlan,
   confirmTracePlan,
   getTracePlan,
-  listTracePlans
+  listTracePlans,
+  cancelTracePlan
 ];
 var TOOL_NAMES = ALL_TOOL_CONTRACTS.map((contract) => contract.name).sort();
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bitfab-cli",
-  "version": "0.2.269",
+  "version": "0.2.270",
   "description": "Install and configure the Bitfab plugin in Claude Code, Codex, or Cursor.",
   "type": "module",
   "main": "dist/index.js",