sascha.koenig
6be5e38021
support - Integrate Opencode terminal IDE with MCP integrations (Ref, Exa, Outline) - Add Beads AI-native issue tracking system (.beads/ + AGENTS.md) - Implement STT/PTT (speech-to-text push-to-talk) with whisper-cpp-vulkan - Add coding feature module with dev tools (beads, alejandra, bun, devpod, nixd) - Create AZPILOGISTIKTEST host configuration - Refactor Hyprland windowrules to new match: syntax - Upgrade nixpkgs/home-manager from 25.05 to 25.11 - Update Ollama to use Vulkan acceleration - Add lmstudio, rofi-project-opener, and various app updates - Add outline-key secret and mem0 service configuration chore: Add Opencode IDE, Beads issue tracking, STT/PTT, and nixpkgs 25.11 upgrade
1.3 KiB
1.3 KiB
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd onboard to get started.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --status in_progress # Claim work
bd close <id> # Complete work
bd sync # Sync with git
Landing the Plane (Session Completion)
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.
MANDATORY WORKFLOW:
- File issues for remaining work - Create issues for anything that needs follow-up
- Run quality gates (if code changed) - Tests, linters, builds
- Update issue status - Close finished work, update in-progress items
- PUSH TO REMOTE - This is MANDATORY:
git pull --rebase bd sync git push git status # MUST show "up to date with origin" - Clean up - Clear stashes, prune remote branches
- Verify - All changes committed AND pushed
- Hand off - Provide context for next session
CRITICAL RULES:
- Work is NOT complete until
git pushsucceeds - NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds