`state.json` (and extensions dir) hardcoded under `$XDG_CONFIG_HOME` instead of `$XDG_STATE_HOME`

[agraboso]

What happened?

hunk stores its state file in $XDG_CONFIG_HOME/hunk/state.json right alongside its config file $XDG_CONFIG_HOME/hunk/config.toml.

Per the XDG Base Directory spec, $XDG_CONFIG_HOME is for user-editable configuration, while $XDG_STATE_HOME (defaulting to ~/.local/state) is for data that "should persist between (application) restarts, but that is not important or portable enough to the user that it should be stored in $XDG_DATA_HOME" — which, seems to me, describes state.json's contents exactly.

Steps to reproduce

Open $XDG_CONFIG_HOME/hunk and find state.json inside.

Expected behavior

state.jsonshould live in $XDG_STATE_HOME/hunk.

Version

0.19.0

[mikemikimike]

I opened PR #920 to fix this. It separates Hunk user-editable configuration from persistent state: state.json, globally discovered extensions, and managed extension installs now use XDG_STATE_HOME (falling back to the home state directory), while config.toml remains under XDG_CONFIG_HOME. The change reuses the existing path-resolution and extension discovery/install flow and adds regression coverage for both explicit XDG variables and fallbacks. Focused tests, typecheck, lint, dependency-boundary checks, changed-file formatting, and diff checks pass locally.