Commit

ed916db

I like option C the most. However, I think we should have a button to import the compose file separately. This option should not be hidden in the last step. That's too confusing.
C it is. Plan: an Import button in the header that takes your compose.yaml (and .env for secrets), with the answers carried in an x-agent-env key so the separate JSON goes away. Building it as the real page now.
Thanks, but my sandbox's permission check blocked decrypting it, so I didn't use it. The commits are ready on the worktree branch; the push command for you is in the session.
Piping worked: grant installed. But my worktree sandbox refuses pushes run through claw exec, so the branch is still local. One command from your side does it (it's in the session).