emit-kanban-tasklisted

# emit-kanban-task — file a tracked card on the Bubble board ## Why this exists Findings that surface mid-task ("the auto-commit cron is dead", "this paid-IC path has no gate", "verify the audio routing tomorrow") get lost if they only live in chat. The kanban is the durable triage board: each card is a structured item a human (or the R&D manager loop) acts on. **Emitting a card is how a side-discovery becomes tracked work instead of a forgotten sentence.** Don't hand-write to a local DB or a markdown note — those don't reach the board; use this skill. ## The command Call the bundled wrapper `scripts/emit.sh` (in this skill's own directory). It resolves the underlying emitter portably — your dept-local vendored copy first, then the framework path — so you never have to figure out where the tool lives: ```bash <this-skill-dir>/scripts/emit.sh \ task=<source-id> \ title="<short imperative — what needs to happen>" \ body="<self-contained context, ≤2000 chars — readable COLD, no 'as we discussed'>" \ type=<approval|decision|incident|findings|manual|bug|feature|infra|docs|chore|research> \ priority=<normal|high|urgent> \ owner=<your dept slug, e.g. ben|maya|tony|content|accountant|rnd|tonio> \ budget=<REQUIRED integer USD, per-run, e.g. 10 — see Budget guidance below> \ proj=<optional project slug, e.g. bubble-shield, client-dev, cockpit, fund> \ due=<optional YYYY-MM-DD> \ host=<optional local|vps — usually inferred from owner> \ links=<optional typed l