Bump Rust toolchain to 1.98.1

Cargo.toml

@@ -8,7 +8,7 @@ edition = "2024"
 license = "MIT"
 repository = "https://github.com/AdaWorldAPI/a2ui-rs"
 authors = ["AdaWorldAPI"]
-rust-version = "1.95"
+rust-version = "1.98.1"
 
 # ── The fork, named ONCE, with no version anywhere ───────────────────────────
 #

Dockerfile.railway

@@ -47,7 +47,7 @@
 # TOOLCHAIN — 1.98.1 by ALIGNMENT, not by necessity. CLAUDE.md documents
 # `cargo +1.98.1` as this workspace's toolchain, so the image uses it and one
 # version holds everywhere. What this pin is NOT is a floor: the crate declares
-# `rust-version = "1.95"` and genuinely builds and tests green on 1.95.0 with
+# `rust-version = "1.98.1"` and genuinely builds and tests green on 1.98.1 with
 # every dependency present (measured, see the CORRECTION above). A newer
 # toolchain always works, so alignment is free — but do not cite this line as
 # evidence that something requires 1.98.1. If the floor ever really does rise,
@@ -72,6 +72,13 @@
 # while its same-numbered image tag is absent, and a Dockerfile that conflates
 # them inherits an availability constraint it never meant to take on.
 #
+# (2026-09-25: the 1.98.1 tags now exist — `rust:1.98.1`, `rust:1.98.1-bookworm`
+# and `rust:1.98.1-slim-bookworm` are all HTTP 200 as of today. The 404 above
+# was real when this file was written; docker-library has since published the
+# point-release tags it was lagging. The MINOR-tag float below is still kept
+# on purpose — see the "Consequence worth stating" paragraph — but the ARG is
+# now set to the exact patch tag since it exists.)
+#
 # (The failure surfaces confusingly: BuildKit resolves every stage's base in
 # parallel, so the last line printed is often the HEALTHY one —
 # `load metadata for docker.io/library/debian:bookworm-slim`, which resolves
@@ -96,7 +103,7 @@
 # (1.98 -> 1.99), and never to a patch-level tag — that is the shape that
 # broke.
 
-ARG RUST_IMAGE_TAG=1.98-slim-bookworm
+ARG RUST_IMAGE_TAG=1.98.1-slim-bookworm
 ARG BIN_NAME=a2ui-paint-web
 
 # ── builder ────────────────────────────────────────────────────────────────

Dockerfile.solid.railway

@@ -31,7 +31,7 @@
 # have no GPU and this tier does not want one.
 #
 # TOOLCHAIN — 1.98.1 by ALIGNMENT, not necessity, exactly as in the paint
-# image. The crates declare `rust-version = "1.95"` and build green there; the
+# image. The crates declare `rust-version = "1.98.1"` and build green there; the
 # pin matches the toolchain CLAUDE.md documents so one version holds across the
 # workspace. Do not cite this line as evidence that something requires 1.98.1.
 # ---------------------------------------------------------------------------
@@ -53,6 +53,13 @@
 # while its same-numbered image tag is absent, and a Dockerfile that conflates
 # them inherits an availability constraint it never meant to take on.
 #
+# (2026-09-25: the 1.98.1 tags now exist — `rust:1.98.1`, `rust:1.98.1-bookworm`
+# and `rust:1.98.1-slim-bookworm` are all HTTP 200 as of today. The 404 above
+# was real when this file was written; docker-library has since published the
+# point-release tags it was lagging. The MINOR-tag float below is still kept
+# on purpose — see the "Consequence worth stating" paragraph — but the ARG is
+# now set to the exact patch tag since it exists.)
+#
 # (The failure surfaces confusingly: BuildKit resolves every stage's base in
 # parallel, so the last line printed is often the HEALTHY one —
 # `load metadata for docker.io/library/debian:bookworm-slim`, which resolves
@@ -77,7 +84,7 @@
 # (1.98 -> 1.99), and never to a patch-level tag — that is the shape that
 # broke.
 
-ARG RUST_IMAGE_TAG=1.98-slim-bookworm
+ARG RUST_IMAGE_TAG=1.98.1-slim-bookworm
 ARG BIN_NAME=a2ui-solid-web
 
 # ── builder ────────────────────────────────────────────────────────────────