waymark-worklisted

# Waymark work — new issue doc Create one thin issue doc (one issue = one file) in `waymark/draft/`. Reference external truth, never copy it. Only run this where Waymark is set up (a `waymark/` folder exists); if not, suggest `waymark init` first. Speak in the repo's `lang`. ## Step 1 — Read config Read `.waymark.yml` (and `.waymark.local.yml` if present) for `lang`, `repos` (alias → remote), `assignees` (github-id → prefix), and whether a `tracker_type` is configured (the tracker tool, used for id allocation). Note: `tracker_type` (config, the tool) is distinct from a doc's `tracker` frontmatter (the issue links). ## Step 2 — Basics Gather the issue title and which repos it targets (MUST be aliases declared in `repos:`). ## Step 3 — Ask EXPLICITLY what to link (don't assume none) - **Planning source** (the why/what): a Confluence / Notion / PDF / doc link. "None — verbal discussion or pure infra" is a valid answer; record it as such, don't invent one. - **Tracker issues** (Jira / Linear / GitHub Issues / any tool): the issue(s) this work syncs with. **Multiple allowed** when one work unit spans several tickets (backend + frontend, or a cross-tool link). "None" is valid. These are references, not copies — link them, never mirror their contents. If the tracker list keeps growing large, that's a smell the issue is too big — suggest splitting it. ## Step 4 — Allocate the id (always exactly ONE) - If a `tracker_type` is configured AND the user designates one tracker i