The updates feed keeps its addresses, and carries contract versions

Each item in the updates feed now has a permanent address: its own page under /updates. It used to carry a number that shifted every time something new shipped, so feed readers showed old items as new again, and the links went nowhere. Because every address changed this once, your reader may show the newest 50 items as new one last time. The feed now includes the tool contract versions beside the product updates, holds the newest 50, and has a JSON Feed twin at /feed.json. Also in this release: the public card pages and the collection-efficiency numbers are served from the edge cache instead of being worked out again on every visit; a deploy no longer removes files that an open console still needs; the "Publish your own stats" example points at an agent connection, since war history and standings are MCP tools the JSON API does not serve; and the game's river-race log is described as ten weeks, not twenty. No change to the tools.