bitfab-cli 0.2.234 → 0.2.236
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/index.js +2 -2
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -28373,7 +28373,7 @@ var saveTemplate = {
|
|
|
28373
28373
|
var createTracePlan = {
|
|
28374
28374
|
name: "create_trace_plan",
|
|
28375
28375
|
title: "Create Trace Plan",
|
|
28376
|
-
description: "Post a tracing instrumentation plan and get back a URL the user opens to
|
|
28376
|
+
description: "Post a tracing instrumentation plan and get back a URL the user opens to review or adjust it. Send the full call tree (root + children + framework spans + ~10 surrounding callers above the root and ~10 surrounding callees below each leaf as `pure` context nodes), the initial recommended captured node ids, replay `analysis` (classification + kind) on every node, and any sample input/output stored on the relevant nodes. Pass `traceFunctionKey` so future Modify cycles for this same key can bootstrap from this plan via get_trace_plan. Returns a URL the user opens in the browser; after they close or update the plan there, call get_trace_plan to read the final captured set and the per-node replay/mock decisions, then act on them.",
|
|
28377
28377
|
inputSchema: {
|
|
28378
28378
|
language: external_exports.enum(["python", "typescript", "ruby", "go"]).describe("Source language of the user's code"),
|
|
28379
28379
|
// Structured (not z.unknown()) so the tool's JSON Schema shows the agent
|
|
@@ -28390,7 +28390,7 @@ var createTracePlan = {
|
|
|
28390
28390
|
var confirmTracePlan = {
|
|
28391
28391
|
name: "confirm_trace_plan",
|
|
28392
28392
|
title: "Confirm Trace Plan",
|
|
28393
|
-
description: "Confirm a trace plan WITHOUT the browser, for the
|
|
28393
|
+
description: "Confirm a trace plan WITHOUT the browser, for the continue path where the user accepted the ASCII plan in chat, or left the Studio plan page without saving. Persists the plan as the latest *confirmed* plan for its traceFunctionKey (so later get_trace_plan by key, setup view, and setup modify can find it) and returns the final captured set plus per-node replay/mock decisions, exactly like get_trace_plan. Studio's Close/Update button does this for the browser path; call this only when the user continues without Studio, or leaves the plan page without saving. Pass the recommended capturedNodeIds; omit mockOnReplayByNodeId to accept the analysis-derived replay decisions (only pass it to override specific nodes the way a Studio toggle would).",
|
|
28394
28394
|
inputSchema: {
|
|
28395
28395
|
planId: external_exports.string().describe("The trace plan id returned by create_trace_plan."),
|
|
28396
28396
|
capturedNodeIds: external_exports.preprocess(parseJsonString, external_exports.array(external_exports.string()).min(1)).describe("The captured set to confirm. Must reference ids present in the plan's tree and form a single connected sub-tree with one entry point (its top-most captured span). The entry point does NOT have to be the plan's tree root: untracing the tree root and rooting at a captured descendant is honored and persisted as-is."),
|