fix: add shutdownTracing export to NAPI binding files

The new shutdownTracing() NAPI function needs its export registered
in the auto-generated binding files for the snapshot test to pass.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: branchseer

packages/cli/binding/index.cjs

@@ -769,3 +769,4 @@ module.exports.rewriteImportsInDirectory = nativeBinding.rewriteImportsInDirecto
 module.exports.rewriteScripts = nativeBinding.rewriteScripts;
 module.exports.run = nativeBinding.run;
 module.exports.runCommand = nativeBinding.runCommand;
+module.exports.shutdownTracing = nativeBinding.shutdownTracing;

packages/cli/binding/index.d.cts

@@ -267,6 +267,13 @@ export declare function rewriteScripts(scriptsJson: string, rulesYaml: string):
  */
 export declare function run(options: CliOptions): Promise<number>;
 
+/**
+ * Flush and drop the tracing guard. Must be called before process.exit()
+ * because Rust statics in OnceLock are never dropped, and the ChromeLayer
+ * FlushGuard only writes trace data to disk when dropped.
+ */
+export declare function shutdownTracing(): void;
+
 /**
  * Run a command with fspy tracking, callable from JavaScript.
  *