test(v1.1.7): upgrade or install on Windows and report behavior

[Fmarzochi]

Mission

Upgrade to or install EGC v1.1.7 on Windows and report whether it works correctly.

v1.1.7 includes a consolidated Windows crash fix (idempotent DB close, BOM-safe JSON parsing, async ping() fix, graceful libuv process exit). This issue tracks whether that fix holds in real environments.

Setup

Fresh install:

npm install -g @egchq/egc
egc init

Upgrade from an older version:

npm install -g @egchq/egc
egc repair

Requires Node.js 20+. Download at https://nodejs.org

Checklist

Installation

• npm install -g @egchq/egc completes without errors
• egc --version prints 1.1.7
• egc doctor passes all checks (green output)
• egc init starts the dashboard and opens the browser

Core behavior

• get_state returns context from a previous session (or empty on fresh install)
• update_state saves and persists across terminal restarts
• State file is created at %USERPROFILE%\.egc\state\<project>.md
• egc repair runs without errors after upgrade

Windows-specific (v1.1.7 fix validation)

• No crash or hang when closing the terminal while EGC is running
• No SyntaxError or Unexpected token errors when reading state files (BOM-safe JSON)
• No unhandledRejection from ping() in telemetry
• Process exits cleanly (no libuv error on shutdown)

Report

Leave a comment with:

• Windows version (e.g. Windows 11 23H2) and Node.js version
• Shell used (PowerShell, CMD, Git Bash, WSL)
• Any errors with full stack trace
• egc doctor output if something fails

This issue is part of the v1.1.7 validation campaign.