McRitchie Studio

Agent Context

Found by dogfooding bin/release retro on rel-20260623-ba72f5 right after shipping #130. The conductor helper interpolates the answers JSON as an escaped Ruby string into 'rails runner "..."' and runs it via heroku run; heroku run's arg handling eats the \" escaping so the remote receives mangled JSON. Two repros on PROD board: (a) answers with parens -> remote bash 'syntax error near unexpected token (' ; (b) EVEN empty answers -> JSON::ParserError 'got worked:[],riction:[],ollowups:' (quotes + leading f eaten). Tests passed because they hit Release::Retro directly + the local CLI path, never the real heroku-run quoting round-trip. Fix: stop string-interpolating the payload into rails runner; pass it shell-safe — base64-encode the JSON and decode remotely, or via ENV, or stdin — and add a test that exercises the actual conductor/heroku-run command construction. Same shell-boundary class as the post-deploy --exit-code/Shellwords findings.