librarian AGENTS.md

Librarian

This project uses Librarian for semantic search and graph-based code navigation. See .librarian/rules.md for the full guidance.

Before exploring with grep/find, try:

• librarian search "<topic>" — semantic search over docs + code
• librarian context "<topic>" — deep briefing: related docs + code refs
• librarian neighbors <node> — what does X connect to?
• librarian path <from> <to> — how do these pieces relate?

Read .librarian/out/GRAPH_REPORT.md for a topology snapshot (god nodes, communities, cross-cluster edges).

Beads Issue Tracker

This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work
bd close <id>         # 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

Session Completion

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

1. File issues for remaining work - Create issues 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. PUSH TO REMOTE - This is MANDATORY:

   git pull --rebase
   bd dolt push
   git push
   git status  # MUST show "up to date with origin"
   

5. Clean up - Clear stashes, prune remote branches
6. Verify - All changes committed AND pushed
7. Hand off - Provide context for next session