Fix i32 overflow in online status reporting for peers

.github/workflows/build.yaml

@@ -53,7 +53,7 @@ jobs:
       - name: Install toolchain
         uses: actions-rs/toolchain@v1
         with:
-          toolchain: "1.90"
+          toolchain: "stable"
           override: true
           default: true
           components: rustfmt
@@ -94,7 +94,7 @@ jobs:
       - name: Install toolchain
         uses: actions-rs/toolchain@v1
         with:
-          toolchain: "1.90"
+          toolchain: "stable"
           override: true
           default: true
           components: rustfmt

AGENTS.md

@@ -0,0 +1,17 @@
+# Repository Instructions
+
+## Rust Rules
+
+- In Rust code, do not introduce `unwrap()` or `expect()`.
+- Allowed exceptions:
+- Tests may use `unwrap()` or `expect()` when it keeps the test focused and readable.
+- Lock acquisition may use `unwrap()` only when the locking API makes that the practical option and the failure mode is poison handling rather than normal control flow.
+- Outside those exceptions, propagate errors, handle them explicitly, or use safer fallbacks instead of `unwrap()` and `expect()`.
+
+## Editing Hygiene
+
+- Do not introduce formatting-only changes.
+- Do not run repository-wide formatters or reflow unrelated code unless the
+  user explicitly asks for formatting.
+- Keep diffs limited to semantic changes required for the task.
+

CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md