Align missing-schema errors: no env.ts starter snippets (dev + v1)

[yamcodes]

This was generated by AI during triage.

Summary

Align missing-schema error content across hosts and branches: errors must not embed example / starter env.ts code blocks. Prefer short, actionable text (expected paths, schemaPath, optionally arkenv init).

Related but separate: missing-schema severity (everyone throws) is #1470.

Policy

• No inline starter modules in thrown errors (no fenced src/env.ts examples).
• Applies to Bun, Vite, Next, and Nuxt wherever a missing-schema error is produced.
• Message wording may differ per host; no starter snippets must not.

Current behavior

dev

• Bun: missing-schema error includes an arktype Example \src/env.ts`` code block
• Next / Nuxt / Vite: no starter snippets in errors (Vite has no file-discovery miss path)

v1

• Bun: short error after fix(v1): drop env.ts starters; warn when Nuxt finds no schema #1468 (no starter) — keep it that way
• Vite / Next / Nuxt: no starter snippets

Desired behavior

• dev: remove Bun starter snippet; error stays a throw with paths / how to configure (severity unchanged — see Align missing-schema severity: all hosts throw (dev → v1) #1470)
• v1: confirm no host reintroduces starters; fix if any remain
• Optional consistent hint such as arkenv init is fine if it fits each package’s CLI story; not required to be identical wording

Acceptance criteria

On dev

• Bun missing-schema error contains no example env.ts / code fence starter
• Tests updated if they asserted on starter text
• Changeset(s) for affected packages

On v1

• No host embeds starter snippets in missing-schema errors (regression check / fix if needed)
• Changeset only if a code change is required

Out of scope

• Throw vs warn vs silent (Align missing-schema severity: all hosts throw (dev → v1) #1470)
• Adding starters to Vite/Next/Nuxt
• Expanding file-discovery on Vite dev

[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.

Agent Brief

Category: enhancement
Summary: Ensure missing-schema errors never embed example/starter env.ts snippets; align dev with the short-error style already on v1.

Current behavior:

• On dev, the Bun plugin missing-schema error includes an arktype Example src/env.ts fenced starter.
• Next / Nuxt / Vite on dev do not embed starters (Vite has no file-discovery miss path).
• On v1 (after fix(v1): drop env.ts starters; warn when Nuxt finds no schema #1468), Bun already uses a short error without a starter; other hosts likewise have no starter snippets.

Desired behavior:

• Policy: thrown missing-schema errors must not include inline starter modules or fenced example env.ts bodies.
• On dev, remove the Bun starter snippet; keep throwing with checked paths / how to set the schema path (severity is Align missing-schema severity: all hosts throw (dev → v1) #1470).
• On v1, verify no host still embeds starters; change code only if a regression is found.
• An optional arkenv init hint is allowed where the CLI story fits; wording need not be identical across hosts.

Key interfaces:

• Bun plugin missing-schema error construction — drop example module text; keep a short actionable throw.
• Any other host missing-schema error builders — must not gain or retain starter snippets.
• Do not change throw vs warn vs silent behavior in this issue.

Acceptance criteria:

• On dev, Bun missing-schema error has no example env.ts / code-fence starter
• Tests on dev updated if they asserted on starter text
• Changeset(s) for affected packages on dev
• On v1, no host embeds starter snippets in missing-schema errors (fix only if needed)
• Changeset on v1 only if code changed

Out of scope:

• Missing-schema severity alignment (Align missing-schema severity: all hosts throw (dev → v1) #1470)
• Adding starters to Vite / Next / Nuxt
• Adding Vite file-discovery on dev