Historical 2026-08-06 evidence of a guild tracker becoming a player picker, in-game objective, and human-review evidence; current authority is comfy-quest.
Derek's call. Valheim ground is not flat and 89 beams on a hillside reads as broken rather than impressive, so the gallery brings its own floor. Deliberately not a disc - a 38 m disc is roughly 1100 tiles of which most are never walked on, whereas a plaza with eight spokes and eight pads is 499 and looks like a ritual floor rather than a car park, with the shape itself telling a visitor where to walk. Ring tightened from 46 m to 38 m so the spokes stay short while leaving 30 m of arc between monuments. The builder picks one world height for the whole platform - highest ground under the footprint plus clearance - so the floor is level where the terrain is not.
Derek's call, and the right tradeoff: a bigger download that gives value two minutes after install beats a smaller one that needs an hour of hunting creatures and crafting a bow. The gallery is eight rune monuments on a 46 m ring, a practice station under each, and an armoury at the centre so nothing must be found or made. The runes are raised from logs, and the beam positions are cut from the SAME segment table that draws the 14-pixel glyph in the panel - one shape at two scales, so a monument cannot end up a different shape from the page it belongs to. Emitted as generated data rather than numbers embedded in code, so the preview renders exactly what will be built.
A committed document is corrected rather than left standing: NETCODE-OWNERSHIP-MAP.md's headline that ZDO ownership is 100 percent server-authoritative through a single funnel is falsified by five verified client-side SetOwner sites (Ship, Sadle, Vagon, ArmorStand, ItemStand); its narrower ReleaseNearbyZDOS claim survives. OwnershipPinRunner was designed against that thesis and its selector has never been evaluated against a funnel it cannot see.
The Discord sync receipt shows exactly one pending change: the Recoverable pieces thread gains the dated update pointing at the re-landed raw material. The four tool threads stay blocked by design while provision.json site_base_url is null, so an apply cannot touch them. Applying remains operator-gated: apply --yes --expect-plan ba37ecab31d2.
plans/recoverable-pieces-landing-workbook.md records the reusable playbook the 2026-07-29 landings executed: three find-lanes anchored on d75ffb2/57654fd/ae81c83, the migrate-vs-document decision record, byte-exact landing mechanics with the sha proof, the doc-sync surface list, the verification suite, and a model-tier legend so deterministic tools and cheaper models carry the mechanical steps. Result ledger cites C1-C3.
The handoff block that goes to the agent updating the catalog page now states verified live facts instead of the pre-provisioning prediction: two threads posted, no member replies yet, nothing exported, and the candidate journal not yet existing. It calls out that five of the seven tools will carry a null discussion link until the catalog deploys and that one tool never gets a thread at all, so nulls read as the designed state rather than as missing data, and it records that the page generator already allowlists the forum's link host, so the thread URLs will render as live links.