style(codeblocks): align all copy buttons to the top-right

The mermaid and markmap copy buttons sat top-left while the tree's sat
top-right, so the three codeblocks disagreed on placement. Top-right
matches Obsidian's own convention for code blocks.

Only the copy buttons move. The markmap zoom/fit toolbar stays in the
bottom-right — it's a separate control group and doesn't collide.

Author: michaelpporter

CHANGELOG.md

@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 * Restored every missing margin, padding, gap, width and offset across the plugin. The stylesheet imported only Tailwind's utilities layer, but the numeric spacing scale that `p-2`, `gap-1`, `w-48`, `top-2` and friends resolve against lives in its theme layer — so all 39 of those classes, used in 15 files, were silently dropped at build time. Importing the theme layer brings them back. Expect slightly roomier spacing in the settings tab and the side views, and correctly positioned floating buttons in codeblocks. Preflight (Tailwind's browser reset) is deliberately still excluded, so nothing about Obsidian's own styling changes.
 * The tree codeblock's copy button now floats in the top-right corner ([#736](https://github.com/michaelpporter/breadcrumbs/issues/736)) instead of rendering on top of the first row's collapse arrow. It was a casualty of the missing spacing scale above: the button was already positioned as floating, but its offsets compiled to nothing, so it fell back to the top-left of the tree.
+* Codeblock buttons now sit in the same place in all three codeblock types. The mermaid and markmap copy buttons moved from the top-left to the top-right, matching the tree codeblock and Obsidian's own convention for code blocks. The markmap zoom/fit toolbar stays in the bottom-right.
 * Links with a block or heading reference now point at the note itself ([#734](https://github.com/michaelpporter/breadcrumbs/issues/734)). `down:: [[2#^71f2d9]]` in `1.md` used to create an edge to a phantom `2#^71f2d9.md` node, so `1.md`'s tree looked right while `2.md` never showed `1.md` as its parent. The subpath is now stripped before resolving, for both frontmatter and inline fields and in list notes, and regardless of which folders the notes live in. A subpath-only link (`[[#^71f2d9]]`, pointing inside the same note) creates no edge.
 * Inline Dataview fields no longer claim links that sit outside them ([#731](https://github.com/michaelpporter/breadcrumbs/issues/731)). `(down:: [[y]]) [[x]]` in `x.md` used to make **both** `[[y]]` and `[[x]]` `down` children — including a self-loop from the note to itself — because the builder attributed every link on a line to whichever field opened that line. Bracketed fields now end at their closing bracket, matching Dataview, so only `[[y]]` becomes an edge and links elsewhere on the line stay ordinary prose. Multiple fields on one line (`(up:: [[p]]) (down:: [[c]])`) are also parsed separately now. Bare line-level fields (`down:: [[y]], [[x]]`) are unchanged — their value is still the rest of the line.
 

src/components/codeblocks/CodeblockMarkmap.svelte

@@ -270,7 +270,7 @@
 
 	{#if code}
 		<div class="relative">
-			<div class="absolute left-2 top-2 z-10 flex">
+			<div class="absolute top-2 right-2 z-10 flex">
 				<CopyToClipboardButton
 					text={code}
 					cls="clickable-icon nav-action-button"

src/components/codeblocks/CodeblockMermaid.svelte

@@ -163,7 +163,7 @@
 
 	{#if code}
 		<div class="relative">
-			<div class="absolute left-2 top-2 z-10 flex">
+			<div class="absolute top-2 right-2 z-10 flex">
 				<CopyToClipboardButton
 					text={code}
 					cls="clickable-icon nav-action-button"