charlie: next/v3 docs and playbooks parity with main for Raw, Conditional, and tests

[charliecreates]

Subtask of #348. Align docs and .charlie playbooks on next/v3 with main for Raw and Conditional semantics and running jsx-email tests so v3 contributors have branch-appropriate guidance.

Target branch

All work for this issue should be implemented against the next/v3 branch.

• Branch from origin/next/v3.
• Open pull requests with base set to next/v3 (not main).

Context

As next/v3 is brought into alignment with main for Raw/Conditional behavior and core correctness, we also want the written guidance to match. Today, main has more complete docs and .charlie playbooks describing:

• How the Raw and Conditional pipeline is expected to behave (including MSO/Outlook conditionals and Raw-inside-Conditional cases).
• How to run jsx-email tests locally in a way that mirrors CI (including FORCE_COLOR usage and the relevant Moon tasks).

next/v3 should carry branch-specific versions of this guidance so contributors working on v3 know to target next/v3, understand the intended behavior, and can run the right verification commands.

Implementation notes

When working this issue:

1. Audit the docs and .charlie content on main related to Raw, Conditional, and running jsx-email tests like CI.
2. Port or adapt that content into next/v3, updating any branch-specific details (for example, which Moon tasks exist on next/v3, or where workflows differ) so the instructions are accurate for v3.
3. Make sure each relevant doc or playbook explicitly calls out that PRs for this alignment work should target the next/v3 branch and reference charlie: head vs next/v3 #348 for the broader context of keeping next/v3 and main aligned.

[charliecreates]

Expand this to see my work.

• Reset the working branch ai-354-charlie-next-v3-docs-and-playbooks-parity-w hard to origin/next/v3 so all changes are based on the correct target branch and recent Raw/Conditional pipeline work from #360.
• Scanned the repo root (including moon.yml, docs/, packages/, apps/) on next/v3 and confirmed there was no existing .charlie directory, meaning playbooks needed to be added rather than edited.
• Reviewed .charlie contents on origin/main (notably .charlie/playbooks/conditional-and-raw.md and .charlie/playbooks/run-jsx-email-tests.md) plus docs/components/raw.md and docs/components/conditional.md on both main and next/v3 to understand what guidance to port and confirm docs parity for <Raw> and <Conditional>.
• Compared root moon.yml and packages/jsx-email/moon.yml between origin/main and origin/next/v3 to map which Moon tasks and FORCE_COLOR behaviors exist on next/v3 and must be reflected in v3-specific instructions, and cross-checked .github/workflows/test*.yml to mirror CI commands.
• Created .charlie/instructions/pull-request.md on next/v3 with repo-specific rules for Charlie, including Moon usage, Vitest + .snapshots conventions, FORCE_COLOR=1 requirements, and explicit guidance that Raw/Conditional alignment PRs must branch from and target next/v3 while referencing #348.
• Added .charlie/playbooks/conditional-and-raw.md on next/v3 that documents <Conditional>/<Raw> behavior (including MSO conditionals, expression conditionals, closing <![endif]--> expectations, and Raw-inside-Conditional no-duplication) plus pnpm moon run jsx-email:test and pnpm moon run jsx-email:tsc usage tailored to next/v3.
• Added .charlie/playbooks/run-jsx-email-tests-like-ci.md describing how to run packages/jsx-email tests locally with FORCE_COLOR=1 and the relevant Moon tasks so contributors can mirror the next/v3 CI workflows when working on Raw/Conditional and core correctness.
• Staged and committed the new .charlie files with git commit -m "chore(charlie): add next-v3 playbooks for Raw, Conditional, and tests", which recorded 3 new files and 128 insertions for the ai-354-charlie-next-v3-docs-and-playbooks-parity-w branch.
• Reviewed the body and structure of #360 to mirror its formatting and "Verification" section when drafting the new PR for this docs/playbooks work.
• Opened PR #361 (base: next/v3, head: ai-354-charlie-next-v3-docs-and-playbooks-parity-w) titled chore(charlie): align next/v3 docs/playbooks with main for Raw, Conditional, tests, with a filled-out template, Resolves #354 / Refs #348, and an explicit note that this is a docs-only .charlie change with verification steps limited to checking Moon tasks and CI workflows for the referenced commands.

[charliecreates]

Opened #361 to add the next/v3-specific docs and playbooks.

Changes

• Ported Charlie PR instructions to next/v3

  • Added .charlie/instructions/pull-request.md based on origin/main, but wired to the next/v3 setup:
    • Test command now uses pnpm moon run jsx-email:test instead of the jsx-email:test.ci task that only exists on main.
    • References the shared/vitest.config.ts file used on next/v3.
    • Keeps the existing guidance around repo:lint, snapshots, Conventional Commits, etc.
  • Added an explicit note for the alignment effort: for work on <Raw> / <Conditional> behavior and core correctness, branch from origin/next/v3, set PR base to next/v3 (not main), and mention #348 in the PR description.

• Next/v3 version of the Conditional/Raw playbook

  • Added .charlie/playbooks/conditional-and-raw.md that mirrors the main-branch playbook but is explicitly marked as the next/v3 copy.
  • Commands are updated for next/v3:
    • Build artifacts: pnpm moon run plugin-inline:build plugin-minify:build plugin-pretty:build && pnpm moon run jsx-email:build
    • Tests: pnpm moon run jsx-email:test (the Moon task already sets FORCE_COLOR=1 like CI)
    • TypeScript: pnpm moon run jsx-email:tsc
  • References now point at shared/vitest.config.ts and packages/jsx-email/moon.yml.
  • Includes a short branch-targeting block that repeats the next/v3 / #348 guidance for Raw/Conditional alignment work.

• Next/v3 playbook for running jsx-email tests like CI

  • Added .charlie/playbooks/run-jsx-email-tests-like-ci.md, again adapted from main but aligned with the next/v3 workflow:
    • Step 1: pnpm install, then pnpm moon run plugin-inline:build plugin-minify:build plugin-pretty:build, then pnpm moon run jsx-email:build.
    • Step 2: run the package tests via pnpm moon run jsx-email:test (the Moon task configures FORCE_COLOR=1 on next/v3).
    • Step 3: optional snapshot updates using pnpm vitest -u --config ../../shared/vitest.config.ts.
    • Step 4: pnpm moon run jsx-email:tsc.
  • Includes the same “branch from origin/next/v3, base=next/v3, mention #348” note so contributors doing alignment work get clear branch-specific instructions.

• Docs parity check for Raw/Conditional components

  • Verified that docs/components/raw.md and docs/components/conditional.md are already identical between origin/main and origin/next/v3, so no content changes were needed there. The new .charlie files carry the branch-specific contributor guidance requested in charlie: next/v3 docs and playbooks parity with main for Raw, Conditional, and tests #354.

Scope & self-review notes

• This PR is docs-only: it adds .charlie instructions/playbooks and does not touch any runtime TypeScript/JS, tests, or workflows.
• I did not run pnpm moon run repo:lint, jsx-email:build, jsx-email:test, or jsx-email:tsc for this change, since it only introduces documentation/Charlie configuration and doesn’t affect shipping code.
• The automated self-review surfaced a number of pre-existing next/v3 changes (pnpm workspace flags, CLI test reshaping, Playwright version differences, etc.) that live outside this diff and came in via earlier alignment PRs (e.g. chore(charlie): align next/v3 core correctness with main for compile, preview, config #355, chore(charlie): align next/v3 Raw and Conditional pipeline with main #360). I intentionally left those untouched to keep charlie: next/v3 docs and playbooks parity with main for Raw, Conditional, and tests #354 focused strictly on docs and playbooks for Raw, Conditional, and test-running guidance on next/v3.