READMEs: capture the server PID instead of relying on job control

`kill %1` assumes the server is the only background job; `SERVER_PID=$!`
plus `kill "$SERVER_PID"` is the same one-line recipe but immune to
whatever else the shell has running.

Author: maxisbey

examples/stories/bearer_auth/README.md

@@ -15,12 +15,13 @@ authorization server; see `../oauth/` for the full grant flow.
 ```bash
 # start the bearer-gated server (real uvicorn on :8000)
 uv run python -m stories.bearer_auth.server --port 8000 &
+SERVER_PID=$!
 
 # connect with the demo bearer token
 uv run python -m stories.bearer_auth.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.bearer_auth.server_lowlevel --port 8000 &
 uv run python -m stories.bearer_auth.client --http http://127.0.0.1:8000/mcp
 ```

examples/stories/dual_era/README.md

@@ -12,10 +12,11 @@ stays era-agnostic.
 ```bash
 # over HTTP — the same /mcp endpoint serves both eras
 uv run python -m stories.dual_era.server --http --port 8000 &
+SERVER_PID=$!
 uv run python -m stories.dual_era.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.dual_era.server_lowlevel --http --port 8000 &
 uv run python -m stories.dual_era.client --http http://127.0.0.1:8000/mcp
 ```

examples/stories/legacy_routing/README.md

@@ -17,10 +17,11 @@ browser-based MCP clients need.
 ```bash
 # HTTP only — the predicate is an HTTP-transport concern
 uv run python -m stories.legacy_routing.server --port 8000 &
+SERVER_PID=$!
 uv run python -m stories.legacy_routing.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.legacy_routing.server_lowlevel --port 8000 &
 uv run python -m stories.legacy_routing.client --http http://127.0.0.1:8000/mcp
 ```

examples/stories/oauth_client_credentials/README.md

@@ -11,10 +11,11 @@ discovery → token POST → Bearer attachment automatically.
 ```bash
 # start the server (real uvicorn on :8000 — auth is HTTP-only)
 uv run python -m stories.oauth_client_credentials.server --port 8000 &
+SERVER_PID=$!
 uv run python -m stories.oauth_client_credentials.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.oauth_client_credentials.server_lowlevel --port 8000 &
 uv run python -m stories.oauth_client_credentials.client --http http://127.0.0.1:8000/mcp
 ```

examples/stories/reconnect/README.md

@@ -11,10 +11,11 @@ traffic and has `server_info` / `server_capabilities` available immediately.
 ```bash
 # over HTTP — Streamable HTTP only; in-memory has no "round-trip" to skip
 uv run python -m stories.reconnect.server --http --port 8000 &
+SERVER_PID=$!
 uv run python -m stories.reconnect.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.reconnect.server_lowlevel --http --port 8000 &
 uv run python -m stories.reconnect.client --http http://127.0.0.1:8000/mcp
 ```

examples/stories/stateless_legacy/README.md

@@ -13,12 +13,13 @@ wiring, no era flag. The client connects once per era and asserts the same
 ```bash
 # start the server (real uvicorn on :8000)
 uv run python -m stories.stateless_legacy.server --port 8000 &
+SERVER_PID=$!
 
 # connect once as a modern client and once as a legacy client
 uv run python -m stories.stateless_legacy.client --http http://127.0.0.1:8000/mcp
 
 # lowlevel server variant — same port, so stop the first server
-kill %1
+kill "$SERVER_PID"
 uv run python -m stories.stateless_legacy.server_lowlevel --port 8000 &
 uv run python -m stories.stateless_legacy.client --http http://127.0.0.1:8000/mcp
 ```