Retire the local beads database; the issues live in shaer-frontend
All 32 kept their prutfolio-src-* ids, so bd show prutfolio-src-7cz
still means the same issue from the other repository.
The reason this database drifted is worth recording next to the notice:
this repo has no core.hooksPath, so the hooks in .beads/hooks/ never ran.
The Dolt database is gitignored and the one tracked artefact,
.beads/issues.jsonl, is refreshed only by those hooks — it had fallen
four days and two issues behind before anyone looked.
core.hooksPath is deliberately left unset. Setting it now would make a
retired database export itself into git on every commit, which is the
opposite of retiring it.
Nothing enforces the retirement. A bd create here will still succeed
and still be lost, and the notice says so rather than implying a guard.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
