Link automd belongs to the link interaction lane

Question

Should [text](url) automd be treated as just another autoformat family?

Decision

No.

Treat link automd as a richer link-interaction surface that can reuse autoformat mechanics, but should not be flattened into the same family as:

• block shorthand autoformat
• inline mark autoformat
• text-substitution autoformat

Why

• it parses two payloads, not one trigger string
• it creates an inline non-void link span with URL payload, not just a mark or text substitution
• it is closer to markdown source-entry for links than to generic shorthand replacement
• current Plate now ships the narrow closing-) slice in the default current kits, but it still does so through the richer link interaction lane instead of flattening it into plain autoformat

Consequences

• spec it separately
• keep it out of the current shipped autoformat family
• allow shared runtime reuse where helpful, but do not let the mechanical implementation dictate the behavior lane