Escalation: update_ticket MCP tool returns

Tinker

Home Epics Escalation: update_ticket MCP tool returns ForbiddenAttributesErrorEdit

Escalation: update_ticket MCP tool returns ForbiddenAttributesError

Cancel

Title *

Project *

Description

Escalation: update_ticket MCP tool returns ActiveModel::ForbiddenAttributesError

## Issue

All `update_ticket` MCP tools (tinker-orchestrator, tinker-worker) return 422 error when trying to update ticket fields:

```
ActiveModel::ForbiddenAttributesError
```

## What Was Attempted

Tried updating ticket #134 with:
- New title
- New description
- Clearing pull_request_url

All attempts failed with the same error across multiple agent tool contexts.

## Root Cause

Rails StrongParameters - the controller is not permitting the parameters being passed from the MCP bridge. The Go bridge is likely sending parameters that the Rails controller doesn't have in its permit() list.

## Impact

- Cannot update ticket descriptions after creation
- Cannot clear/update PR URLs
- Agents cannot mark their work as complete with updated context
- Planner cannot refine requirements on existing tickets

## Suggested Fix

Check `app/controllers/api/v1/tickets_controller.rb` (or similar) in the `update` action. Ensure the ticket params permit:

```ruby
def ticket_params
  params.require(:ticket).permit(:title, :description, :priority, :pull_request_url, :working_memory, ...)
end
```

The MCP bridge in Go needs to send parameters wrapped in a `ticket` key, or the controller needs to be updated to accept the parameter format the bridge is sending.

## Related

- Ticket #134 (where this was discovered)
- Comment #138 on ticket #134 (has the intended updated content)