docs: changelog — nodeless npm install + release pipeline fixes

Author: yethikrishna

CHANGELOG.md

@@ -20,6 +20,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Subagent step budgets bounded by the parent** — a spawned agent now gets `min(default, parent's remaining steps)` instead of a flat 100. The effort dial caps the parent, so it now bounds the whole swarm: at `low` (30) children can no longer get a fresh 100-step allowance, and a nearly-depleted parent cannot spawn runaway children.
 
 ### Fixed
+- **npm-installed CLI no longer requires Node at run time** (`exec: node: not found` in shells without Node). npm's generated bin shims are Node scripts, but Node is only guaranteed at *install* time — `postinstall` now downloads the platform binary eagerly and rewrites the shims (`levelcode`, `levelcode.cmd`, `levelcode.ps1`) to exec `~/.config/levelcode/levelcode` directly. Download logic moved to a shared `installer.js` used by both the eager postinstall path and the Node fallback launcher.
+- Release pipeline targeted the upstream `LevelCodeAI/levelcode-community` repo for both the GitHub Release upload and the web download proxy — every release attempt 404'd there after binaries built. Both now default to this repository (workflow fix + `LEVELCODE_RELEASES_BASE_URL` env override on the download route).
 - Provider config and model-catalog cache ignored `LEVELCODE_HOME` — `provider-fs` and `model-catalog` used raw `os.homedir()`, so hermetic environments loaded the host's real `providers.json` (and `--print-config` reported paths the runtime didn't consult). Both now resolve through `getUserHomeDir()`.
 - CLI session/credential storage ignored `LEVELCODE_HOME` — `getConfigDir` used raw `os.homedir()`, breaking hermetic test/live environments and diverging from the monorepo home-dir convention. Both cli and sdk now resolve through `getUserHomeDir()`.
 - Resuming or forking a run-state persisted without `fileContext` (or with a partial agent state) crashed mid-run at `fileContext.agentTemplates` / `agentState.childRunIds` with an opaque TypeError after the fork clone was already on disk. `applyOverridesToSessionState` backfills defaults, so legacy/hand-crafted saves resume cleanly and the model call fails with a real reason.