docs(CH-035): publish Rumble documentation and open P-004

[flemming-n-larsen]

Acceptance brief

• Plan item: P-003/M-009 and successor plan P-004. Both remain wanted.
• Acceptance criteria: None added, retired, or materially changed; no scenario-resolution verdicts are required.
• Merge binds: CH-035’s published Rumble documentation, P-003 completion, and the draft P-004 hardening plan. The earlier documentation PR docs(CH-034): publish Rumble user documentation #250 is superseded. Accepted changes already on main, including CH-036/P-005, are retained.
• Documentation impact: ARCH-025 and the published Rumble guides are updated. No public API or runtime interface changes are introduced by CH-035.
• Verification: clue validate --forbid-changes, the repository Markdown local-link check, ./gradlew clean build, and ./gradlew :web:build pass.
• Review: in-context fallback, reviewed commit 40ecb0c9cedc3b2c3fee0414e42da2503ba97f95, pass 1, no blocking findings and no advisories.

Rumble user documentation (P-003/M-009)

This PR carries the documentation work originally proposed in PR #250, which is now superseded.

New quickstarts under web/docs/rumble/, one per audience, are wired into the VitePress navigation and sidebar:

• bot-author-guide.md: fork, add source, validate, open the PR, plus TwinDuel teams, ownership, versions, and slots.
• client-guide.md: register a client, build from source, check and synchronize, run one ranked battle, submit results.
• moderator-guide.md: review submissions and client registrations, handle disputes and abuse, keep the GitHub automation healthy.
• index.md: landing page.

The client guide describes the client's actual current pre-release state rather than an aspirational published-container flow. With M-009 done, all six P-003 milestones are done and P-003 becomes status: completed.

P-004 successor plan (CH-035)

Closing a plan does not close the system. Delivery work for P-003’s own milestones is still unmerged upstream, and hands-on testing after the V1 launch found defects that were never tracked. P-003 stays immutable as the launch record; P-004 carries the follow-up as its own campaign rather than reopening P-003.

ID	Milestone	Tracked in
M-011	In-flight P-003 delivery reconciled	This PR, plus rumble-client#9 awaiting a maintainer merge
M-012	Practice mode has a working CLI path	rumble-client#10
M-013	Catalog passes its own validator	rumble-bots#8
M-014	Documentation matches post-fix behavior	Gated on the others
M-015	Container image runs under rootless Podman	rumble-client#11

M-015 covers the concrete risk that docker/rumble.sh passes --user "$(id -u):$(id -g)" alongside bind mounts, which under rootless Podman can leave the mounted state directory unwritable. Podman is not becoming a second CI-tested runtime; the milestone asks for one deliberate manual pass and an honest written answer.

Review corrections included

• Submission trees put bot source under src/, matching the booter convention and live catalog bots.
• The client guide carries -PtankRoyaleSource and --no-configuration-cache on every Gradle invocation.
• The client guide explains that several game types cause the client to select the alphabetically first entry, and notes that battlesPerSession is unused by current commands.
• The moderator guide points bans at bannedAccounts and disqualifiedBots in rumble-data/bans.json.
• TwinDuel team members are identified by their name-and-version entries.

Per C-002, this PR requires a human merge.

🤖 Generated with Claude Code