Ole-Morten Duesund
7be7f5e199
Adds internal/supervisor: a thin wrapper around os/exec that handles the zombie/leak/escalation concerns once, so phase-4 (bridge) and phase-5 (session glue) don't each have to re-derive them. Lifecycle (Stop): 1. Close stdin — well-behaved stdio servers exit on EOF 2. Send SIGTERM 3. Wait up to StopGrace (default 5s) for exit 4. SIGKILL if still alive Reaping is mandatory: a goroutine calls cmd.Wait so the kernel actually collects the child. Without it you accumulate zombies under N concurrent sessions. Tests exercise this via the helper-process pattern (TestMain re-execs the test binary in helper mode) — no shell or external binary dependency. Tests cover: empty Cmd validation, missing-binary error, echo round trip via stdin/stdout, stderr drainer collecting lines, SIGTERM-friendly graceful stop, SIGTERM-ignoring child escalating to SIGKILL (with a ready-on-stdout sync barrier so the test isn't racing the helper's signal.Notify), idempotent Stop, clean exit detection, non-zero exit detection, env override propagation. 89.6% coverage; remaining gap is unreachable-from-public-API defensive branches (pipe-creation failures under FD exhaustion, post-release Pid). Manual smoke test against a real `forgejo-mcp --transport stdio` is deferred to phase 4b's integration test (where it adds the most value). Closes forgejo-mcp-broker-zuq. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| hooks | ||
| .gitignore | ||
| config.yaml | ||
| issues.jsonl | ||
| metadata.json | ||
| README.md | ||
Beads - AI-Native Issue Tracking
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.
What is Beads?
Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
Learn more: github.com/steveyegge/beads
Quick Start
Essential Commands
# Create new issues
bd create "Add user authentication"
# View all issues
bd list
# View issue details
bd show <issue-id>
# Update issue status
bd update <issue-id> --claim
bd update <issue-id> --status done
# Sync with Dolt remote
bd dolt push
Working with Issues
Issues in Beads are:
- Git-native: Stored in Dolt database with version control and branching
- AI-friendly: CLI-first design works perfectly with AI coding agents
- Branch-aware: Issues can follow your branch workflow
- Always in sync: Auto-syncs with your commits
Why Beads?
✨ AI-Native Design
- Built specifically for AI-assisted development workflows
- CLI-first interface works seamlessly with AI coding agents
- No context switching to web UIs
🚀 Developer Focused
- Issues live in your repo, right next to your code
- Works offline, syncs when you push
- Fast, lightweight, and stays out of your way
🔧 Git Integration
- Automatic sync with git commits
- Branch-aware issue tracking
- Dolt-native three-way merge resolution
Get Started with Beads
Try Beads in your own projects:
# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Initialize in your repo
bd init
# Create your first issue
bd create "Try out Beads"
Learn More
- Documentation: github.com/steveyegge/beads/docs
- Quick Start Guide: Run
bd quickstart - Examples: github.com/steveyegge/beads/examples
Beads: Issue tracking that moves at the speed of thought ⚡