Refactor Code Task

Problem

A Rails team needs help with a task in this area:

Use when refactoring Rails code to change structure without changing behavior — must write characterization tests and verify they pass on the current code BEFORE touching any production files, identify inputs/outputs keeping public interfaces stable, run verification after every step and the full suite at the end, and include a Stable behavior statement and Verification evidence showing actual command output under the Observed output label.

The team has asked for a concise implementation artifact that a reviewer can inspect without needing to observe the agent's process.

Output

Create answer.md with:

• a short plan for the work
• the concrete Rails-oriented artifact or recommendation
• the verification steps or quality gates that should be run
• any assumptions that affect the result