Changeset 4cc4bcf in Klonkt for AGENTS.md

Timestamp:

08/23/2026 06:21:30 PM (2 weeks ago)

Author:

Bart <bart@…>

Branches:

main

Children:

7b03c35

Parents:

1e194e4

Message:

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.

File:

• AGENTS.md (modified) (1 diff)

AGENTS.md

@@ -1 +1 @@
 # Agent Instructions
 
-This project uses **bd** (beads) for issue tracking. Run `bd prime` for full workflow context.
+> **The beads database in this repository is retired. Do not write to it.**
+>
+> Klonkt's issues live in `~/Sources/shaer-frontend/.beads` (Dolt database
+> `shaer`). All 32 of them were migrated there on 2026-08-23 keeping their
+> original `prutfolio-src-*` ids, so `bd show prutfolio-src-7cz` works from that
+> repository and means the same issue it always did.
+>
+> Create, update and close Klonkt issues from `~/Sources/shaer-frontend`. The
+> `bd` commands below apply there, not here.
+>
+> Why: this repository has no `core.hooksPath`, so the beads hooks in
+> `.beads/hooks/` never ran. The Dolt database is gitignored and the one tracked
+> artefact, `.beads/issues.jsonl`, is only refreshed by those hooks — it had
+> drifted four days and two issues behind before anyone noticed. shaer-frontend
+> has the hooks wired, so its export stays current.
+>
+> The local database is left in place and still readable for history. Nothing
+> enforces this: it is a convention, and a `bd create` run here will succeed and
+> be lost.
+
+This project uses **bd** (beads) for issue tracking, from the shaer-frontend
+repository. Run `bd prime` there for full workflow context.
 
 ## Quick Reference