fnox daemon clear can be misleading with profile-scoped daemon caches

[jeiea]

Reproduction Steps

1. Enable the fnox daemon in a project that has multiple profiles, for example default, dev, and stage.
2. Run a command that resolves a secret through a non-default profile:

   fnox exec --profile dev -- printenv SOME_SECRET

3. Update the backing provider value for that secret, for example in 1Password.
4. Run:

   fnox daemon clear
   fnox daemon status

5. Run the same profile-scoped command again:

   fnox exec --profile dev -- printenv SOME_SECRET

6. Compare with:

   fnox --profile dev daemon status
   fnox --profile dev daemon clear

Expected Behavior

After running fnox daemon clear, I expected the stale daemon cache affecting my project commands to be cleared, including caches used by profile-scoped commands such as fnox exec --profile dev.

Actual Behavior

fnox daemon clear only clears the default profile daemon. fnox daemon status can show cached_entries: 0, while fnox --profile dev daemon status still shows cached entries. As a result, fnox exec --profile dev may continue injecting stale secret values until fnox --profile dev daemon clear is run.

Suggestion

Please consider adding a flag to clear all profile daemon caches, for example:

fnox daemon clear --all-profiles

Alternatively, make fnox daemon clear clear all profiles by default, since users may not realize that daemon caches are profile-scoped.

[jdx]

Implemented this in PR #581: #581

The change makes fnox daemon clear scan the fnox runtime directory and send Clear to every running daemon socket, so profile-scoped daemon caches are cleared together. It also adds a regression test covering default + non-default profile caches.

This comment was generated by Codex.