Lambda d7231d34d7 feat(rich-content): render bare in-app project/issue URLs as chips (MUL-5499) ...

A project has no `MUL-123`-style identifier — only a UUID and a free-text
title — so there is nothing for the bare-identifier autolink preprocessor to
detect, and the link copied out of the app is how people actually reference
one. It rendered as a raw URL.

RichLink now unfurls a bare in-app entity URL into the same chip the
`mention://project/<uuid>` form already produces (issue URLs go through the
same path for symmetry). Render-only: stored markdown is untouched, and the
editable Tiptap path is deliberately unaffected.

Three guards, each load-bearing: the link must be bare (an authored label is
never discarded), same-workspace (a chip resolves its title in the current
workspace only), and address exactly one entity page by UUID with no query or
fragment.

Also:
- mobile: tapping a `mention://project/` link navigated nowhere despite the
  `project/[id]` route existing — it now pushes the project detail.
- agents had no documented way to emit a clickable project reference: add the
  link form to the runtime brief's Mentions section and to the projects skill,
  and record in the mentioning skill why `project` sits outside `MentionRe`
  (render-only, enqueues nothing).

Co-authored-by: multica-agent <github@multica.ai>

2026-07-29 21:53:37 +08:00

..

desktop

Revert "feat(ui): establish a role-named type scale and migrate ad-hoc font s…" (#6116)

2026-07-29 17:10:33 +08:00

docs

fix(agents): allow agent owners to manage their own agent's env (MUL-5438) (#6080)

2026-07-29 14:01:09 +08:00

mobile

feat(rich-content): render bare in-app project/issue URLs as chips (MUL-5499)

2026-07-29 21:53:37 +08:00

web

docs(changelog): add v0.4.14 release entry (#6120)

2026-07-29 17:58:47 +08:00