Epic references are looking a little funny sometimes

@jay_mccure reported this surprise / in a top-level epic notification in #is-this-known:

Looking at epic references in general, something feels a bit off. Here's some Markdown:

* [epic:gitlab-org/quality/116]
* gitlab-org/quality&116
* gitlab-org/quality#116
* /gitlab-org/quality&116
* /gitlab-org/quality#116
* gitlab-org#19140
* gitlab-org&19140
* /gitlab-org#19140
* /gitlab-org&19140

Here's the live render:

• gitlab-org/quality&116
• gitlab-org/quality&116
• gitlab-org/quality#116
• /gitlab-org/quality&116
• /gitlab-org/quality#116
• gitlab-org#19140
• gitlab-org&19140
• /gitlab-org#19140
• /gitlab-org&19140

Here's a screenshot of that render for posterity:

Has the # always "bled" through like this? It seems to me an epic reference should maybe always link itself using the canonical & syntax, even if it wasn't linked that way initially. And the / root is getting left out to dry.

I'm assuming the system note generator uses the / syntax, leading to the above. (They should really use full URLs tbh, but let's not get ahead of ourselves.) Let's repro in dev and see.

[3] pry(main)> Note.last(2).first.note
  Note Load (1.0ms)  SELECT "notes".* FROM "notes" ORDER BY "notes"."id" DESC LIMIT 2 /*application:console,db_config_database:gitlabhq_development,db_config_name:main,console_hostname:aconnor--20250904-77Q07,console_username:kivikakk,line:(pry):3:in `__pry__'*/
=> "mentioned in epic /gitlab-org#1"