Changeset 4cc4bcf in Klonkt


Ignore:
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.

Files:
3 edited

Legend:

Unmodified
Added
Removed

  • .beads/README.md

    r1e194e4 r4cc4bcf  
    11# Beads - AI-Native Issue Tracking
     2
     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.
    222
    323Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.

  • AGENTS.md

    r1e194e4 r4cc4bcf  
    11# Agent Instructions
    22
    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
     23This project uses **bd** (beads) for issue tracking, from the shaer-frontend
     24repository. Run `bd prime` there for full workflow context.
    425
    526## Quick Reference

  • CLAUDE.md

    r1e194e4 r4cc4bcf  
    22
    33This file provides instructions and context for AI coding agents working on this project.
     4
     5> **The beads database in this repository is retired. Do not write to it.**
     6>
     7> Klonkt's issues live in `~/Sources/shaer-frontend/.beads` (Dolt database
     8> `shaer`). All 32 of them were migrated there on 2026-08-23 keeping their
     9> original `prutfolio-src-*` ids, so `bd show prutfolio-src-7cz` works from that
     10> repository and means the same issue it always did.
     11>
     12> Create, update and close Klonkt issues from `~/Sources/shaer-frontend`. The
     13> `bd` commands below apply there, not here.
     14>
     15> Why: this repository has no `core.hooksPath`, so the beads hooks in
     16> `.beads/hooks/` never ran. The Dolt database is gitignored and the one tracked
     17> artefact, `.beads/issues.jsonl`, is only refreshed by those hooks — it had
     18> drifted four days and two issues behind before anyone noticed. shaer-frontend
     19> has the hooks wired, so its export stays current.
     20>
     21> The local database is left in place and still readable for history. Nothing
     22> enforces this: it is a convention, and a `bd create` run here will succeed and
     23> be lost.
    424
    525<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:7510c1e2 -->
Note: See TracChangeset for help on using the changeset viewer.