start-issue

Automate Marshroom cart issue setup with branch creation, status tracking, and context injection. Start working on a Marshroom cart issue in the current repository. - Reads the Marshroom state file, filters cart issues matching the current repository, and creates a feature or hotfix branch with standardized naming ( Feature/#N or HotFix/#N ) - Mandatory state.json update: sets issue status to running via marsh start command or atomic jq write, with verification to ensure the update succeeds - Injects issue body as context so the agent understands the full scope of work before planning - Handles multiple matching issues by prompting user selection, and validates the git remote URL against both HTTPS and SSH formats - state.json update is MANDATORY . After creating the branch, you MUST update the issue status to running in ${MARSHROOM_STATE:-~/.config/marshroom/state.json} . If this fails, stop and report the error — do NOT silently continue. - Use marsh start if available; otherwise fall back to direct jq atomic write (see step 10). - Read ${MARSHROOM_STATE:-~/.config/marshroom/state.json} and parse the JSON - Extract the cart array. If the cart is empty, tell the user to add issues in the Marshroom app - Run git remote get-url origin to get the current repo's remote URL - Extract owner/repo from the remote URL (handle both HTTPS and SSH formats) - Filter cart entries where...