(v1) Examples & playgrounds for Standard Mode per integration

[yamcodes]

This was generated by AI during triage.

Natural continuation of #1199 (Standard Mode packaging). Spun out while closing #1436.

Summary

ArkType-mode examples/playgrounds exist for Vite, Bun, Next.js, and Nuxt. Standard Mode only has standalone examples (with-standard-schema, with-zod) — nothing that exercises @arkenv/*/standard under a real integration.

Scope (to decide here)

A full matrix (every integration × Standard Schema validator) may be overkill to maintain. Decide how wide the matrix should be, for example:

• One Standard Mode example per integration (Zod is enough), or
• A thinner set (e.g. only Next + Vite), or
• Playgrounds only / examples only

Acceptance criteria (once scope is chosen)

• Chosen integrations have at least one Standard Mode example or playground that installs @arkenv/standard (not arktype / @arkenv/core) and uses the /standard entry
• Docs or example READMEs point at the Standard Mode path where relevant

Out of scope

• ImportMetaEnvAugmented / ProcessEnvAugmented Standard Mode typing — superseded by the canonical env-object surface in (v1) Adopt the env object as the canonical surface for Vite/Bun (transform design) #1105
• Re-doing packaging from Distribution: Implement Standard Mode Packaging Strategy (Split core into @arkenv/core and @arkenv/standard) #1199

[pullfrog]

This run croaked 😵

The workflow encountered an error before any progress could be reported. Please check the link below for details.

  ^{｜ Rerun failed job ➔ ｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[yamcodes]

This was generated by AI during triage.

Note: SPA-mode typing helpers (ImportMetaEnvAugmented / ProcessEnvAugmented) are not fully superseded by #1105 — they remain for SPA mode. Tracking that work in #1440. This examples ticket can still decide whether Standard Mode SPA examples are in the matrix.