0.1.1 — tombstone banner fix

Fixes a tombstone bug found by the end-to-end runbook against a real
1682-page vault.

Fixed

A restored page kept its "Deleted in Javis" banner forever. The banner was
written above the generated block — in the half of the file the plugin is
forbidden to touch — so restoring the page cleared javis_deleted and refilled
the block, but could never remove the banner. One delete/restore cycle and the
note read as deleted permanently.

The banner is now the generated block's content, so a restore overwrites it
like any other generated text. No exception is carved out of the
never-touch-outside-the-markers rule.

Nothing else changed. minAppVersion stays 1.11.4.

Upgrading from 0.1.0

Replace main.js and manifest.json in
<vault>/.obsidian/plugins/javis-wiki-sync/ and reload Obsidian. Your notes,
settings and sign-in are untouched.

If a note still shows a "Deleted in Javis" banner from 0.1.0, delete those two
lines by hand — the plugin will not remove them, because they sit in your half
of the file and removing them would be exactly the rule this release is
defending.

Verified against production

Tombstone	banner between the markers
Restore	banner gone, javis_deleted cleared, body restored
Vault-wide	1683 files, 0 stray banners, no .trash

290 unit tests, clean typecheck and build. The runbook now stands at 21 pass,
0 fail, 5 blocked — every critical case passing, including never-unlink,
self-heal after losing plugin state, and hand-written content surviving both an
update and a delete.

Still a pre-release: this has been exercised on one real vault, not many.