···11-# Agent Instructions
22-33-This project uses **bd** (beads) for issue tracking. Run `bd onboard` to get started.
44-55-## Quick Reference
66-77-```bash
88-bd ready # Find available work
99-bd show <id> # View issue details
1010-bd update <id> --claim # Claim work atomically
1111-bd close <id> # Complete work
1212-bd sync # Sync with git
1313-```
1414-1515-## Non-Interactive Shell Commands
1616-1717-**ALWAYS use non-interactive flags** with file operations to avoid hanging on confirmation prompts.
1818-1919-Shell commands like `cp`, `mv`, and `rm` may be aliased to include `-i` (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.
2020-2121-**Use these forms instead:**
2222-```bash
2323-# Force overwrite without prompting
2424-cp -f source dest # NOT: cp source dest
2525-mv -f source dest # NOT: mv source dest
2626-rm -f file # NOT: rm file
2727-2828-# For recursive operations
2929-rm -rf directory # NOT: rm -r directory
3030-cp -rf source dest # NOT: cp -r source dest
3131-```
3232-3333-**Other commands that may prompt:**
3434-- `scp` - use `-o BatchMode=yes` for non-interactive
3535-- `ssh` - use `-o BatchMode=yes` to fail instead of prompting
3636-- `apt-get` - use `-y` flag
3737-- `brew` - use `HOMEBREW_NO_AUTO_UPDATE=1` env var
3838-3939-<!-- BEGIN BEADS INTEGRATION -->
4040-## Issue Tracking with bd (beads)
4141-4242-**IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
4343-4444-### Why bd?
4545-4646-- Dependency-aware: Track blockers and relationships between issues
4747-- Version-controlled: Built on Dolt with cell-level merge
4848-- Agent-optimized: JSON output, ready work detection, discovered-from links
4949-- Prevents duplicate tracking systems and confusion
5050-5151-### Quick Start
5252-5353-**Check for ready work:**
5454-5555-```bash
5656-bd ready --json
5757-```
5858-5959-**Create new issues:**
6060-6161-```bash
6262-bd create "Issue title" --description="Detailed context" -t bug|feature|task -p 0-4 --json
6363-bd create "Issue title" --description="What this issue is about" -p 1 --deps discovered-from:bd-123 --json
6464-```
6565-6666-**Claim and update:**
6767-6868-```bash
6969-bd update <id> --claim --json
7070-bd update bd-42 --priority 1 --json
7171-```
7272-7373-**Complete work:**
7474-7575-```bash
7676-bd close bd-42 --reason "Completed" --json
7777-```
7878-7979-### Issue Types
8080-8181-- `bug` - Something broken
8282-- `feature` - New functionality
8383-- `task` - Work item (tests, docs, refactoring)
8484-- `epic` - Large feature with subtasks
8585-- `chore` - Maintenance (dependencies, tooling)
8686-8787-### Priorities
8888-8989-- `0` - Critical (security, data loss, broken builds)
9090-- `1` - High (major features, important bugs)
9191-- `2` - Medium (default, nice-to-have)
9292-- `3` - Low (polish, optimization)
9393-- `4` - Backlog (future ideas)
9494-9595-### Workflow for AI Agents
9696-9797-1. **Check ready work**: `bd ready` shows unblocked issues
9898-2. **Claim your task atomically**: `bd update <id> --claim`
9999-3. **Work on it**: Implement, test, document
100100-4. **Discover new work?** Create linked issue:
101101- - `bd create "Found bug" --description="Details about what was found" -p 1 --deps discovered-from:<parent-id>`
102102-5. **Complete**: `bd close <id> --reason "Done"`
103103-104104-### Auto-Sync
105105-106106-bd automatically syncs with git:
107107-108108-- Exports to `.beads/issues.jsonl` after changes (5s debounce)
109109-- Imports from JSONL when newer (e.g., after `git pull`)
110110-- No manual export/import needed!
111111-112112-### Important Rules
113113-114114-- ✅ Use bd for ALL task tracking
115115-- ✅ Always use `--json` flag for programmatic use
116116-- ✅ Link discovered work with `discovered-from` dependencies
117117-- ✅ Check `bd ready` before asking "what should I work on?"
118118-- ❌ Do NOT create markdown TODO lists
119119-- ❌ Do NOT use external issue trackers
120120-- ❌ Do NOT duplicate tracking systems
121121-122122-For more details, see README.md and docs/QUICKSTART.md.
123123-124124-## Landing the Plane (Session Completion)
125125-126126-**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
127127-128128-**MANDATORY WORKFLOW:**
129129-130130-1. **File issues for remaining work** - Create issues for anything that needs follow-up
131131-2. **Run quality gates** (if code changed) - Tests, linters, builds
132132-3. **Update issue status** - Close finished work, update in-progress items
133133-4. **PUSH TO REMOTE** - This is MANDATORY:
134134- ```bash
135135- git pull --rebase
136136- bd sync
137137- git push
138138- git status # MUST show "up to date with origin"
139139- ```
140140-5. **Clean up** - Clear stashes, prune remote branches
141141-6. **Verify** - All changes committed AND pushed
142142-7. **Hand off** - Provide context for next session
143143-144144-**CRITICAL RULES:**
145145-- Work is NOT complete until `git push` succeeds
146146-- NEVER stop before pushing - that leaves work stranded locally
147147-- NEVER say "ready to push when you are" - YOU must push
148148-- If push fails, resolve and retry until it succeeds
149149-150150-<!-- END BEADS INTEGRATION -->
···11+# reqwless-linux
22+33+> A demonstration of a no_std reqwless http downloader for linux
44+55+## Usage
66+77+```bash
88+cargo run -- http://example.com
99+```
1010+1111+This prints the HTTP response body to stdout.
1212+1313+## Notes
1414+1515+- `no_std` + `no_main` binary using Linux libc syscalls
1616+- Uses `reqwless` with `default-features = false` (HTTP only)
1717+- Uses fixed-size stack buffers for request/response and output chunks
1818+- Performs best-effort low-allocation operation (no `String`/`Vec` in app code)