- Timestamp:
- 08/24/2026 07:42:24 AM (2 weeks ago)
- Branches:
- main
- Children:
- aaa700e
- Parents:
- e48ec78 (diff), 4cc4bcf (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
AGENTS.md
re48ec78 r7b03c35 1 1 # Agent Instructions 2 2 3 This project uses **bd** (beads) for issue tracking. Run `bd prime` for full workflow context. 3 > **The beads database in this repository is retired. Do not write to it.** 4 > 5 > Klonkt's issues live in `~/Sources/shaer-frontend/.beads` (Dolt database 6 > `shaer`). All 32 of them were migrated there on 2026-08-23 keeping their 7 > original `prutfolio-src-*` ids, so `bd show prutfolio-src-7cz` works from that 8 > repository and means the same issue it always did. 9 > 10 > Create, update and close Klonkt issues from `~/Sources/shaer-frontend`. The 11 > `bd` commands below apply there, not here. 12 > 13 > Why: this repository has no `core.hooksPath`, so the beads hooks in 14 > `.beads/hooks/` never ran. The Dolt database is gitignored and the one tracked 15 > artefact, `.beads/issues.jsonl`, is only refreshed by those hooks — it had 16 > drifted four days and two issues behind before anyone noticed. shaer-frontend 17 > has the hooks wired, so its export stays current. 18 > 19 > The local database is left in place and still readable for history. Nothing 20 > enforces this: it is a convention, and a `bd create` run here will succeed and 21 > be lost. 22 23 This project uses **bd** (beads) for issue tracking, from the shaer-frontend 24 repository. Run `bd prime` there for full workflow context. 4 25 5 26 ## Quick Reference
Note:
See TracChangeset
for help on using the changeset viewer.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)