[b0dea]

Fixes #1246

The "Configuration is currently invalid" banner now lists the failing keys on the same line, e.g. Configuration is currently invalid: DATABASE_URL, API_TOKEN. Tools that keep only the first stderr line of a failed process (container termination reasons, CI annotations, error-tracker titles) now say which variable is wrong. Only key names are added, never values.

• checkForConfigErrors appends the failing keys to the banner.
• New unit test in error-checks.test.ts loads a real graph with two empty required items and one valid item, and checks the first non-empty stderr line names both failing keys and not the valid one. It fails on main and passes with the change.
• Updated the example output in getting-started/usage.mdx.

Existing smoke and framework tests match the banner with toContain('Configuration is currently invalid'), so they still match.

$ npx vitest run src/cli/helpers/test/error-checks.test.ts   # packages/varlock
 Test Files  1 passed (1)
      Tests  8 passed (8)

[pullfrog]

✅ No new issues found.

Reviewed changes: Reviewed the banner formatting change, its CLI and library callers, the regression test, and the documentation update.

• Error banner: Adds error-state key names in schema order without reading values or changing validation and exit behavior.
• Regression coverage: Checks that the first non-empty stderr line names both failing keys and excludes the valid key; all 23 focused tests passed, along with the Varlock build and changed-file lint check.
• Documentation and release note: Updates the usage example and adds a patch release note describing the diagnostic improvement.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}

[theoephraim]

thanks for the PR! ended up fixing in #1256 with some modifications.