feat: align issue format with wiki workflow spec

Match the Issues-Workflow wiki (claude-skills/tea#1): types expand to
bug|task|refactor|test|feature|draft (feature becomes a container,
task takes over new functionality), add severity/tech/comp label
namespaces, an optional "Depends on" section, and templates for
test and feature. Milestone/Project containers documented.

Refs claude-skills/tea#1

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

skills/use/SKILL.md

@@ -86,10 +86,11 @@ Notes:
 - [HELPERS](references/tea/helpers.md) — open, notifications, clone, api
 - [MISC](references/tea/misc.md) — whoami, admin
 - [SETUP](references/tea/setup.md) — logins, logout, ssh-keys
-- [ISSUE FORMAT](references/issue-format.md) — canonical issue format: types
-  (`type/bug|feature|refactor` exclusive labels), templates, title and
-  language rules. MANDATORY whenever creating or editing an issue; the
-  `/tea:issue` skill is the guided procedure for it.
+- [ISSUE FORMAT](references/issue-format.md) — canonical issue format: label
+  namespaces (`type/*`, `severity/*` exclusive; `tech/*`, `comp/*` free),
+  types `bug|task|refactor|test|feature|draft`, templates, dependencies,
+  title and language rules. MANDATORY whenever creating or editing an issue;
+  the `/tea:issue` skill is the guided procedure for it.
 
 ## Rich payloads — write to `$PWD/tmp/` first, then `tea api`