tagged/topic: auto-tags miss the initiative's main theme — tagged returns empty

[1Croydan1]

Problem

Auto-derived topic tags miss the initiative's main theme, so tagged — the only consumer of topic: tags — returns emptiness and never gets positive reinforcement (0 calls ever; agents loaded its schema ~5 times and, having read it, chose search instead).

Evidence

• A live call tagged "topic:figma" inside a Figma-centric team initiative → "(0): (empty)" — the tool description's promise ("slice by tag via tagged "topic:..."") fails on the project's main theme.
• Related: closed topic: auto-tags are the body's first 5 surface forms — noise on inflected languages #41 (topic tags = the body's first 5 surface forms — noise on inflected languages) — that issue covers a different aspect of the same mechanism: even after topic: auto-tags are the body's first 5 surface forms — noise on inflected languages #41, derivation doesn't guarantee the initiative's theme lands in the tags at all.
• Meanwhile tagged is the only path to status:open hypotheses (see the awake read-back issue) — a dead tool gates a live need.

Proposal

Either fix derivation (consider the node name and the initiative name, not just the body; frequency across the initiative rather than per node), or until then remove topic: from tagged's description — it currently sells a capability that doesn't exist, and the first empty answer kills trust in the tool.