gosalyn: Case 2 design ruling after r11, a link or embed to a non-.md target is an attachment, not followed and not R4; note embeds resolve as links; change goes to C2-05a (webby-0041 N3, mos-1110)

agents/gosalyn/work/case2/DESIGN.md

@@ -8,6 +8,16 @@ Base: `refactor` at 9ae8c73ac. r1 cited 5d019d876. `git diff --stat 5d019d876 9a
 adapters roles scripts` is empty (Mos in mos-0980, Webby in webby-0001), so every `file:line` holds at
 9ae8c73ac. Paths are relative to the repository root.
 
+## Ruling after r11: embeds and attachments (row 212 N3)
+
+Webby's row 212 review (webby-0041, N3) found that the C2-01 reader reads `![[...]]` embeds as links, so
+an embedded image, which is unmapped and so never indexed, counts as R4. Mos asked for a ruling from me
+or Sage (mos-1110). Ruling: a wikilink or embed whose target ends in an extension other than `.md`, in
+any case, refers to an attachment. The reader doesn't follow it, raises no problem for it, and the
+survey counts it as an attachment. An embed with no extension or with `.md` embeds a note and resolves
+like any link, R4 included. Section 1.3 says so. Row 212 lands as approved, and the change is C2-05a's,
+the first row that reads the R4 count.
+
 ## Changes from r10
 
 Webby returned r10 with B1-B3 and N1-N5 (webby-0036, `agents/webby/work/case2-r10/REVIEW.md` at
@@ -449,7 +459,9 @@ Links are `[[target]]`, `[[target|label]]` and `[[target#heading]]`. The resolve
 path from the repo root, the same path with `vaultPrefix/` stripped, a path relative to the linking file,
 and Obsidian's shortest-path form, a base name that matches exactly one indexed file. A link whose target
 is in another of her repos under `~/src` resolves to nothing (R4). `appears_in` and `relationships`
-values are read as links when they are wikilinks, and as names otherwise.
+values are read as links when they are wikilinks, and as names otherwise. A `![[target]]` embed of a
+note resolves like a link. A link or embed whose target ends in an extension other than `.md` refers to
+an attachment: it isn't followed and raises no problem (ruling after r11).
 
 One known difference (N4). Obsidian resolves a shortest-path link across her whole vault, `~/src`, and
 the reader sees only the books repo. A base name that is unique in the repo but also exists in another