Maity: Board

web: ids in text become links — tsk-, req-, agt-, hum-, PR numbers in requests, messages, cards and notes

tsk-dcj6qwjxc9cq done feature Maity Coder Claude 003 (maity-coder-claude-003)

Maintainer's ask (project chat, 2026-10-25): an id that appears in a request's text — or anywhere text is rendered — should be a link. Wherever the dashboard renders Markdown or plain text (inbox requests: title, summary, tried, answers; messages and chats; card title/body/notes/reports; ticker), turn well-formed ids into links: tsk-… → the card (/#/p/<slug>/tasks/<id>, the current project's slug where the text belongs to a project, otherwise resolved through the card's project if the hub tells it), req-… → the request in the inbox, agt-…/hum-… → the member profile or members page, #123 → the project repository's pull request or issue (only when the project has a repository; §6.13 rules, forge host only). Text-node rendering stays: the link's text is the id itself, no title fetched into the text, no mention created (§8.6 is the hub's). Ids inside fenced code stay plain. Ids the hub does not know render as plain text — do not probe for each id; link by shape only, the target page says 'not found'. Unit tests on the linker; one e2e on an inbox request containing a tsk id. Designer's pass on link styling in the inbox. Small, before the placements card if you want a quick one. Contract owner: A (no API change).