diff --git a/README.md b/README.md
index a40712a..08c8b9b 100644
--- a/README.md
+++ b/README.md
@@ -115,12 +115,12 @@ Publishing is merge-driven; there is no release tag to push. On every push to
 `main`, [`Package Release`](.github/workflows/package-release.yaml) calls
 rainix's `rainix-autopublish`, which compares the package content against the
 latest published revision. If it differs, it runs
-`forge soldeer push rain-solmem~<version>`, tags `sol-v<version>`, and commits a
-bump of `[package] version` back to `main`.
+`forge soldeer push rain-solmem~<version>` and tags `sol-v<version>`.
 
-`[package] version` in `foundry.toml` is the **next, unpublished** version, not
-the current one. It is always one ahead of the registry; do not "correct" it to
-match.
+The publish version is derived from the Soldeer registry and git tags, never
+from `foundry.toml`: it is the semver max of a patch bump of the newest
+published version and the newest `next-v<x.y.z>` tag merged into the pushed
+head. Push a `next-v<x.y.z>` tag to request a deliberate minor or major jump; the tag is read only when a push to `main` runs the workflow, so it must already be merged into the pushed head — a tag-only push publishes nothing.
 
 Everything [`.soldeerignore`](.soldeerignore) does not exclude ships — `src/**`,
 `README.md`, `LICENSE`, `LICENSES/`, `REUSE.toml` — and any change to it
diff --git a/foundry.toml b/foundry.toml
index e8de1cc..a42a6b5 100644
--- a/foundry.toml
+++ b/foundry.toml
@@ -1,11 +1,3 @@
-# Release metadata, not foundry config. `rainix-autopublish` reads `version` as
-# the next, unpublished Soldeer release and rewrites it when it publishes.
-# `[external.*]` is the section foundry reserves for another tool's config and
-# ignores; any other unreserved section it reads as a profile and warns about.
-[external.package]
-name = "rain-solmem"
-version = "0.1.27"
-
 [profile.default]
 
 # See more config options https://github.com/foundry-rs/foundry/tree/master/config