MK301 greps .lua/.json bodies for the generated-tree paths, so the
comment explaining how to match a template offline read exactly like a
real load path. Nothing here ever opened that tree -- the probe walks
the live map through the engine -- so describe the tables instead and
point at tools/voxel-survey.md, which keeps the literal paths because
the gate exempts .md and .py.
Prints the building models built and the tiles objects claimed. The
comment carries the trap it cost me: Buildings.stats() is the module's
memoisation cache, global and cumulative for the session, so it reads
as "a foreign building stamped here" when nothing of the sort happened.
Match template grids offline against maps.lua instead -- and remember a
drawing can straddle a map boundary, as the Pokemon Tower's does.
DramaticShape