[Feature Request] Configurable schema filename

[jdillon]

Description

Allow the schema filename to be something other than .env.schema — via an env var, a package.json field, or a config key.

Motivation

Coding agents are commonly sandboxed with a deny rule on .env* so they can't read secret-bearing dotenv files. That rule catches .env.schema too, even though it's committed and holds no values — so the agent can't read or edit the one file it's most useful for it to maintain.

Proposed Solution

No preference on mechanism.

Alternatives

Naming the real file .env-schema and symlinking .env.schema to it. Works, but the symlink has to be explained to everyone who sees it.

--path .env-schema also appears to work, but only applies to that one call site — anything else running varlock load sees no schema.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[philmillman]

They typically respect .gitignore, so usually a !.env.schema is enough but we will discuss, I've certainly been bitten by this many times.

Thanks for the issue!

[philmillman]

@theoephraim I think we'll need to think through how this works with the hierarchy of files that gets loaded, whether this replaces just the .env.schema (likely) or replaces a whole pattern?