The MCP server gains a second session, --browser: the game in the player's tab, reached through the
agent relay npm run dev hosts at /agent (loopback unless --host; Host and Origin checked, no token).
The player turns it on in Settings → Agent API, a section only the development page has, and picks the
clock: a pace of 30 s to 5 min a day that nobody can pause, or the agent's own. Headless gets the
running clock too (--clock realtime --pace MS) and both get a wait tool.
All of it lives in src/agent/ (development page only). The game offers HOOKS, UI.clockLocked,
setSpeed() and runClock(dt), the frame's day block moved out unchanged, and nothing more: the page
players get grows by under 1 KB gzipped and runs exactly as before.
scripts/mcp.js registers the same tools on @modelcontextprotocol/server (2.4.0, with
@modelcontextprotocol/node 2.1.2 for node:http; dev dependencies, pinned) instead of its own JSON-RPC
loop. stdio works as before; --http [HOST:]PORT serves Streamable HTTP at /mcp, on loopback unless
told otherwise.
Over HTTP every request's Host must be an address of this machine (or --allow-host), an Origin other
than localhost is refused, and a bearer token (SOT_MCP_TOKEN or --token-file) is optional; bound
beyond loopback without one, the server warns. load_save and export_save take JSON only there, or files
under --save-dir and nowhere else. Calls from every client run one at a time, in order.
npm run perf -- --browser times the same workloads in Chromium as a desktop
and as a phone (390x844 at 3x, CPU slowed 4x), one browser per version. Each
run collects garbage first and ends by forcing layout and the map canvas, so
deferred work counts. The jsdom DOM is about 30x slower than a browser's and
has no layout, so the interface rows need this.
Shared machines swing single runs by 30% on identical code, CPU time
included. A row now counts as slower or faster only when it moved 15% and a
Mann-Whitney U test gives p < 0.01 (15 runs a side by default). Identical
code: no flags in three full runs; a routing slowdown planted in a copy is
flagged in jsdom and on the phone.
The panel workload renders both selections every run instead of alternating,
which split its samples in two. CI drives the runner's Chrome through
playwright-core, no browser download.
The world layer only includes cables below zoom 1.7, but drawCables
skipped its own lines whenever any cached layer existed, so zoomed in
nobody drew them. The layer now records whether it holds the cables.
A goal to build your first scrubbing center, and badges for weathering an
attack, holding a multi-terabit flood, running a clean-pipe or a sacrificial
PNI, blackholing your own city, and landing a HackBack that works. New stats
track the hold/monster/hack-win counts; Italian and a test included.
Rounds out the DDoS toolbox. Scrubbing centers come in 100G/1T/10T tiers and
clean only up to their capacity; always-on or cheaper on-demand (which lags a
couple of days). A transit clean-pipe add-on scrubs a flood upstream before it
reaches you. A Chinese PNI can be marked sacrificial: a flood over it dies on
the small port instead of the core, at the cost of half its legit capacity. A
new IX-blackhole mitigation drops about half the junk while keeping the victim
up. Selling DDoS protection now carries an SLA penalty when a protected
customer still goes down. Italian and tests included.
Flowspec was a flat network-wide licence. In reality the drop rules live in
hardware TCAM, and the budget differs by platform, so flowspec is now a
router-model capability: none on the used Rusty, a little on merchant-silicon
and whitebox models, full on the big chassis. The flood is filtered only where
the attacked POP's router can do it, and a bigger TCAM knocks it down further.
The licence is gone; the NOC shows how many POPs are capable and the attack
panel names the chassis doing the filtering.
DDoS was one flat random event. Now each attack has a vector (DNS, NTP,
CLDAP, SYN, HTTP), a size from a few Gbps to a multi-terabit monster, a
target POP, a duration and an entry point among that city's uplinks.
The NOC grows a live attack panel and a toolbox: RTBH (free, instant, but
the victim goes dark too), a one-time Flowspec licence that drops known UDP
floods at the edge but cannot touch an HTTP flood, the existing scrubbing
center, and HackBack 3000, which sometimes ends the attack and often
flattens an innocent for a fine. New Vigilante and Collateral Damage badges,
Italian translations, and tests for the attack, each tool and old saves.
Fabric customers buy transit, or a circuit to one of your POPs, over
Megapork, PocketFabric or Consolation Connect. They come in through your
NNI port in their city and count against its capacity.
Zoomed out, cities become dots and POPs small router pills with thinner
links and fewer labels. Up close a POP shows the router instead of the
skyline, with a router B for a second site. Parallel waves on one cable
draw as one line with a combined label. POPs can be decommissioned one at
a time or in bulk, with early-termination penalties for affected
customers. Dark fiber panels can add parallel links. NLNOG Day joins the
conferences.
Closes#37Closes#19Closes#32