Change default server port to 2900 and bump Node to 24

Replace the default KalamDB HTTP API port 8080 with 2900 across docs, examples, tests, CI workflows, agent metadata, and configs. Update related server checks, CLI envs, and sample code to use the new API port; adjust cluster RPC/API settings in release workflow (rpc port updated to 2910, api addr to 2900). Also bump GitHub Actions Node.js setup from Node 22 to Node 24 in multiple workflows and add the 'react' package to the typescript-sdk test matrix. Miscellaneous housekeeping updates to keep documentation and test harnesses consistent with these defaults.

Author: jamals86

.agents/skills/rust-skills/rules/api-default-impl.md

@@ -81,7 +81,7 @@ impl Default for Connection {
     fn default() -> Self {
         Connection {
             host: "localhost".to_string(),
-            port: 8080,
+            port: 2900,
             timeout: Duration::from_secs(30),
         }
     }

.agents/skills/rust-skills/rules/api-typestate.md

@@ -87,12 +87,12 @@ impl Connection<Authenticated> {
 
 // Bug: forgot to authenticate
 let conn = Connection::new();
-let conn = conn.connect("server:8080")?;
+let conn = conn.connect("server:2900")?;
 conn.send(b"data");  // Compile error! send() not available on Connection<Connected>
 
 // Correct usage
 let conn = Connection::new();
-let conn = conn.connect("server:8080")?;
+let conn = conn.connect("server:2900")?;
 let mut conn = conn.authenticate("secret")?;
 conn.send(b"data")?;  // Works - type is Connection<Authenticated>
 ```

.agents/skills/rust-skills/rules/async-cancellation-token.md

@@ -94,7 +94,7 @@ let child = token.child_token();
 
 ```rust
 async fn run_server(shutdown: CancellationToken) {
-    let listener = TcpListener::bind("0.0.0.0:8080").await?;
+    let listener = TcpListener::bind("0.0.0.0:2900").await?;
 
     loop {
         tokio::select! {

.agents/skills/rust-skills/rules/doc-hidden-setup.md

@@ -131,7 +131,7 @@ For examples that shouldn't run in tests:
 /// ```no_run
 /// # use my_crate::Server;
 /// // This would actually start a server - don't run in tests
-/// let server = Server::bind("0.0.0.0:8080").await?;
+/// let server = Server::bind("0.0.0.0:2900").await?;
 /// server.run().await?;
 /// # Ok::<(), my_crate::Error>(())
 /// ```

.agents/skills/rust-skills/rules/err-expect-bugs-only.md

@@ -114,14 +114,14 @@ let port: u16 = input.parse().expect("Invalid port");
 let port: u16 = input.parse().map_err(|_| ConfigError::InvalidPort)?;
 
 // Do: Provide default
-let port: u16 = input.parse().unwrap_or(8080);
+let port: u16 = input.parse().unwrap_or(2900);
 
 // Do: Handle explicitly
 let port: u16 = match input.parse() {
     Ok(p) => p,
     Err(_) => {
         log::warn!("Invalid port '{}', using default", input);
-        8080
+        2900
     }
 };
 ```

.agents/tasks/performance-profiling.md

@@ -25,7 +25,7 @@ Iteratively identify and fix INSERT hot-path bottlenecks using Jaeger distribute
 
 ### Step 1: Run Benchmark
 ```bash
-cd cli && KALAMDB_SERVER_URL="http://127.0.0.1:8080" KALAMDB_ROOT_PASSWORD="kalamdb123" \
+cd cli && KALAMDB_SERVER_URL="http://127.0.0.1:2900" KALAMDB_ROOT_PASSWORD="kalamdb123" \
   cargo test --features e2e-tests --test smoke smoke_test_insert_throughput_summary -- --nocapture
 ```
 
@@ -91,7 +91,7 @@ Common fixes:
 ### Step 6: Rebuild & Re-run
 ```bash
 # Kill server
-lsof -i :8080 -t | xargs kill
+lsof -i :2900 -t | xargs kill
 
 # Rebuild (incremental)
 cd backend && cargo build --bin kalamdb-server
@@ -100,7 +100,7 @@ cd backend && cargo build --bin kalamdb-server
 cargo run --bin kalamdb-server &
 
 # Wait for startup
-sleep 10 && curl -s http://127.0.0.1:8080/health
+sleep 10 && curl -s http://127.0.0.1:2900/health
 
 # Re-run benchmark (Step 1)
 ```

.github/agents/kalamdb-release-server-check.agent.md

@@ -1,14 +1,14 @@
 ---
 name: "KalamDB Release Server Checker"
-description: "Use when checking the KalamDB server end-to-end, reusing an existing healthy server on 127.0.0.1:8080 when present, otherwise starting a release server, wiring cli/.env, running cli/run-tests.sh, recording failures, fixing them one-by-one, and confirming the requested server check passes."
+description: "Use when checking the KalamDB server end-to-end, reusing an existing healthy server on 127.0.0.1:2900 when present, otherwise starting a release server, wiring cli/.env, running cli/run-tests.sh, recording failures, fixing them one-by-one, and confirming the requested server check passes."
 tools: [execute, read, edit, search, todo]
-argument-hint: "Describe what to verify, whether to reuse an existing 8080 server, any custom port/password, and whether the server should stay running after the check."
+argument-hint: "Describe what to verify, whether to reuse an existing 2900 server, any custom port/password, and whether the server should stay running after the check."
 user-invocable: true
 ---
-You are a specialist for KalamDB release-mode server validation. Your job is to validate KalamDB against a live server, preferably by reusing an already-running healthy server on `127.0.0.1:8080`. When no suitable 8080 server exists, start a real `cargo run --release --bin kalamdb-server`, point the CLI test harness at the chosen server through `cli/.env`, run `cli/run-tests.sh`, record failures, fix them one-by-one with narrow reruns, and prove the requested validation scope passes.
+You are a specialist for KalamDB release-mode server validation. Your job is to validate KalamDB against a live server, preferably by reusing an already-running healthy server on `127.0.0.1:2900`. When no suitable 2900 server exists, start a real `cargo run --release --bin kalamdb-server`, point the CLI test harness at the chosen server through `cli/.env`, run `cli/run-tests.sh`, record failures, fix them one-by-one with narrow reruns, and prove the requested validation scope passes.
 
 ## Constraints
-- DO NOT start a second backend if a single healthy KalamDB server is already listening on `127.0.0.1:8080`; reuse it.
+- DO NOT start a second backend if a single healthy KalamDB server is already listening on `127.0.0.1:2900`; reuse it.
 - DO NOT validate server behavior against a debug build.
 - DO NOT skip starting or verifying a live server process before running CLI tests.
 - If you start a new backend, DO NOT use `KALAMDB_STORAGE_DATA_PATH`; use `KALAMDB_DATA_DIR`.
@@ -25,10 +25,10 @@ You are a specialist for KalamDB release-mode server validation. Your job is to
 1. Determine the requested validation scope.
 If the user asked for a broad server check, run the full `cli/run-tests.sh` flow. If they asked for a narrower validation, honor that with the smallest matching `run-tests.sh` arguments.
 2. Choose the server target before starting anything new.
-Check `127.0.0.1:8080` first.
+Check `127.0.0.1:2900` first.
 - If exactly one healthy KalamDB server is already there, reuse it instead of starting a second backend.
 - Prefer proving from the process command, startup logs, or binary path that it is a release server. If it is clearly a debug binary or clearly not KalamDB, treat it as unsuitable.
-- Only start a new backend when `8080` is unused or the existing target is unsuitable.
+- Only start a new backend when `2900` is unused or the existing target is unsuitable.
 3. If you must start a new backend, start it correctly in release mode.
 Use `cd backend && cargo run --release --bin kalamdb-server`, adding an explicit port override only when needed to avoid conflicts.
 - Use a clean temp `KALAMDB_DATA_DIR`.
@@ -65,7 +65,7 @@ Unless the user asked to keep the server running, stop the server process after
 
 ## Output Format
 Return:
-- whether you reused an existing `127.0.0.1:8080` server or started a new one
+- whether you reused an existing `127.0.0.1:2900` server or started a new one
 - the exact release server command used
 - the `cli/.env` values you set or changed
 - the exact discovery, narrow rerun, and final `cli/run-tests.sh` command(s) used
@@ -74,8 +74,8 @@ Return:
 - whether the server is still running or was stopped
 
 ## Conflict Handling
-- If a healthy KalamDB server is already running on `127.0.0.1:8080`, reuse it instead of starting a second backend.
-- If an existing `8080` server is clearly unsuitable, say exactly why and only start a new release server when necessary.
+- If a healthy KalamDB server is already running on `127.0.0.1:2900`, reuse it instead of starting a second backend.
+- If an existing `2900` server is clearly unsuitable, say exactly why and only start a new release server when necessary.
 - If the root password or server URL cannot be determined safely, say exactly what is missing instead of guessing.
 - If a compile failure blocks test discovery, treat that compile failure as the first remembered failure and fix it before resuming discovery.
 - If a failure is outside the requested scope but blocks the requested validation, call that out explicitly and explain why it is a blocker.

.github/workflows/ci.yml

@@ -366,10 +366,10 @@ jobs:
         with:
           toolchain: ${{ env.RUST_VERSION }}
 
-      - name: Setup Node 22
+      - name: Setup Node 24
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
 
       - name: Install cargo-license
         shell: bash

.github/workflows/dart-sdk.yml

@@ -176,7 +176,7 @@ jobs:
           KALAMDB_SERVER_LOG="$PWD/dart-sdk-server.log" \
           KALAMDB_SERVER_PID_FILE="$SERVER_WORK_DIR/server.pid" \
           KALAMDB_SERVER_WAIT_SECONDS="120" \
-          KALAMDB_URL="http://localhost:8080" \
+          KALAMDB_URL="http://localhost:2900" \
           bash scripts/start-sdk-test-server.sh
           echo "SERVER_PID=$(cat "$SERVER_WORK_DIR/server.pid")" >> "$GITHUB_ENV"
 
@@ -186,7 +186,7 @@ jobs:
         shell: bash
         working-directory: link/sdks/dart
         env:
-          KALAMDB_URL: "http://localhost:8080"
+          KALAMDB_URL: "http://localhost:2900"
           KALAMDB_USER: "admin"
           KALAMDB_PASSWORD: "kalamdb123"
           KALAMDB_ROOT_PASSWORD: "kalamdb123"

.github/workflows/react-e2e.yml

@@ -29,7 +29,7 @@ env:
   CARGO_TERM_COLOR: always
   RUST_VERSION: "1.92.0"
   WASM_PACK_VERSION: "0.14.0"
-  KALAMDB_URL: "http://127.0.0.1:8080"
+  KALAMDB_URL: "http://127.0.0.1:2900"
 
 jobs:
   e2e:
@@ -57,7 +57,7 @@ jobs:
       - name: Setup Node
         uses: actions/setup-node@v5
         with:
-          node-version: '20'
+          node-version: '24'
 
       - name: Setup Rust
         uses: dtolnay/rust-toolchain@stable