(v1) Remove legacy schema/define API surface

[yamcodes]

This was generated by AI during triage.

Summary

On the v1 branch, remove the legacy schema/define API surface that Option 3 (#1333) drops from the product: arkenv(schema)-style entry, native accessor / define wiring, and ambient helper types (.d.ts augmentation helpers such as ImportMetaEnvAugmented / ProcessEnvAugmented).

This is the package-level cleanup. CLI scaffold + migration UX lives in #1332. Docs/ADR/examples/skill live in #1333.

Context

• (v1) Decide lasting stance on schema/define path; docs for canonical env object #1333 locked Option 3 (Remove / don’t offer) for v1.
• v0 (dev) keeps schema/define working — do not change dev behavior in this issue.
• (v1) SPA-mode env augment types for /standard (Vite + Bun) #1440 (Standard Mode ambient augment types) is closed out of scope; see .out-of-scope/spa-mode-ambient-augment-types.md.

Scope

• Remove or stop exporting schema/define public APIs from arkenv, @arkenv/vite-plugin, and @arkenv/bun-plugin on v1.
• Drop ambient augment type helpers and any docs/comments that teach them as a supported v1 path (package READMEs / JSDoc only — user-facing site docs are (v1) Decide lasting stance on schema/define path; docs for canonical env object #1333).
• Internal cleanup: dead define/rewrite paths that exist solely for the legacy surface, unused helpers, and tests that assert schema/define as a supported product path.
• Ensure the canonical env-object + transform surface remains the only supported Vite/Bun consumption path on v1.

Out of scope

• CLI init/migrate behavior ((v1) CLI scaffold: collapse to canonical env-object family + v0→v1 migration #1332)
• www guides, examples, ADR amendment, agent skill ((v1) Decide lasting stance on schema/define path; docs for canonical env object #1333)
• Any change to schema/define on the dev (v0) line

Related

• (v1) Adopt the env object as the canonical surface for Vite/Bun (transform design) #1105 (epic)
• (v1) Decide lasting stance on schema/define path; docs for canonical env object #1333 (product call + docs)
• (v1) CLI scaffold: collapse to canonical env-object family + v0→v1 migration #1332 (CLI)
• (v1) SPA-mode env augment types for /standard (Vite + Bun) #1440 (closed)

[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 (refactor)
Summary: On v1, remove the legacy schema/define public API and ambient augment helpers so only the env-object surface remains.

Current behavior:
Vite/Bun packages still expose or support a schema/define path (arkenv(schema)-style usage, native accessor / define wiring, ambient .d.ts helpers). That path remains valid on v0 (dev) but is product-rejected for v1 (#1333 Option 3).

Desired behavior:
On the v1 branch only, those legacy APIs and helpers are gone. Consumers use import { env } from "./env" with the transform/plugin pipeline. No public export, type helper, or package-level doc string presents schema/define as a supported v1 option. Tests cover the removal (legacy imports fail or are absent; env-object path still works).

Key interfaces:

• Public exports from arkenv, @arkenv/vite-plugin, and @arkenv/bun-plugin that exist solely for schema/define / ambient augmentation
• Ambient helper types historically used for SPA .d.ts augmentation (e.g. ImportMetaEnvAugmented, ProcessEnvAugmented)
• Plugin define/rewrite entry points that exist only to serve native-accessor schema mode (retain anything still required by the env-module transform)

Acceptance criteria:

• Work lands on the v1 branch only; dev / v0 schema/define behavior is unchanged
• Schema/define public APIs and ambient augment helpers are removed from v1 package surfaces
• Remaining Vite/Bun path is env-object + transform; tests assert legacy surface is unavailable
• No package README/JSDoc on v1 teaches schema/define as supported
• Changeset recorded appropriately for the breaking removal on v1

Out of scope:

• CLI scaffold and migration automation ((v1) CLI scaffold: collapse to canonical env-object family + v0→v1 migration #1332)
• www docs, examples, ADR 0015 amendment, agent skill ((v1) Decide lasting stance on schema/define path; docs for canonical env object #1333)
• Reviving ambient /standard augment types ((v1) SPA-mode env augment types for /standard (Vite + Bun) #1440 — closed / out of scope)