docs(readme): protocol 4, and module-uo v1.0.1 in the quick start #4

wtclaude · 2026-08-19T22:59:47Z

wtclaude commented

2026-08-19 22:59:47 +00:00

Phase 0 of the runicgateway.com plan, conflict 4. Pairs with docs#172, which fixes the same protocol number in INTEGRATION.md, INSTALL.md and v4.md.

This page is the project's front door — it renders at gitea.whitlocktech.com/RunicGateway — and both of its copy-pasteable values were stale.

The installer handoff block printed Protocol version 3. That block exists to be typed into Admin → Shard. Protocol 4 shipped 2026-08-19 as sidecar v2.0.0 and overlay v1.0.0, and a stale number there comes back from the sidecar as a 409 — which INSTALL.md's own troubleshooting table notes "looks exactly like your shard going offline".

The module quick start still pointed at v0.3.0 — both the install-manifest URL and the MODULES=uo@0.3.0=… example. module-uo is on v1.0.1; I verified the asset name (module-uo-1.0.1.json) against the release rather than assuming the naming pattern held.

Three lines, no structural change.

AI-assisted contribution

Drafted by Claude (Claude Code), per the org's AI-usage disclosure policy. Commit carries the Co-Authored-By trailer.

Phase 0 of the [runicgateway.com plan](https://gitea.whitlocktech.com/RunicGateway/runicgateway.com/pulls/2), conflict 4. Pairs with [docs#172](https://gitea.whitlocktech.com/RunicGateway/docs/pulls/172), which fixes the same protocol number in `INTEGRATION.md`, `INSTALL.md` and `v4.md`. This page is the project's front door — it renders at `gitea.whitlocktech.com/RunicGateway` — and both of its copy-pasteable values were stale. **The installer handoff block printed `Protocol version 3`.** That block exists to be typed into Admin → Shard. Protocol 4 shipped 2026-08-19 as sidecar v2.0.0 and overlay v1.0.0, and a stale number there comes back from the sidecar as a `409` — which `INSTALL.md`'s own troubleshooting table notes "looks exactly like your shard going offline". **The module quick start still pointed at v0.3.0** — both the install-manifest URL and the `MODULES=uo@0.3.0=…` example. `module-uo` is on **v1.0.1**; I verified the asset name (`module-uo-1.0.1.json`) against the release rather than assuming the naming pattern held. Three lines, no structural change. ## AI-assisted contribution Drafted by Claude (Claude Code), per the org's AI-usage disclosure policy. Commit carries the `Co-Authored-By` trailer.

wtclaude added 1 commit 2026-08-19 22:59:49 +00:00

docs(readme): protocol 4, and module-uo v1.0.1 in the quick start 327bb68091

The landing page is the project's front door, and both of its
copy-pasteable values were stale.

The installer handoff block printed "Protocol version 3". That block
exists to be typed into Admin -> Shard, and protocol 4 shipped on
2026-08-19 as sidecar v2.0.0 and overlay v1.0.0. A stale number there
comes back from the sidecar as a 409, which INSTALL.md's own
troubleshooting table notes "looks exactly like your shard going
offline".

The module quick start still pointed at the v0.3.0 install manifest and
MODULES=uo@0.3.0. module-uo is on v1.0.1; asset names verified against
the release.

Co-Authored-By: Claude <noreply@anthropic.com>

whitlocktech merged commit c9ba2d2fd3 into main

2026-08-19 23:26:09 +00:00

whitlocktech deleted branch docs/protocol-4-and-versions

2026-08-19 23:26:10 +00:00

whitlocktech referenced this issue from a commit

2026-08-19 23:26:11 +00:00

Merge pull request 'docs(readme): protocol 4, and module-uo v1.0.1 in the quick start' (#4) from docs/protocol-4-and-versions into main

wtclaude referenced this pull request from RunicGateway/runicgateway.com

2026-08-19 23:42:10 +00:00

docs(plan): D13 settles the contact address, and Phase 0 is done #3

Sign in to join this conversation.