Remove the TldrawImage assets patch once the SDK ships the prop

[frolic]

We carry a patch-package patch against tldraw purely to add an assets prop to TldrawImage:

- const store = useTLStore({ snapshot: props.snapshot, shapeUtils: shapeUtilsWithDefaults })
+ const store = useTLStore({ assets: props.assets, snapshot: props.snapshot, shapeUtils: shapeUtilsWithDefaults })

Without it TldrawImage falls back to the inline base64 asset store, so drawings we render read-only (embeds and previews) can't resolve media stored in the user's vault.

That change is now open upstream as tldraw/tldraw#9697, which closes tldraw/tldraw#4603 — the original request, filed here by @jon-dez in 2024 with a working implementation, which the stale bot closed without it being picked up.

We're deliberately keeping the patch for now rather than blocking on the SDK review.

What to do once tldraw/tldraw#9697 is released

1. Bump tldraw in package.json to the first release containing the prop.
2. Delete patches/tldraw+5.2.5.patch.
3. It's our only patch, so also drop "postinstall": "patch-package" and the patch-package devDependency.
4. Check the assets prop is still passed wherever we render TldrawImage — upstream it is optional, so if it silently stops being forwarded, images just quietly disappear rather than erroring.
5. Verify an embedded drawing that references a vault-stored image still renders it.

Step 5 is the one worth doing by hand. The e2e suite doesn't cover asset resolution, so nothing will fail if this regresses.

Depends on #212, which bumps tldraw to 5.2.5 and regenerates the patch under its current filename.

[jon-dez]

@frolic I've been inactive for a bit, though i have been making some changes / refactors across the repository (changes local on my machine). I would be happy to collaborate with you, rebasing my changes on top of yours.

[frolic]

Hey! Would love to hear about these changes. We're just trying to get the Obsidian plugin back up to speed with the SDK and prepare for supporting the .tldraw file format.

[jon-dez]

@frolic just pushed my changes to https://github.com/jon-dez/tldraw-in-obsidian/tree/dev (still not ready, just a few package updates waiting on me to publish to npm)

I didn't feel like typing it all out so I had Claude generate a summary for me 😆. Essentially it focuses on general refactors, organizing files into "layers" so to say (enforced by eslint-plugin-boundaries) and updates to dependencies (including tldraw 5.2.5). Also, I added more e2e test cases. Since the Vite integration and some e2e helpers are supported by packages that I maintain, I need to publish those packages to npm (will be doing so shortly).

---

Summary: Codebase refactor + dependency modernization

This range covers a large internal restructuring effort plus a wave of dependency upgrades. No user-facing feature changes — the goal was code health, maintainability, and fixing latent bugs found along the way.

1. Layer-separation refactor

Reorganized the plugin's internal architecture into clearly separated layers (plugin lifecycle, document/data model, view logic, settings), enforced with lint rules (eslint-plugin-boundaries) so future PRs can't accidentally reintroduce cross-layer coupling.

Bugs found and fixed as part of this work (each with a regression test added first):

• IndexedDB connection was being reopened on every call instead of reused
• Asset cleanup ("prune") loop stopped early instead of checking all assets, leaving orphaned assets behind in some cases
• Settings migration could silently drop a user's legacy file-destination setting
• Some settings updates weren't being awaited, risking lost writes
• A text-replacement routine could corrupt $-prefixed patterns inside drawing data
• Settings ownership was consolidated into a single manager, fixing a related view-state bug

2. Dependency upgrades

• TypeScript 5.5 → 6.0
• React / React-DOM 18.3 → 19.2 (plus a follow-up fix for plugin instantiation under React 19)
• ESLint 8.57 → 10.7 (with a new React linting plugin)
• zustand 4.5 → 5.0
• monkey-around, builtin-modules bumped
• Split the TypeScript config so plugin code (src/) and Node tooling (scripts/, build configs) are type-checked separately, catching a batch of previously-hidden type errors

3. Test infrastructure

• Added a minimum window-size requirement for e2e tests to eliminate flakiness from UI elements being hidden at small window sizes
• Strengthened a couple of e2e checks that were previously no-ops (visual checks that didn't actually assert anything)
• Added new tests documenting bugs before fixing them

---

Net result: same functionality for end users, but a cleaner internal architecture, an up-to-date dependency set (notably React 19 and TS 6), and several real bugs (data loss / corruption edge cases) fixed along the way.

[frolic]

Sounds great! I also added some e2e tests and working to bump the SDK to 5.2.5. Should we pull in your other changes too?

[jon-dez]

@frolic Yep! just pushed some changes, should be fine to pull in now!