ci: switch npm publish to OIDC trusted publishing (#8454)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

crates/goose-acp/acp-schema.json

@@ -436,7 +436,6 @@
         },
         "messageCount": {
           "type": "integer",
-          "format": "uint64",
           "minimum": 0
         }
       },

crates/goose-acp/src/bin/generate_acp_schema.rs

@@ -38,8 +38,12 @@ fn main() {
     // Replace `true` with `{}` throughout $defs. Both mean "accept any value" in
     // JSON Schema, but many TS codegen tools (e.g. @hey-api/openapi-ts Zod plugin)
     // silently drop properties whose schema is the bare `true` literal.
+    //
+    // Also strip "format": "uint64" / "int64" from integer types — these cause TS
+    // codegen to emit BigInt validators, but JS/TS uses `number` for all integers.
     for def in defs.values_mut() {
         replace_true_schemas(def);
+        strip_integer_formats(def);
     }
 
     // Annotate $defs entries with x-method/x-side. Only set x-method for types
@@ -189,6 +193,30 @@ fn main() {
     println!("{json_str}");
 }
 
+/// Recursively strip `"format"` from integer-typed schemas.
+///
+/// schemars emits `"format": "uint64"` / `"int64"` etc. for Rust integer types.
+/// TS codegen tools interpret these as BigInt, but JS/TS uses `number` everywhere.
+fn strip_integer_formats(value: &mut Value) {
+    match value {
+        Value::Object(map) => {
+            let is_integer = map.get("type").and_then(|v| v.as_str()) == Some("integer");
+            if is_integer {
+                map.remove("format");
+            }
+            for v in map.values_mut() {
+                strip_integer_formats(v);
+            }
+        }
+        Value::Array(arr) => {
+            for v in arr.iter_mut() {
+                strip_integer_formats(v);
+            }
+        }
+        _ => {}
+    }
+}
+
 /// Recursively replace `true` with `{}` in a JSON value.
 ///
 /// In JSON Schema, `true` and `{}` both mean "accept any value", but many