(v1) refactor(nuxt): deepen boot-gate / capture / flat thin-accessor locality

[yamcodes]

Summary

Follow-up to #1424 / #1458. After sharing strict client/server thin-accessor wiring, three deepenings remain outside that PR’s honesty-transport contract.

Part of #1105. Precursor: #1424.

Problem

1. Legacy schema parsing is duplicated between schema capture (boot gate / build-time validate) and the thin accessor. Nested vs flat / public-key decisions can drift.
2. boot-gate mixes two jobs — Jiti/alias schema load via capture, and applying coerced values into live runtimeConfig / boot-gate result state — which makes each harder to reason about and test alone.
3. Flat arkenv() entries (ArkType + Standard) still duplicate thin runtime wiring that the strict dispatcher already owns for client/server.

Desired behavior

• One shared, cycle-safe helper decides legacy nested vs flat shape and declared/public keys for both capture and thin accessors.
• Schema load via capture is separable from “run/ensure boot gate” (flatten, core coerce, write runtimeConfig, set boot-gate result).
• Flat package entries become type shells over the same thin-dispatch locality as strict client/server (no behavior change).

Acceptance criteria

• Capture and thin accessors share one legacy/flat schema-shape helper (no divergent nested detection)
• Boot-gate apply path can be exercised without re-testing Jiti alias plumbing, and vice versa
• Flat ArkType and Standard arkenv() runtimes share dispatch locality with strict entries; public behavior unchanged
• Client entries remain validator-free (@arkenv/core / ArkType / @arkenv/standard stay out of the client graph)
• Existing @arkenv/nuxt typecheck + vitest suite stays green

Out of scope

• Changing Nuxt honesty transport (boot gate + symmetric thin accessors) — already (v1) feat(nuxt): boot-time coercion into runtime payload + validator-free client env #1424
• Merging ArkType and Standard export/type surfaces (ADR 0007 subpaths stay)
• Vite literal-inlining / env-module transforms ((v1) feat(vite-plugin): env-module transform — canonical env object surface #1328 / (v1) feat(bun-plugin): env-module transform — canonical env object surface #1329)

[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: Deepen Nuxt boot-gate / capture / flat thin-accessor locality after #1424 without changing honesty-transport behavior

Current behavior:

• Schema capture (used by the Nuxt boot gate and build-time validate) and the thin accessor each decide legacy nested vs flat schema shape and which keys are public/declared. Those decisions can drift independently.
• The boot-gate module both loads schema via capture (Jiti/aliases/strict globals) and applies coerced values into live runtimeConfig plus boot-gate result state.
• Flat ArkType and Standard arkenv() package entries still encode their own thin runtime wiring, while strict client/server entries already share a dispatcher + parameterized auto-extend helper.

Desired behavior:

• One cycle-safe helper owns legacy nested vs flat shape and declared/public key extraction for both capture and thin accessors.
• Schema load via capture is separable from run/ensure boot gate (flatten env, core coerce, write runtimeConfig, set boot-gate result) so each path can be reasoned about and tested without the other.
• Flat ArkType and Standard arkenv() runtimes share the same thin-dispatch locality as strict client/server entries; public imports, types, and runtime behavior stay the same.
• Client package entries remain validator-free: no @arkenv/core, ArkType, or @arkenv/standard in the client graph. Keep the existing #arkenv/server-boot / boot-gate-result seams.

Key interfaces:

• Schema capture combine / public-key helpers and thin-accessor key collection — should share one nested-vs-flat shape contract
• Boot-gate “load schema via capture” vs “ensure/run boot gate” — separable modules with the same external scheduling (module registration + Nitro plugin + thin server hook)
• Flat arkenv() entries vs dispatchStrictThinArkenv / auto-extend — flat entries should reuse thin-dispatch locality without requiring strict-layout auto-extend unless that is already their behavior

Acceptance criteria:

• Capture and thin accessors share one legacy/flat schema-shape helper (no divergent nested detection)
• Boot-gate apply path can be exercised without re-testing Jiti alias plumbing, and vice versa
• Flat ArkType and Standard arkenv() runtimes share dispatch locality with strict entries; public behavior unchanged
• Client entries remain validator-free (@arkenv/core / ArkType / @arkenv/standard stay out of the client graph)
• Existing @arkenv/nuxt typecheck + vitest suite stays green

Out of scope:

• Changing Nuxt honesty transport (boot gate + symmetric thin accessors) — (v1) feat(nuxt): boot-time coercion into runtime payload + validator-free client env #1424
• Merging ArkType and Standard export/type surfaces (ADR 0007 subpaths stay)
• Vite literal-inlining / env-module transforms ((v1) feat(vite-plugin): env-module transform — canonical env object surface #1328 / (v1) feat(bun-plugin): env-module transform — canonical env object surface #1329)
• Re-doing the strict client/server withAutoExtend / thin dispatcher already landed on feat: (v1) boot-time coercion into runtime payload + validator-free client env #1458