Set a new issue's board status to Backlog when gh:create files it #3549

Overview

bun run gh:create adds a new issue to the NodeSpace project board but leaves its Status empty. The issue is on the board in no column, so it does not show among the filed-but-unqueued work until someone sets a status by hand.

Problem Statement

createIssue in scripts/github-client.ts calls addIssueToProject and stops there. The Status field is only ever written by gh:status. Eight issues filed in one sitting all landed with an empty Status and needed eight separate gh:status calls; another recently filed issue is in the same state. Reading an issue's board state then shows a project item with a blank status, which is easy to misread as the issue not being on the board at all.

Proposed Solution

After adding the new issue to the board, set its Status to Backlog, the value the workflow guide gives for an issue that is filed but not queued. A failure to set it is reported as a warning, like a failure to add the issue to the board: the issue exists and its number is what the caller needs.

Documentation

• Issue workflow - the six Status values and what Backlog means
• Updates: development/issue-workflow.md (say that gh:create files an issue as Backlog)

No ADR covers the project board tooling.

Acceptance Criteria

• An issue created with bun run gh:create is on the board with Status Backlog
• The status is set using the project item id returned by the add, with no second listing of the board's items
• If the issue is added to the board but the status write fails, the command still succeeds, prints the issue number and URL, and warns that the status was not set
• If the add to the board fails, the existing warning is unchanged and no status write is attempted
• gh:status behaves as before, and shares the status write with the create path instead of duplicating it
• scripts/gh-utils.test.ts covers the create path setting the status, and the two failure cases
• development/issue-workflow.md says a new issue is filed as Backlog
• Code passes bun run quality:fix
• Tests pass (bun run test:changed)

Technical Specifications

Reference Files

• scripts/github-client.ts - createIssue, addIssueToProject, updateIssueStatus and the Status option ids
• scripts/gh-utils.ts - the issues:create command and what it prints
• scripts/gh-utils.test.ts - existing tests; tests under scripts/ use bun:test and stay DOM-free

Implementation Details

• addIssueToProject already returns the new project item's id. Pass it to the status write.
• The status write is one GraphQL mutation; extract it from updateIssueStatus so both paths call it.