wg-admin/AGENTS.md

Agent Instructions

This project uses bd (beads) for issue tracking and Gitea for external issue tracking.

Gitea Issues Workflow

When asked to work on Gitea issues:

1. Read issue via API: curl -s "https://gitea.calmcacil.dev/api/v1/repos/{owner}/{repo}/issues/{number}"
2. Analyze requirements and scope
3. Create task list with todowrite for multi-step work
4. Implement fix following existing patterns
5. Commit with Closes #{number} in message (auto-closes issue)
6. Push to remote

See GITEA_ISSUES.md for detailed workflow.

Beads Workflow

Run bd onboard to get started with beads.

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:

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 sync
   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

CRITICAL RULES:

• Work is NOT complete until git push succeeds
• 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