bitfab-cli 0.2.498 → 0.2.500

package/dist/index.js

@@ -29627,7 +29627,7 @@ var listScenarios = {
 var getScenario = {
   name: "get_scenario",
   title: "Get Scenario",
-  description: "Read one scenario, found by its id or by a trace it was built from: the situation the trace function's run was in, as the trigger that started the run and the data available when it arrived, with a name and a description. The name, description, trigger, and data describe the situation only, never what the run did or should do. Returns the review status, the note saying what needs updating when a person flagged the scenario (and the resolution once one was sent), then the trigger and data summaries, then the actual outcome when one was saved (what the run actually did: one example, not what it should have done), then the name, description, trigger, data, and actualOutcome as JSON in exactly the shape save_scenario accepts, including the categories it is filed under. A scenario not generated yet has no trigger or data of its own: it is returned with its review status, its categories, and the assertions on the trace it was made from, whose input and output stand in for its trigger and data. data.sources, when saved, says where the records came from and, for each kind of data, whether it was read in full, as of the run or as of capture, with columns the capture predates, or not captured at all. Call it before save_scenario so an edit starts from what is saved.",
+  description: "Read one scenario, found by its id or by a trace it was built from: the situation the trace function's run was in, as the trigger that started the run and the data available when it arrived, with a name and a description. The name, description, trigger, and data describe the situation only, never what the run did or should do. Returns the review status, the note saying what needs updating when a person flagged the scenario (and the resolution once one was sent), then the trigger and data summaries, then the actual outcome when one was saved (what the run actually did: one example, not what it should have done), then the name, description, trigger, data, and actualOutcome as JSON in exactly the shape save_scenario accepts, including the categories it is filed under. When the organization has a scenario callback, it also says how the callback last went for this scenario and when: waiting to run, filled the scenario, answered with nothing to add, accepted the request to fill it later, skipped, or failed, with the reason for a skip or failure. A scenario not generated yet has no trigger or data of its own: it is returned with its review status, its categories, and the assertions on the trace it was made from, whose input and output stand in for its trigger and data. data.sources, when saved, says where the records came from and, for each kind of data, whether it was read in full, as of the run or as of capture, with columns the capture predates, or not captured at all. Call it before save_scenario so an edit starts from what is saved.",
   inputSchema: scenarioTargetSchema
 };
 var saveScenario = {
@@ -31126,10 +31126,10 @@ var semver2 = __toESM(require_semver2(), 1);
 
 // ../bitfab-plugin-lib/dist/bakedSdkVersions.js
 var BAKED_SDK_VERSIONS = {
-  typescript: "0.72.0",
-  python: "0.72.0",
-  ruby: "0.71.0",
-  go: "0.70.0"
+  typescript: "0.72.1",
+  python: "0.72.1",
+  ruby: "0.71.1",
+  go: "0.70.1"
 };
 
 // ../bitfab-plugin-lib/dist/installedSdk.js

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bitfab-cli",
-  "version": "0.2.498",
+  "version": "0.2.500",
   "description": "Install and configure the Bitfab plugin in Claude Code, Codex, or Cursor, or the Bitfab skill pack in Amp (Alpha).",
   "type": "module",
   "main": "dist/index.js",