From 51c14c320a53dca1352a3efd34bc6cbccd664a08 Mon Sep 17 00:00:00 2001 From: Victor Balegas Date: Thu, 23 Jul 2026 15:56:34 +0100 Subject: [PATCH 1/2] chore: remove beads/codex agent tooling from the repo Drops the tracked .codex/ config, the .agents/skills/beads skill, the bd-prime SessionStart hook (.claude/settings.json), and the managed beads blocks in CLAUDE.md/AGENTS.md. The conservative git policy those blocks carried survives as a short Git Policy section in both files. The .beads database itself was never tracked and there are no refs/dolt/* on the remote. Co-Authored-By: Claude Fable 5 --- .agents/skills/beads/SKILL.md | 80 ------------------------ .agents/skills/beads/agents/openai.yaml | 4 -- .claude/settings.json | 15 ----- .codex/config.toml | 2 - .codex/hooks.json | 51 ---------------- AGENTS.md | 81 +------------------------ CLAUDE.md | 57 +---------------- 7 files changed, 6 insertions(+), 284 deletions(-) delete mode 100644 .agents/skills/beads/SKILL.md delete mode 100644 .agents/skills/beads/agents/openai.yaml delete mode 100644 .claude/settings.json delete mode 100644 .codex/config.toml delete mode 100644 .codex/hooks.json diff --git a/.agents/skills/beads/SKILL.md b/.agents/skills/beads/SKILL.md deleted file mode 100644 index a5a3344..0000000 --- a/.agents/skills/beads/SKILL.md +++ /dev/null @@ -1,80 +0,0 @@ ---- -name: beads -description: Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking. ---- - -# Beads - -Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work. - -## First Step - -Run: - -```bash -bd prime -``` - -If that prints nothing, check whether the repository has an active Beads workspace: - -```bash -bd where -``` - -## Preferred Route - -Use the `bd` CLI when shell access is available. It is the most compact and direct Beads interface. - -## Core CLI Workflow - -1. Find work: - -```bash -bd ready -bd list --status=open -bd list --status=in_progress -``` - -2. Inspect before editing: - -```bash -bd show -``` - -3. Claim work atomically: - -```bash -bd update --claim -``` - -4. Create durable follow-up work when implementation reveals new tasks: - -```bash -bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2 -``` - -5. Close completed work: - -```bash -bd close --reason="Completed" -``` - -## What Belongs In Beads - -Use Beads for: - -- shared project tasks -- blockers and dependencies -- discovered follow-up work -- work that must survive thread reset, compaction, or handoff -- status that another person or agent should be able to resume - -Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state. - -## Rules - -- Do not create markdown TODO files as the source of truth when Beads is available. -- Do not use `bd edit`; it opens an interactive editor. Use `bd update` flags instead. -- Prefer `--json` when parsing `bd` output programmatically. -- If hooks are installed, `bd prime` may already be injected. Run it manually when context is missing. -- Do not auto-close or mutate tasks unless the work is actually complete. diff --git a/.agents/skills/beads/agents/openai.yaml b/.agents/skills/beads/agents/openai.yaml deleted file mode 100644 index 09c3b8f..0000000 --- a/.agents/skills/beads/agents/openai.yaml +++ /dev/null @@ -1,4 +0,0 @@ -interface: - display_name: "Beads" - short_description: "Project task tracking with bd" - default_prompt: "Use $beads to inspect ready work and manage durable project tasks." diff --git a/.claude/settings.json b/.claude/settings.json deleted file mode 100644 index c6907bf..0000000 --- a/.claude/settings.json +++ /dev/null @@ -1,15 +0,0 @@ -{ - "hooks": { - "SessionStart": [ - { - "hooks": [ - { - "command": "bd prime --hook-json", - "type": "command" - } - ], - "matcher": "" - } - ] - } -} \ No newline at end of file diff --git a/.codex/config.toml b/.codex/config.toml deleted file mode 100644 index 146af7e..0000000 --- a/.codex/config.toml +++ /dev/null @@ -1,2 +0,0 @@ -[features] -hooks = true diff --git a/.codex/hooks.json b/.codex/hooks.json deleted file mode 100644 index 13c7229..0000000 --- a/.codex/hooks.json +++ /dev/null @@ -1,51 +0,0 @@ -{ - "hooks": { - "PostCompact": [ - { - "hooks": [ - { - "command": "bd codex-hook PostCompact", - "statusMessage": "Scheduling Beads context refresh", - "type": "command" - } - ], - "matcher": "manual|auto" - } - ], - "PreCompact": [ - { - "hooks": [ - { - "command": "bd codex-hook PreCompact", - "statusMessage": "Checking Beads context", - "type": "command" - } - ], - "matcher": "manual|auto" - } - ], - "SessionStart": [ - { - "hooks": [ - { - "command": "bd codex-hook SessionStart", - "statusMessage": "Loading Beads context", - "type": "command" - } - ], - "matcher": "startup|resume|clear" - } - ], - "UserPromptSubmit": [ - { - "hooks": [ - { - "command": "bd codex-hook UserPromptSubmit", - "statusMessage": "Refreshing Beads context", - "type": "command" - } - ] - } - ] - } -} diff --git a/AGENTS.md b/AGENTS.md index f46f96f..d727bc4 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -296,82 +296,7 @@ canvas update, screenshot. against a running demo catches what the (absent) typechecker can't. **Changing code means realigning docs in the same pass.** - -## Beads Issue Tracker +## Git Policy -This project uses **bd (beads)** for issue tracking. Run `bd prime` to see full workflow context and commands. - -### Quick Reference - -```bash -bd ready # Find available work -bd show # View issue details -bd update --claim # Claim work -bd close # Complete work -``` - -### Rules - -- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists -- Run `bd prime` for detailed command reference and session close protocol -- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files - -**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md for details and anti-patterns. - -## Agent Context Profiles - -The managed Beads block is task-tracking guidance, not permission to override repository, user, or orchestrator instructions. - -- **Conservative (default)**: Use `bd` for task tracking. Do not run git commits, git pushes, or Dolt remote sync unless explicitly asked. At handoff, report changed files, validation, and suggested next commands. -- **Minimal**: Keep tool instruction files as pointers to `bd prime`; use the same conservative git policy unless active instructions say otherwise. -- **Team-maintainer**: Only when the repository explicitly opts in, agents may close beads, run quality gates, commit, and push as part of session close. A current "do not commit" or "do not push" instruction still wins. - -## Session Completion - -This protocol applies when ending a Beads implementation workflow. It is subordinate to explicit user, repository, and orchestrator instructions. - -1. **File issues for remaining work** - Create beads for anything that needs follow-up -2. **Run quality gates** (if code changed) - Tests, linters, builds -3. **Update issue status** - Close finished work, update in-progress items -4. **Handle git/sync by active profile**: - ```bash - # Conservative/minimal/default: report status and proposed commands; wait for approval. - git status - - # Team-maintainer opt-in only, unless current instructions forbid it: - git pull --rebase - bd dolt push - git push - git status - ``` -5. **Hand off** - Summarize changes, validation, issue status, and any blocked sync/commit/push step - -**Critical rules:** -- Explicit user or orchestrator instructions override this Beads block. -- Do not commit or push without clear authority from the active profile or the current user request. -- If a required sync or push is blocked, stop and report the exact command and error. - - - -## Beads Issue Tracker - -Use Beads (`bd`) for durable task tracking in repositories that include it. Use the `beads` skill at `.agents/skills/beads/SKILL.md` (project install) or `~/.agents/skills/beads/SKILL.md` (global install) for Beads workflow guidance, then use the `bd` CLI for issue operations. - -### Quick Reference - -```bash -bd ready # Find available work -bd show # View issue details -bd update --claim # Claim work -bd close # Complete work -bd prime # Refresh Beads context -``` - -### Rules - -- Use `bd` for all task tracking; do not create markdown TODO lists. -- Run `bd prime` when Beads context is missing or stale. Codex 0.129.0+ can load Beads context automatically through native hooks; use `/hooks` to inspect or toggle them. -- Keep persistent project memory in Beads via `bd remember`; do not create ad hoc memory files. - -**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md for details and anti-patterns. - +Do not commit or push unless explicitly asked. At handoff, report changed files, validation run, +and suggested next commands. diff --git a/CLAUDE.md b/CLAUDE.md index 2232d55..84c45e6 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -2,61 +2,10 @@ This file provides instructions and context for AI coding agents working on this project. - -## Beads Issue Tracker - -This project uses **bd (beads)** for issue tracking. Run `bd prime` to see full workflow context and commands. - -### Quick Reference - -```bash -bd ready # Find available work -bd show # View issue details -bd update --claim # Claim work -bd close # Complete work -``` - -### Rules - -- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists -- Run `bd prime` for detailed command reference and session close protocol -- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files - -**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md for details and anti-patterns. - -## Agent Context Profiles - -The managed Beads block is task-tracking guidance, not permission to override repository, user, or orchestrator instructions. - -- **Conservative (default)**: Use `bd` for task tracking. Do not run git commits, git pushes, or Dolt remote sync unless explicitly asked. At handoff, report changed files, validation, and suggested next commands. -- **Minimal**: Keep tool instruction files as pointers to `bd prime`; use the same conservative git policy unless active instructions say otherwise. -- **Team-maintainer**: Only when the repository explicitly opts in, agents may close beads, run quality gates, commit, and push as part of session close. A current "do not commit" or "do not push" instruction still wins. - -## Session Completion - -This protocol applies when ending a Beads implementation workflow. It is subordinate to explicit user, repository, and orchestrator instructions. - -1. **File issues for remaining work** - Create beads for anything that needs follow-up -2. **Run quality gates** (if code changed) - Tests, linters, builds -3. **Update issue status** - Close finished work, update in-progress items -4. **Handle git/sync by active profile**: - ```bash - # Conservative/minimal/default: report status and proposed commands; wait for approval. - git status - - # Team-maintainer opt-in only, unless current instructions forbid it: - git pull --rebase - git push - git status - ``` -5. **Hand off** - Summarize changes, validation, issue status, and any blocked sync/commit/push step - -**Critical rules:** -- Explicit user or orchestrator instructions override this Beads block. -- Do not commit or push without clear authority from the active profile or the current user request. -- If a required sync or push is blocked, stop and report the exact command and error. - +## Git Policy +Do not commit or push unless explicitly asked. At handoff, report changed files, validation run, +and suggested next commands. ## Build & Test From 7b421e379b4fbf3ade7377a127315e178596d96e Mon Sep 17 00:00:00 2001 From: Victor Balegas Date: Thu, 23 Jul 2026 15:57:24 +0100 Subject: [PATCH 2/2] =?UTF-8?q?chore:=20drop=20beads=20leftovers=20?= =?UTF-8?q?=E2=80=94=20.gitignore=20block,=20dangling=20issue=20ids=20in?= =?UTF-8?q?=20memory-model=20doc?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5 --- .gitignore | 7 ------- docs/memory-model.md | 2 +- 2 files changed, 1 insertion(+), 8 deletions(-) diff --git a/.gitignore b/.gitignore index 461d1da..4177352 100644 --- a/.gitignore +++ b/.gitignore @@ -19,12 +19,5 @@ erl_crash.dump *.dump memtest.txt /results/ - -# Beads / Dolt files (added by bd init) -.dolt/ -*.db -.beads-credential-key -.beads/proxieddb/ -.beads/ data/dbsp/ packages/bench/data/ diff --git a/docs/memory-model.md b/docs/memory-model.md index 0cff183..ec7cc49 100644 --- a/docs/memory-model.md +++ b/docs/memory-model.md @@ -178,7 +178,7 @@ So the feed set does **not** move to disk. It stays a host-side bitmap, and the (`ELECTRIC_CIRCUITS_SUBQ_STORAGE_*`) now covers only the **contributor** relation still in the circuit — kept because a high-selectivity inner query could grow it, with the default a candidate to flip off (a separate, gated follow-up; see the spike §4c). Checkpoint/restore of -the feed bitmaps and the contributor relation (beads **dbsp-ds-mrt** / **dbsp-ds-pg5**) is now +the feed bitmaps and the contributor relation (a tracked follow-up) is now *simpler*: the bulk of what needed checkpointing was the feed set, which serialises trivially, and a checkpoint taken under the registry lock is consistent by construction (same SnapshotGate/xid-fencing discipline the counts tier uses). Full analysis: