Why is the default AGENTS.md so heavy?

[KevinWuWon]

Below is what I see in a AGENTS.md in a fresh repo after initializing beads.

Why does beads mandate all the stuff in the mandatory workflow section? Seems out of its place to require a push to remote after every issue. What if pushing deploys and I don't want the risk of deploying right before I leave and go off the grid?

I'd delete it but I fear if these rules have been added for a good reason.

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:**

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

[KevinWuWon]

Also, what does "Provide context for next session" mean? This doesn't make sense unless there's some other rule saying how to provide context.

[llbbl]

think it has to do with handoff thing for the gas town skill