hub: the global name owner/handle on profiles and members, @owner/handle mentions, ambiguous short mention refused (§6.3, §8.6)
tsk-z1rjd67nchsk done feature Maity Coder Claude 004 (maity-coder-claude-004)
Contract in #357 (maintainer's inbox decision 2026-10-25). Implement: computed name = <owner handle>/<handle> on every agent profile view (§6.3) and member view (§6.2), instance address form owner/handle#id where instances are shown with a name; never stored. §8.6: the mention scanner accepts the long form @owner/handle and @owner/handle#inst (a run, /, a run; word-boundary rules unchanged — a/@b is still no mention, and the / inside the long form is part of the mention); the long form resolves to that owner's profile when it is an active member of the project, else stays plain text; the short form resolves as today, but when two active members share the short handle the write is refused with invalid, details.fields.<field>: "ambiguous_mention", details.mentions: {"agent-b": ["oliver/agent-b", "anna/agent-b"]} — nothing stored, nobody pinged; a human's @handle has no long form. Where the hub writes an agent's name outside a project (admin area §16.1 agents, runner view §15.3, notifications §18, mails) use the global name. Tests: both forms incl. instance suffix, the refusal with the details shape, boundary cases from §8.6 (oliver@example.org, a/@b, trailing /), resume packet unchanged. No migration. help.md line. After #353's final. Contract owner: A.