bitfab-cli 0.2.315 → 0.2.316

package/dist/index.js

@@ -26987,10 +26987,10 @@ var semver3 = __toESM(require_semver2(), 1);
 
 // ../bitfab-plugin-lib/dist/bakedSdkVersions.js
 var BAKED_SDK_VERSIONS = {
-  typescript: "0.50.0",
-  python: "0.50.0",
-  ruby: "0.43.1",
-  go: "0.41.1"
+  typescript: "0.51.0",
+  python: "0.51.0",
+  ruby: "0.51.0",
+  go: "0.51.0"
 };
 
 // ../bitfab-plugin-lib/dist/installedSdk.js
@@ -35758,7 +35758,7 @@ The SDK-installed \`bitfab-replay\` command lets the team regression-test any re
 - **Replay root parity verification:** when reporting replay setup completion, include the required final verification section: \`Replay root parity:\`, \`Production root symbol:\`, \`Production import/path:\`, \`Replay symbol:\`, \`Replay import/path:\`, \`Same symbol? yes/no\`, and \`If no, why is this impossible?\`.
 - **Use the same \`Bitfab\` client across instrumentation and replay.** Import it from the instrumented module or a shared singleton; never construct a second client inside the registry module.
 - Register every pipeline name with the same client and exact production function/method. Decorated roots supply their trace function key automatically; plain handler roots declare it on the registry entry.
-- The SDK-installed \`bitfab-replay\` executable supplies \`--limit\`, \`--trace-ids\`, \`--name\`, \`--concurrency\`, \`--code-change\`, \`--experiment-group-id\`, \`--dataset-id\`, \`--grader-ids\`, and \`--mock\`. Never parse or forward these in the registry module.
+- The SDK-installed \`bitfab-replay\` executable supplies \`--limit\`, \`--trace-ids\`, \`--name\`, \`--concurrency\`, \`--code-change\`, \`--experiment-group-id\`, \`--dataset-ids\` (and its \`--dataset-id\` spelling), \`--grader-ids\`, and \`--mock\`. Never parse or forward these in the registry module.
 - Put only function-specific defaults such as \`adaptInputs\` / \`adapt_inputs\`, mock overrides, or database snapshots on the registry entry.
 - **Each registry entry MUST reference the actual instrumented function** (for handler-instrumented keys: a callable that re-invokes the actual framework entrypoint), never a stub or identity function. If historical inputs need reshaping, use the registry entry's input adapter.
 - **Load the app normally.** The registry module imports app code as a library, and the executable loads that module. Use the project's normal env loader around \`bitfab-replay\` when needed and keep module-scoped clients, config, and models wired as the app expects. This is for dependency resolution and fidelity, not safety.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bitfab-cli",
-  "version": "0.2.315",
+  "version": "0.2.316",
   "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",