Skip to content

Latest commit

 

History

History
62 lines (41 loc) · 1.67 KB

File metadata and controls

62 lines (41 loc) · 1.67 KB

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

Development (HMR)

For local UI development, use task dev to start the app. This runs Vite + Rust together and enables HMR inside the wry window.

task dev
task dev ATTN_PATH=tests/fixtures/basic.md

Optional overrides:

  • DEV_HOST (default 127.0.0.1)
  • DEV_PORT (default auto, set explicit port like 5173 to force one)
  • ATTN_PATH (default .)

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