expose suggested_branch_name on the shared ticket resource
reuse the existing BuildSuggestedTicketBranchName logic instead of duplicating slug generation
cover the API and MCP ticket responses with focused assertions
Verification
npm run build
php artisan test tests/Feature/Api/TicketApiTest.php tests/Feature/Mcp/KanbanGitMcpTest.php
## Summary
- expose `suggested_branch_name` on the shared ticket resource
- reuse the existing `BuildSuggestedTicketBranchName` logic instead of duplicating slug generation
- cover the API and MCP ticket responses with focused assertions
## Verification
- `npm run build`
- `php artisan test tests/Feature/Api/TicketApiTest.php tests/Feature/Mcp/KanbanGitMcpTest.php`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
suggested_branch_nameon the shared ticket resourceBuildSuggestedTicketBranchNamelogic instead of duplicating slug generationVerification
npm run buildphp artisan test tests/Feature/Api/TicketApiTest.php tests/Feature/Mcp/KanbanGitMcpTest.php