v0.6.1 — Namespace rules reach an update

Namespace rules now reach an existing installation

0.6.0 introduced the memory model — a memory class, a ranking bonus and an
instruction template per namespace — and seeded the rules that drive all three
from bootstrap.ts. update.sh calls bootstrap with --skills-only, on
purpose, so that a tuned configuration is never overwritten. The rules rode
along in the part that is deliberately skipped.

An installation updating from 0.5.0 therefore received the schema of the new
memory model without any of its configuration. Entries written after the update
carried no class, no bonus and no framing, because nothing matched the namespace
they were written to. The feature the release is named for reached new
installations only.

The rules move to migration V81, which runs on both the install and the update
path. ON CONFLICT (pattern) DO NOTHING keeps it additive: a rule you edited, or
deleted on purpose, stays as you left it.

update.sh also loses its 0.6.0 notice, and the message strings that fed it. It
could never have printed — the script body sits in a function so that bash parses
it before git pull replaces the file, which means the version that runs is
the one already installed. A notice added for release N is executed by release
N-1's script, where it does not exist.

⚠️ Do not stay on this release

V81 as shipped here cannot be parsed by Flyway, and the update aborts at the
migrator. Go to 0.6.2.

Nothing is applied before that failure, so the schema stays where it was and no
flyway repair is needed — running the update again on 0.6.2 is enough.