chore: bd init + Claude Code project assets #5

Merged
zombor merged 2 commits from chore/bd-init-setup into develop 2026-05-11 00:51:39 +00:00
Owner

Summary

Brings the bd (beads) issue-tracker setup and project-level Claude Code orchestration assets into develop. None of the three open feature PRs (#2 #3 #4) can have a clean diff until these files exist on develop, because they were all branched off a local commit that adds them.

After this merges, the feature PR diffs will collapse to only their actual feature changes — no rebase needed on those branches.

Commits

  • d728fd07 bd init: initialize beads issue tracking — generated by bd init; adds .beads/ (config, hooks, metadata), the .beads-credential-key / *.db / .dolt/ entries in .gitignore, and a bd Issue Tracker section in AGENTS.md.
  • 6ddc8639 chore: complete bd init setup and add .claude orchestration assets — the rest of the per-project Claude Code config that was still uncommitted locally: .claude/ (agents, hooks, rules, skills, settings), the Grimmory orchestration section appended to AGENTS.md, .claude/.upgrades/ added to .gitignore, and dolt.auto-push: false in .beads/config.yaml.

Notes

  • CLAUDE.md is a symlink to AGENTS.md, so the Beads + orchestration content is consumed by both Claude Code (which reads CLAUDE.md) and other agent runtimes (which read AGENTS.md).
  • .claude/.upgrades/ is Claude Code's local upgrade cache and stays untracked.
  • dolt.auto-push: false skips the dolt-side git push after each bd write; can be re-enabled with bd config set dolt.auto-push true once the Forgejo remote is confirmed writable.

Test plan

  • Visual diff review only — no code paths touched.
  • After merge, confirm PRs #2 / #3 / #4 diffs no longer include .beads/, .claude/, AGENTS.md, .gitignore.
## Summary Brings the bd (beads) issue-tracker setup and project-level Claude Code orchestration assets into `develop`. None of the three open feature PRs (#2 #3 #4) can have a clean diff until these files exist on `develop`, because they were all branched off a local commit that adds them. After this merges, the feature PR diffs will collapse to only their actual feature changes — no rebase needed on those branches. ## Commits - **d728fd07** `bd init: initialize beads issue tracking` — generated by `bd init`; adds `.beads/` (config, hooks, metadata), the `.beads-credential-key` / `*.db` / `.dolt/` entries in `.gitignore`, and a bd Issue Tracker section in `AGENTS.md`. - **6ddc8639** `chore: complete bd init setup and add .claude orchestration assets` — the rest of the per-project Claude Code config that was still uncommitted locally: `.claude/` (agents, hooks, rules, skills, settings), the Grimmory orchestration section appended to `AGENTS.md`, `.claude/.upgrades/` added to `.gitignore`, and `dolt.auto-push: false` in `.beads/config.yaml`. ## Notes - `CLAUDE.md` is a symlink to `AGENTS.md`, so the Beads + orchestration content is consumed by both Claude Code (which reads CLAUDE.md) and other agent runtimes (which read AGENTS.md). - `.claude/.upgrades/` is Claude Code's local upgrade cache and stays untracked. - `dolt.auto-push: false` skips the dolt-side `git push` after each `bd` write; can be re-enabled with `bd config set dolt.auto-push true` once the Forgejo remote is confirmed writable. ## Test plan - [ ] Visual diff review only — no code paths touched. - [ ] After merge, confirm PRs #2 / #3 / #4 diffs no longer include `.beads/`, `.claude/`, `AGENTS.md`, `.gitignore`.
chore: complete bd init setup and add .claude orchestration assets
Some checks failed
notify-discord-release-notes.yml / chore: complete bd init setup and add .claude orchestration assets (push) Failing after 0s
notify-discord-release-notes.yml / chore: complete bd init setup and add .claude orchestration assets (pull_request) Failing after 0s
CodeQL / Analyze (java-kotlin) (pull_request) Failing after 3s
CodeQL / Analyze (actions) (pull_request) Failing after 3s
CI - Semantic PR Title / Validate PR Title (pull_request) Successful in 1s
CodeQL / Analyze (javascript-typescript) (pull_request) Failing after 3s
CI - Validate / Upload Event File (pull_request) Failing after 8s
CI - Validate / Check for DB Migrations (pull_request) Successful in 8s
CI - Validate / Flyway DB Migration Preview (pull_request) Has been skipped
CI - Validate / Flyway Migration Check (pull_request) Successful in 0s
CI - Validate / Backend Tests (pull_request) Failing after 4s
CI - Validate / Frontend Tests (pull_request) Failing after 3s
CI - Validate / Test Suite (pull_request) Failing after 0s
CI - Validate / Packaging Smoke Test (pull_request) Has been skipped
CI - Frontend Quality Thresholds / Frontend Lint Threshold Check (pull_request) Failing after 2m32s
notify-discord-release-notes.yml / Merge pull request 'chore: bd init + Claude Code project assets' (#5) from chore/bd-init-setup into develop (pull_request) Failing after 0s
6ddc8639a6
Follow-up to commit d728fd07. Adds the per-project Claude Code
orchestration configuration and bd workflow assets:

- .claude/agents, .claude/hooks, .claude/rules, .claude/skills,
  .claude/settings.json, .claude/.manifest.json
- AGENTS.md: append the Grimmory orchestration section consumed by
  the Beads workflow (epic vs standalone vs quick-fix paths,
  investigation-before-delegation rules, agent list)
- .gitignore: ignore .claude/.upgrades/ (Claude Code internal cache)
- .beads/config.yaml: dolt.auto-push: false to avoid retry latency
  on bd writes; can be re-enabled once remote-push is verified
zombor merged commit 1f606c9952 into develop 2026-05-11 00:51:39 +00:00
zombor deleted branch chore/bd-init-setup 2026-05-11 00:51:39 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
zombor/grimmory!5
No description provided.