Seed default config on install; share defaults JSON with runtime

The defaults now live in a single file, scripts/config.default.json:

- src/config.ts imports it via 'with { type: "json" }' and derives
  DEFAULT_CONFIG (with seconds->ms conversion at the boundary), so the
  CLI help text always matches what the seeded user config contains.
- scripts/install.sh copies the same file to
  $XDG_CONFIG_HOME/move/config.json only if no file is already there.
  Existing configs (yours or from a previous install) are never
  overwritten.
- scripts/uninstall.sh does not touch the user config file at all,
  following the strict Unix convention. It does print a one-line
  notice pointing at the path so the user can rm -rf the dir
  themselves if they want a fully-clean removal.
- tsconfig.json gains resolveJsonModule:true so tsc accepts the JSON
  import.
- A small runtime assertion in src/config.ts (assertSeedShape) fails
  loudly if the seed file is missing keys or has wrong types.
- README Configuration section documents the seed behavior; Uninstall
  section documents the leave-config-behind policy with the rm-it-
  yourself command; Files table gains scripts/config.default.json.

This commit is contained in:

nokeo08

2026-06-17 13:13:49 -05:00

parent 940113019d

commit 7714a6ad1a

6 changed files with 145 additions and 29 deletions

									
										scripts/config.default.json
									
		+7
		
												View File
												
				@@ -0,0 +1,7 @@

				{

				  "moveInterval": 240,

				  "checkInterval": 10,

				  "stepDelay": 50,

				  "stepCount": 250,

				  "verbose": false

				}