[BUG]: varlock init has surprising results in monorepos

[apike]

varlock version

0.1.3

Steps to reproduce

1. Have a repo where .env files are not at the root of the project
2. Run pnpm exec varlock init

What is expected?

Ideally: It will find the .env/.env.example files in your project, and help you create an .env.schema for each.

Simpler: It will notice there are .env files elsewhere, and ask you to run pnpm exec varlock init from those locations.

What is actually happening?

It creates a blank .env.schema in your project root, then asks you to review and update it.

System Info

Any additional comments?

No response