23dab31a98
* fix(backend): forward base_branch override for same-repo subtasks via MCP The create_task_kandev MCP handler dropped base_branch silently unless the caller also passed a repository identifier. Same-repo subtasks then inherited the parent's repos verbatim, so "branch off feature/X" calls landed on the parent's branch instead. Forward base_branch at the top level of the WS payload and apply it as an override on the resolved repo list when no per-repo entries were supplied; explicit per-repo BaseBranch wins as before. * docs(backend): correct BaseBranch field comment to match actual fallback semantics The struct doc on `req.BaseBranch` claimed it won over explicit per-repo entries, but the override only fires when `len(req.Repositories) == 0`. Reword as a fallback applied to inherited/resolved repos when no per-repo list is supplied; explicit per-repo BaseBranch stays authoritative when set. Flagged by CodeRabbit and Greptile. * refactor(backend): forward top-level base_branch only when no per-repo entries When the MCP caller supplies a repo identifier, the per-repo base_branch is already authoritative on the backend side, so emitting a top-level base_branch in the same payload was dead weight that the backend's override gate explicitly ignored. Move the top-level forward into the else of hasRepo so the two paths are mutually exclusive and the wire contract reads as "top-level base_branch means inherit-with-override". Flagged by the Claude review bot.