An aggregates-only telemetry API with privacy tests that fail if a player ID, name, or position ever shows up — plus the whole stack, runnable on your machine.
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.
Gateway, Companion, P7 infrastructure, live FieldLab harnesses, and the roadmap journal now live in djcdevelopment/lumberjacks-platform. The roadmap command and pre-commit ceremony move with that implementation authority; baseline remains the evidence archive and fleet index rather than a source fallback.
Quest glue and transport contracts now travel as source packages (Comfy.Quest.Contracts, Comfy.Transport.Contracts); the fused test project split along the quest seam with count conservation (166+185=351); Quest Studio carved behind IQuestStudioHost with route parity 10/10; cross-seam scripts parameterized behavior-preserving. Extraction of networksense, lumberjacks-platform, and comfy-quest can now proceed from one green tag.
Split browser authoring, compact gameplay runtime, and Quest Lab rehearsal around one certified file contract; OMEN listen-host mutation passed while the identical i5 peer failed closed.
Curation is now measured instead of vibes: a depth veto catches camera-against-wall frames with zero keeper loss, and the notebook lets the operator move thresholds and watch winners reorder
The generated Workbench now carries a production provenance stamp for the committed audience vocabulary, catalog, and renderer instead of a preview stamp. The companion corpus projections were rebuilt after the deployment record, keeping the public index and roadmap adapter byte-current with their authoritative journal.
Cut m31-questlab-20260808-r1, shipped it to AM4 with the new isolate deploy lane, recreated lj-workbench on it, and published. The download streams 74949 bytes at d49a20db and /questlab serves the real tome from the mount with X-QuestLab-Sha256 equal to the committed file. THE ACTUAL BLOCKER was neither the image nor the publish: Tailscale Funnel sends / to Caddy on 8190, and Caddy forwards a deliberate allowlist of paths to the Gateway, answering an honest 404 for everything else so that /ops/* is never funneled. The container answered /questlab correctly for twelve minutes while the origin still 404d. Adding /questlab to the @public matcher and reloading was the fix; the boundary was re-checked afterwards and still holds, /ops/* 403 and unmatched 404. That Caddyfile is host-only config carrying bcrypt credentials, so only the mechanism is documented, in START-HERE, in the publish script header, and in the deploy lane README where somebody adding a route will actually look. Also learned: questlab.html and workbench.html are not baked into the image at all -- both have always been served from the mount, and the fallback page is what /questlab served in the gap.