fix(parser): preserve JSON escapes in quoted args

[dannylin108]

Summary

• fix tokenizeCommand so quoted parsing does not strip arbitrary backslashes
• preserve escape sequences like \\n / \\t in double-quoted tokens
• keep single-quoted content literal
• add parser regression tests for --args-json handling

Why

--args-json payloads (especially prompt-rich JSON) could be corrupted during tokenization because backslashes were always consumed in quoted mode. This broke valid JSON before command handlers parsed it.

Validation

• pnpm build
• node --test dist/test/parser.test.js

---

fix #17

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bb665341b9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve escaped apostrophes in single-quoted args

The new single-quote branch closes on every ' character, so inputs that rely on \' now break with Unclosed quote instead of producing a literal apostrophe. For example, --args-json '{"prompt":"don\'t"}' (a common pattern when wrapping JSON in single quotes) parsed before this change but now fails, which can break prompt/JSON payloads containing apostrophes in existing pipelines.

Useful? React with 👍 / 👎.

[dannylin108]

fixed