beads: default new bead status to deferred

New beads created via the 9p interface now start as deferred instead
of open. Planning/human review is required to promote a bead to open
before the scheduler can assign it to a worker.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

internal/p9/beads.go

@@ -768,7 +768,7 @@ func (b *BeadsFS) executeCtlOnStore(store bd.Storage, cmd string) error {
 			issue := &bd.Issue{
 				Title:       title,
 				Description: description,
-				Status:      bd.StatusOpen,
+				Status:      bd.StatusDeferred,
 				IssueType:   bd.TypeTask,
 				Priority:    2,
 			}
@@ -1269,7 +1269,7 @@ func (b *BeadsFS) createSubtaskOnStore(store bd.Storage, parentID, title, descri
 		ID:          childID,
 		Title:       title,
 		Description: description,
-		Status:      bd.StatusOpen,
+		Status:      bd.StatusDeferred,
 		IssueType:   bd.TypeTask,
 		Priority:    2,
 	}

mcptools/create_bead.sh

@@ -32,4 +32,4 @@ CMD="new '$TITLE' '$DESC'"
 [ -n "$CAP" ] && CMD="$CMD $CAP"
 
 echo "$CMD" | 9p write anvillm/beads/$MOUNT/ctl
-echo "created: $TITLE"
+echo "created (deferred): $TITLE"