wizard: write_env quotes apostrophes as shell syntax that dotenv readers do not decode

### Skill `wizard` (`template.sh`) ### Version or commit a496f55 ### Harness and version Claude Code 2.1.308, installed with skills.sh (`npx skills add`). ### Model and effort Opus 5.5, high effort. Not context-related: it reproduces with the template alone. ### What happened `write_env` stores `a'b` as `KEY='a'\''b'`. That is shell concatenation syntax, and dotenv readers do not decode it. The wizard's own shell keeps the correct value, but the app that reads `.env` gets a different one. ```bash printf "%s\n" "KEY='a'\\''b'" > .env bun -e 'console.log(JSON.stringify(process.env.KEY))' # "a" ``` A password or token with an apostrophe is saved incorrectly, and nothing reports it. This is separate from #1260, which is the bash 3.2 round trip inside `_existing`. ### What you expected `write_env` writes values in a form that dotenv readers (Bun, Node `dotenv`) load back unchanged. For example, use double quotes when the value contains `'`, and escape `"`, `\`, and `$` inside them. ### Checks - [x] This issue is about one problem. - [x] I searched open and closed issues for a duplicate.