diff --git a/README.md b/README.md
index 858d2621f..d69535604 100644
--- a/README.md
+++ b/README.md
@@ -76,12 +76,13 @@ bun run dev                     # open the address it prints: that page is the P
 **2. Build.** The built maps are already in the repo. After a change, rebuild just that map, or all of them:
 
 ```bash
-BUNDLE=<map> bun x vite build && bun run fix:sri   # one map, then refresh its integrity hashes
-BUILD_ALLOW=1 bun run build                        # every map (~4 min); the output is public/dx-maps/
+BUNDLE=<map> bun x vite build && bun run tree && bun run fix:sri   # one map, then its pages and hashes
+BUILD_ALLOW=1 bun run build                                         # every map (~4 min); the output is public/dx-maps/
 ```
 
-Skip `fix:sri` after a one-map build and the map's own page and any pasted snippet refuse the new file, because
-they still carry the old integrity hash. When the DX Life site's repo sits next to this one (`../doxa-life`), the full build also copies the maps into
+After a one-map build, `bun run tree` rewrites the map's pages and the manifest (a changed `.meta.json` reaches
+them only this way), and `fix:sri` refreshes their integrity hashes. Skip them and the map's own page and any pasted
+snippet keep the old settings and refuse the new file. When the DX Life site's repo sits next to this one (`../doxa-life`), the full build also copies the maps into
 its `public/`. That is the one path set in `vite.doxa-maps-build-config.json` (`dropin.dest`); nothing else on
 your computer is searched. No site there: the step says so and skips. `DOXA_DROPIN=off` turns it off, and
 `bun run dropin` copies on demand.