feat: add --notes flag to bd create command (GH#830)

Add --notes flag to bd create command, enabling agents to set notes
during issue creation instead of requiring a separate update command.

Motivation: AI agents repeatedly tried to use --notes with bd create.
Context is fresh at creation time - forcing a two-step process means
context loss or workflow interruption.

Changes:
- cmd/bd/flags.go: Added --notes flag to common issue flags
- cmd/bd/create.go: Read and pass notes in both RPC and direct modes
- cmd/bd/update.go: Removed duplicate --notes flag definition
- internal/rpc/protocol.go: Added Notes field to CreateArgs
- internal/rpc/server_issues_epics.go: Process Notes in handleCreate
- cmd/bd/create_notes_test.go: Comprehensive test coverage
- website/docs/cli-reference/issues.md: Documentation

Also adds gitignore entries for Augment AI and .beads/redirect.

Co-authored-by: Leon Letto <lettol@vmware.com>

website/docs/cli-reference/issues.md

@@ -21,6 +21,9 @@ bd create <title> [flags]
 --type, -t        Issue type (bug|feature|task|epic|chore)
 --priority, -p    Priority 0-4
 --description, -d Detailed description
+--design          Design notes
+--acceptance      Acceptance criteria
+--notes           Additional notes
 --labels, -l      Comma-separated labels
 --parent          Parent issue ID
 --deps            Dependencies (type:id format)
@@ -37,6 +40,13 @@ bd create "Login fails with special chars" -t bug -p 1
 bd create "Add export to PDF" -t feature -p 2 \
   --description="Users want to export reports as PDF files"
 
+# Feature with design, acceptance, and notes
+bd create "Implement user authentication" -t feature -p 1 \
+  --description="Add JWT-based authentication" \
+  --design="Use bcrypt for password hashing, JWT for sessions" \
+  --acceptance="All tests pass, security audit complete" \
+  --notes="Consider rate limiting for login attempts"
+
 # Task with labels
 bd create "Update CI config" -t task -l "ci,infrastructure"