fix: reorder shutdownTracing declaration to match NAPI-RS generation

NAPI-RS generates type declarations alphabetically, placing
shutdownTracing (s) after runCommand (r) and its interfaces.

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

Author: branchseer

packages/cli/binding/index.d.cts

@@ -267,13 +267,6 @@ 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.
  *
@@ -343,3 +336,10 @@ export interface RunCommandResult {
   /** Map of relative paths to their access modes */
   pathAccesses: Record<string, PathAccess>;
 }
+
+/**
+ * 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;