Non-secret variables in the auto-loaded store do not resolve at runtime (only "secret": true values resolve)

[komal-lt]

Summary

Variables defined in the auto-loaded variables store (~/.testmuai/kaneai/variables/*.json) only resolve at runtime when marked "secret": true. A non-secret ("secret": false) variable in the same file does not resolve — the field is left blank — while a secret variable in the same file resolves fine.

Severity

S2 — silent, and the failure is asymmetric (some vars work, some don't, from the same file).

kane-cli version

0.4.0

Repro

1. ~/.testmuai/kaneai/variables/dogfood.json:

   {
     "KANE_TEST_USER":     { "value": "user@example.com", "secret": false },
     "KANE_TEST_PASSWORD": { "value": "s3cret",           "secret": true  }
   }

2. A test that types {{KANE_TEST_USER}} into one field and {{KANE_TEST_PASSWORD}} into another.
3. Run via the TUI (or testmd run).

Actual

• {{KANE_TEST_PASSWORD}} (secret) → resolves and is typed. ✅
• {{KANE_TEST_USER}} (non-secret) → does not resolve; field left blank. ❌
• Changing KANE_TEST_USER to "secret": true fixes it.

Expected

Non-secret store variables should resolve at runtime just like secret ones. Per the docs the secret flag should only affect masking/routing, not whether a value resolves at all.

Likely cause / note

Docs say secret values route to the secrets store while non-secret ones "sync as plain variables" — that plain-variable sync (ATMS) appears to fail/no-op locally, so only secret-routed values are available at run time. Related: #69 (variables-file not feeding the resolver), #20.

[siddhant573]

Thanks for reporting @komal-lt . This is duplicate for the issue #69