Ryker 0.1.1

First release with extension-owned storage. Supersedes the 0.1.1-rc.1 candidate.

The storage boundary

The Chrome extension no longer writes to the site being edited. All Ryker state
lives in an extension-origin IndexedDB owned by the service worker, behind a
validated message channel. The worker derives the document key from the sender
rather than trusting the message, so a content script cannot name another
document's records, and listing uses a keyed range instead of scanning the whole
store.

A full extension session now creates no database, no localStorage key and no
sessionStorage key on the visited origin, and never opens a directory picker.

Retention, stated plainly

Nothing is pruned automatically, because the records are often the only durable
copy of what changed. Instead the store reports its usage, warns once per session
past 80 percent of the browser allowance, and names export as the way out. Clear
is per document and offers the export before deleting anything.

extension/README.md now states what is retained, where it lives and how to
remove it, including manual cleanup for anything an older development build left
on a visited site.

Fixes

• byId() could not resolve an id transferred onto an empty block, which aborted
  the test suite partway.
• The clean export erased authored body padding that Ryker never claimed, because
  it consulted a single body-level flag per property.
• The saved-changes status pill was disabled once logging was on, so it described
  a store and then refused to show it. It now opens the records it names.

Housekeeping

The dead GitHub and Google configuration surface, five orphaned DOM helpers left
behind when comments were retired, a dead boot helper and two unused CSS rules
are gone. The credential-name guard stays, because a config written for an older
build can still carry those secrets.

The suite goes from 190 to 200 checks.