docs: end-user install + commit prebuilt dist

Mirror the MarkEdit-preview README structure: lead with the prebuilt
dist file so end users don't need a Node toolchain. The yarn-based
build flow becomes a "Building" section for contributors.

- Remove dist/ from .gitignore so the prebuilt bundle ships with the repo.
- Commit dist/markedit-wikilinks.js (6.35 kB) for direct raw-download install.
- Rewrite README with How to Use table (syntax + click behavior), explicit
  resolution order, sandbox/folder-access note, and architecture notes
  including the preview integration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: nuc

.gitignore

@@ -1,4 +1,3 @@
 node_modules/
-dist/
 .DS_Store
 *.log

README.md

@@ -1,54 +1,61 @@
 # MarkEdit-wikilinks
 
-Obsidian-style `[[wikilinks]]` for [MarkEdit](https://github.com/MarkEdit-app/MarkEdit).
+Obsidian-style `[[wikilinks]]` for [MarkEdit](https://github.com/MarkEdit-app/MarkEdit) that leverages [markedit-api](https://github.com/MarkEdit-app/MarkEdit-api).
 
-A small CodeMirror extension that adds wikilink syntax highlighting and Cmd-click navigation, with Obsidian-style vault-wide resolution.
+A small CodeMirror extension that adds wikilink syntax highlighting and click-to-follow navigation, with Obsidian-style vault-wide resolution. Renders in both the editor and the [MarkEdit-preview](https://github.com/MarkEdit-app/MarkEdit-preview) pane.
 
-## Features
+## Installation
 
-- **Highlights** `[[Note Name]]`, `[[Note|Alias]]`, and `![[Embed]]` as real syntax nodes — implemented via a Lezer inline parser so it composes correctly with the rest of MarkEdit's Markdown grammar and stays inert inside fenced code blocks.
-- **Cmd-click in the editor** opens the linked file. Resolution mirrors Obsidian:
-  1. same folder as the current file,
-  2. vault-relative path if the target contains `/` (e.g. `[[docs/foo]]`),
-  3. recursive search from the vault root (the directory containing `.obsidian/`), skipping hidden and noisy folders, budget-capped at 5,000 entries per click.
-- **Plain click in the [MarkEdit-preview](https://github.com/MarkEdit-app/MarkEdit-preview) pane** also follows wikilinks. The preview integration post-processes the rendered HTML (the preview plugin's `markdown-it` pipeline doesn't know `[[…]]`), turning text nodes into anchors with the same resolver, and is a no-op if MarkEdit-preview isn't installed.
-- **Create-on-miss**: if nothing resolves, prompts to create `<target>.md` in the current folder.
-- **Styled** via CSS classes that pick up your MarkEdit theme.
+Copy [dist/markedit-wikilinks.js](dist/markedit-wikilinks.js?raw=true) to `~/Library/Containers/app.cyan.markedit/Data/Documents/scripts/`. Details [here](https://github.com/MarkEdit-app/MarkEdit/wiki/Customization#entries).
+
+> Once installed, restart MarkEdit to apply the changes.
+>
+> If wikilink resolution fails because the file is in a sibling folder, you may also need to [grant folder access](https://github.com/MarkEdit-app/MarkEdit/wiki/Customization#grant-folder-access) by opening your vault root via **File → Open…** once.
+
+## How to Use
+
+Type any Obsidian-style wikilink in your Markdown:
+
+| Syntax | Meaning |
+|---|---|
+| `[[Note Name]]` | Link to `Note Name.md` |
+| `[[Note Name\|Display Text]]` | Link with custom display text |
+| `[[docs/foo]]` | Vault-relative path |
+| `![[Embed]]` | Embed syntax (highlighted, not yet rendered as image) |
+
+To follow a link:
+
+- **In the editor**: <kbd>⌘</kbd>-click on the wikilink.
+- **In the [MarkEdit-preview](https://github.com/MarkEdit-app/MarkEdit-preview) pane**: plain click.
+
+Resolution mirrors Obsidian, in this order:
+
+1. **Same folder** as the current file.
+2. **Vault-relative path** if the target contains `/` (e.g. `[[docs/foo]]`).
+3. **Recursive search** from the vault root (the directory containing `.obsidian/`), skipping hidden dot-dirs and `node_modules` / `dist` / `build` / `target`, budget-capped at 5,000 entries per click.
+
+If nothing resolves, a diagnostic dialog shows what was tried and offers to create `<target>.md` in the current folder.
 
 ## Not yet supported
 
 - `#header` and `^block-id` fragments — stripped, not navigated.
 - Inline embed rendering — `![[image.png]]` is highlighted but not displayed as an image.
 - Vault index caching — the recursive search rebuilds per click. Fast enough for hundreds of files; large vaults may want a session-scoped index.
 - Autocomplete for link targets.
+- User-configurable settings.
 
-## Install
-
-```sh
-yarn install
-yarn build     # vite build also deploys the bundle to MarkEdit's scripts/ folder
-yarn reload    # restart MarkEdit so the script loads
-```
-
-The compiled bundle lands at:
-`~/Library/Containers/app.cyan.markedit/Data/Documents/scripts/markedit-wikilinks.js`
+## Building
 
-To uninstall: `yarn uninstall`.
-
-### Sandbox / folder access
-
-MarkEdit is sandboxed and only sees folders you've explicitly granted access to.
-If `[[…]]` resolution fails with `listFiles() returned undefined` in the diagnostic
-alert, open your vault folder once via **File → Open…** to grant access. See
-[the MarkEdit wiki on folder access](https://github.com/MarkEdit-app/MarkEdit/wiki/Customization#grant-folder-access) for details.
+Run `yarn install && yarn build` to build and deploy the script. The build also copies the bundle to MarkEdit's scripts folder, so a `yarn reload` will pick up your changes immediately.
 
 ## Architecture
 
 ```
-main.ts              wires three pieces into MarkEdit
+main.ts              wires four pieces into MarkEdit
 src/parser.ts        Lezer inline parser → emits WikiLink / WikiLinkEmbed / Mark / Target / Alias nodes
-src/decoration.ts    CodeMirror ViewPlugin → styles those nodes
-src/follow.ts        domEventHandlers → Cmd-click resolves and opens
+src/decoration.ts    CodeMirror ViewPlugin → styles those nodes in the editor
+src/follow.ts        domEventHandlers → ⌘-click in the editor → resolve and open
+src/preview.ts       MutationObserver on .markdown-body → transform text into <a> + plain-click handler
 ```
 
 A real Lezer parser is used rather than a regex decoration so wikilink nodes:
@@ -57,9 +64,11 @@ A real Lezer parser is used rather than a regex decoration so wikilink nodes:
 - play nicely with code folding and syntax-aware selection,
 - let the click handler use `syntaxTree.resolveInner(pos)` instead of re-matching against document text.
 
-## Contributing
+The preview integration post-processes the rendered HTML inside `.markdown-body` because MarkEdit-preview's [markdown-it](https://github.com/markdown-it/markdown-it) pipeline doesn't know `[[…]]` and has no extension API for adding parsers. The observer skips text inside `<code>`, `<pre>`, `<script>`, `<style>`, and existing `<a>` elements, and disconnects during its own mutations to avoid feedback loops. It's a no-op when MarkEdit-preview isn't installed.
+
+## Contribution
 
-Issues and PRs welcome. Build verification runs via GitHub Actions on every push and PR.
+Issues and PRs welcome. Build verification runs via GitHub Actions on every push and PR. If you change source, please run `yarn build` and commit the updated `dist/markedit-wikilinks.js` along with your changes so end users get the fix without needing a toolchain.
 
 ## License
 

dist/markedit-wikilinks.js

@@ -1,6 +1,6 @@
 {
   "name": "markedit-wikilinks",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Obsidian-style [[wikilinks]] for MarkEdit.",
   "keywords": [
     "markedit",