Index: .beads/README.md =================================================================== --- .beads/README.md (revision 1e194e481dd18fd3624d4649c4be97df3a22cd0f) +++ .beads/README.md (revision 4cc4bcfd5526bad0e0ab54748190b7952db24782) @@ -1,3 +1,23 @@ # Beads - AI-Native Issue Tracking + +> **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. Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code. Index: AGENTS.md =================================================================== --- AGENTS.md (revision 1e194e481dd18fd3624d4649c4be97df3a22cd0f) +++ AGENTS.md (revision 4cc4bcfd5526bad0e0ab54748190b7952db24782) @@ -1,5 +1,26 @@ # 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 Index: CLAUDE.md =================================================================== --- CLAUDE.md (revision 1e194e481dd18fd3624d4649c4be97df3a22cd0f) +++ CLAUDE.md (revision 4cc4bcfd5526bad0e0ab54748190b7952db24782) @@ -2,4 +2,24 @@ This file provides instructions and context for AI coding agents working on this project. + +> **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.