Running any Setup.exe over an existing install wiped accounts.json, accounts.json.bak, settings.json and logs\ on the maintainer's machine (#91): Velopack uninstalls the previous version first and deletes the whole install root, and gclo stored its data in that same folder, %LOCALAPPDATA%\gclo.
Default data root is now %LOCALAPPDATA%\KofTwentyTwo\gclo (GcloPaths.DefaultDataRoot); the CLI's and the activity log's default follow. GCLO_DATA_DIR still overrides it.
No migration, as agreed: single user, single machine, green fields. The default vault scope is still unscoped, so the existing gclo:account:<id> Credential Manager entries keep working once accounts are re-added.
README, docs/CLI.md, the two store doc comments and the threat model (asset table + revision row) say where the data lives and why.
Tests: default root is the new path and is never under the install root; same for the log directory.
## What
Running any `Setup.exe` over an existing install wiped `accounts.json`, `accounts.json.bak`, `settings.json` and `logs\` on the maintainer's machine (#91): Velopack uninstalls the previous version first and deletes the whole install root, and gclo stored its data in that same folder, `%LOCALAPPDATA%\gclo`.
- Default data root is now `%LOCALAPPDATA%\KofTwentyTwo\gclo` (`GcloPaths.DefaultDataRoot`); the CLI's and the activity log's default follow. `GCLO_DATA_DIR` still overrides it.
- **No migration**, as agreed: single user, single machine, green fields. The default vault scope is still unscoped, so the existing `gclo:account:<id>` Credential Manager entries keep working once accounts are re-added.
- README, `docs/CLI.md`, the two store doc comments and the threat model (asset table + revision row) say where the data lives and why.
- Tests: default root is the new path and is never under the install root; same for the log directory.
Closes #91 (blocks #67). Part of #62.
## How it was tested
- `dotnet build -warnaserror` 0 warnings; `dotnet format --verify-no-changes` clean.
- `gclo.Engine.Tests` 425/425, `gclo.Cli.Tests` 129/129; line coverage 100% on `gclo.Engine` and `gclo.ViewModels`.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Running any
Setup.exeover an existing install wipedaccounts.json,accounts.json.bak,settings.jsonandlogs\on the maintainer's machine (#91): Velopack uninstalls the previous version first and deletes the whole install root, and gclo stored its data in that same folder,%LOCALAPPDATA%\gclo.%LOCALAPPDATA%\KofTwentyTwo\gclo(GcloPaths.DefaultDataRoot); the CLI's and the activity log's default follow.GCLO_DATA_DIRstill overrides it.gclo:account:<id>Credential Manager entries keep working once accounts are re-added.docs/CLI.md, the two store doc comments and the threat model (asset table + revision row) say where the data lives and why.Closes #91 (blocks #67). Part of #62.
How it was tested
dotnet build -warnaserror0 warnings;dotnet format --verify-no-changesclean.gclo.Engine.Tests425/425,gclo.Cli.Tests129/129; line coverage 100% ongclo.Engineandgclo.ViewModels.🤖 Generated with Claude Code