Community Workbench

• Build one chart, tile, or widget from the public v0 API and post it good first picksmall
  Done when: Any stack you like — a static page, a spreadsheet, a terminal script — renders live data from a v0 endpoint, and the thread has a screenshot plus how you made it. Needs no repo access; the starter kit includes a Python poller. CT-1
• Bring the local stack up, then add one new aggregate tile the privacy tests still pass on medium
  Done when: The compose stack runs on your machine and a new aggregate is exposed by the v0 API and rendered, with the existing privacy tests passing unmodified. This is the claim path — the source is already public, so nothing blocks you from starting today. CT-2

At stage 3Commit access to the telemetry stack and the operator viewer in baseline, and you triage this tool's thread.

• Walk the join flow end-to-end as a tester and file friction notes small
  Done when: You went from invite link to a running modded client, and every point where you hesitated, guessed, or had to ask is written down in the thread — including the ones that turned out to be your fault. SJ-1
• Write the tester-facing FAQ from the friction notes medium
  Done when: A page answers the questions SJ-1 actually produced, in a tester's words rather than the operator's, and the next tester gets through without asking any of them. SJ-2

At stage 3Commit access to Lumberjacks/src/Game.Gateway/Valheim/ in baseline, and you triage this tool's thread.

• Bring the camera plugin into this repo so the capture half runs here medium
  Done when: The BepInEx plugin builds from a checkout of this repo and a capture run completes without reaching into the comfy archive. This is the claiming task for this tool. It supersedes the old CG-1, which asked for a waypoints sample from segment 1 — tools/selfie-stick/ already emits that. CG-1
• Resolve prefab hashes to names so a structure can be described by material small
  Done when: A one-time in-game dump of ZNetScene's prefab table lands as a committed lookup, and the scanner reports "dominant material: wood_wall" instead of "hash:538325542". The offline classification.json does not cover building pieces — it holds 617 item names and none of them are pieces. CG-2

At stage 3Commit access to the revived pipeline once it lands in baseline, and you triage this tool's thread. The comfy archive it is recovered from stays read-only.

• Prove the ported bridge live: one real in-game completion, EventLog to review record (design: ADR 0018) small
  Done when: A real in-game quest completion, produced by the live mod with QuestEvaluatorEnabled on, is fetched from the durable EventLog by tools/quest-bridge/fetch_completions.py and comes out as one human-readable review record with the quest's guild-command draft. The design call this task used to hide — re-materialize the old screenshot/trace evidence envelope, or accept a thinner record — is decided in ADR 0018 (the EventLog row is the evidence), and the fixture-driven path already passes in tests/test_quest_bridge.py; what remains is the live run. This is the claiming task for this tool. QB-1

At stage 3Commit access to the bridge once the back half lands in baseline, and you triage this tool's thread. The comfy archive it is recovered from stays read-only.

• Try it and verify one school small
  Done when: Run the lab, try the actions for one school, and post in the thread whether the in-game events fired as the Tome predicted. Combat and harvest have live receipts; the other six schools remain unclaimed ground until the i5 suite witnesses them. QL-1
• Author a quest that fires small
  Done when: Edit the starter quest file into a quest of your own, get `lab_reload` to report it armed, make it fire, and post the file. A second worked example is worth more than any amount of documentation. QL-2

At stage 3Commit access to the mod.