Release v0.1.4 with terrain rescanning and owner-published map updates

docs/panorama-contributions.md

@@ -21,7 +21,16 @@ For an already published map, its approved name, description, panorama count, an
 
 ## Refresh guessing map
 
-**Map tools → Refresh guessing map** rebuilds only the overhead map through the worker. It consumes no panorama slots and leaves every panorama image unchanged. Choose the original capture, another processed capture you own, or an accepted contribution whose bounds and expected server address match the map exactly. To show new buildings, export and upload fresh terrain first. The published map and ongoing games keep their current image until a moderator approves the update.
+**Map tools → Refresh guessing map** rebuilds only the overhead map through the worker. It consumes no panorama slots and leaves every panorama image unchanged. Choose the original capture, another processed capture you own, or an accepted contribution whose bounds and expected server address match the map exactly. To show new buildings, export and upload fresh terrain first. The published map and ongoing games keep their current image until the owner publishes the finished update; ongoing games retain their original revision.
+
+New Fabric captures also record up to four surface layers from chunks already
+loaded by the client. The standalone worker renders those blocks using the same
+overhead renderer as plugin terrain, while the mod's panorama photographs remain
+unchanged. Use **Rescan terrain** and revisit changed areas before uploading;
+previously captured chunks remain available until they are rescanned. It does not
+request unexplored chunks; revisit existing areas to capture terrain for older mod maps. Earlier Fabric exports without terrain keep
+using their captured flat map. A standalone worker is required to process the new
+terrain exports; the image-only serverless processor leaves them queued for it.
 
 ## Player workflow
 
@@ -36,6 +45,20 @@ Both tools can contribute to either kind of map. The original surface map and bo
 
 ## Contribution server check
 
+Owners can enter up to ten connection addresses separated by commas, for example
+`play.example.com, mc.example.com:25566`. Matching any listed address is enough;
+the backend still checks every upload and retry. Older capture tools defer the
+alias check to the website. The updated tools check before uploading as well.
+
+For a map that is already published, its owner can save the draft and select
+**Publish update** to publish a validated revision without another moderator
+review. A new map still requires its initial review. This also publishes any
+player contributions the owner has already accepted into that draft.
+When uploading the owner's own contribution to an already published map, the
+contribution draft also offers **Update my map now**. It submits and accepts
+the owner's selected panoramas and publishes the update together; it refuses to
+run while the parent map has other unpublished edits.
+
 Each map has a separate **Contribution server address** setting. New maps use the address recorded by their capture tool. Existing maps with a valid captured address are initialized from their own manifest. Maps whose old exports contain no address show **Server check is off** until the owner enters one.
 
 When contributions are enabled, the map page shows that address. The owner can correct it in the dashboard, including a custom port. **Clear address and turn off check** removes the displayed address and permits submissions without matching a server. Clearing does not skip owner approval or moderator review.