energy-state-analyzer 0.8.0 → 0.9.0

package/.vscodeignore

@@ -18,6 +18,8 @@ vsc-extension-quickstart.md
 **/obj/**
 **/fable_modules/**
 **/.vscode-test.*
+*.tgz
+*.vsix
 .claude/**
 CLAUDE.md
 energy-state.md

package/AGENTS.md

@@ -2,8 +2,8 @@
 
 ## Project overview
 
-Energy State Analyzer is a VS Code extension and CLI that analyze Python, F#, TypeScript, and
-Kotlin through `web-tree-sitter` grammars in `grammars/`. Product source is F# and is compiled
+Energy State Analyzer is a VS Code extension and CLI that analyze Python, F#, TypeScript, Kotlin,
+and C++ through `web-tree-sitter` grammars in `grammars/`. Product source is F# and is compiled
 by Fable 5 to JavaScript before webpack packages the extension and CLI.
 
 See `energy-state.md` for the original design rationale and `docs/fable-rewrite-plan.md` for the
@@ -43,7 +43,7 @@ order.
 - **`src/Core/`**: host-independent synchronous detector pipeline, tree-sitter facade,
   suppression, scanning, and report rendering. `Analyze.fs` is the one detector composition
   point shared by extension and CLI.
-- **`src/Languages/`**: grammar-specific `LanguageAdapter` records for the four supported
+- **`src/Languages/`**: grammar-specific `LanguageAdapter` records for the five supported
   analyzed languages.
 - **`src/Extension/`**: VS Code Fable facade, configuration boundary, grammar cache, analysis
   orchestration, editor/Problems presentation, and `Extension.fs` composition root. The narrow
@@ -56,7 +56,8 @@ order.
   bindings, and Fable entry point. Scan, legacy single-file, `--report`, `--base-ref`, and
   thresholds share the Core pipeline.
 - **`tests/`**: F# Scriptorium suites. `src/test/fixtures/` is retained only as multi-language
-  analyzer input, including `.ts` fixtures; it is not TypeScript product or test code.
+  analyzer input, including `.ts` and `.cpp` fixtures; it is not product or test implementation
+  source in those languages.
 
 The extension composition root owns lifecycle state, grammar caches, decorations, diagnostics,
 commands, and editor/document/configuration event subscriptions. Presentation never leaks into

package/CHANGELOG.md

@@ -1,5 +1,5 @@
 ---
-last_commit_released: 01777cc27c9c08136661a2f1e21409cdf94f05ce
+last_commit_released: 49ef35194407cbc9ca2f63e4248fd1683e03a3f6
 name: energy-state-analyzer
 updaters:
   - command: npm version {version} --no-git-tag-version --allow-same-version
@@ -11,6 +11,26 @@ All notable changes to the "energy-state-analyzer" extension are generated by
 [EasyBuild.ShipIt](https://github.com/easybuild-org/EasyBuild.ShipIt) from
 [Conventional Commits](https://www.conventionalcommits.org/).
 
+## 0.9.0 - 2026-09-01
+
+### 🚀 Features
+
+* *(cpp)* Add C++ analysis support (#61) ([8a81808](https://github.com/cardamomcode/energy-state-analyzer/commit/8a818080a901b0a93d5b2c55ba75f30e36391133))
+
+### 🐞 Bug Fixes
+
+* *(ci)* Handle energy diff reports from forks (#63) ([3ac23aa](https://github.com/cardamomcode/energy-state-analyzer/commit/3ac23aa0f1167ec2d96aae7f75e5518587097c12))
+
+<strong><small>[View changes on Github](https://github.com/cardamomcode/energy-state-analyzer/compare/db726199ca6214ebdf2da5fa0a73d4f29bf6be97..49ef35194407cbc9ca2f63e4248fd1683e03a3f6)</small></strong>
+
+## 0.8.1 - 2026-08-31
+
+### 🐞 Bug Fixes
+
+* *(extension)* Preserve VS Code allowlist values (#59) ([db72619](https://github.com/cardamomcode/energy-state-analyzer/commit/db726199ca6214ebdf2da5fa0a73d4f29bf6be97))
+
+<strong><small>[View changes on Github](https://github.com/cardamomcode/energy-state-analyzer/compare/01777cc27c9c08136661a2f1e21409cdf94f05ce..db726199ca6214ebdf2da5fa0a73d4f29bf6be97)</small></strong>
+
 ## 0.8.0 - 2026-08-31
 
 ### 🚀 Features

package/README.md

@@ -1,10 +1,10 @@
 # Energy State Analyzer
 
-Visualizes "energy states" in Python, F#, TypeScript, and Kotlin code as you edit: parts of a file that are complex, deeply nested, or otherwise harder to understand and maintain get highlighted with colored gutter icons, inline decorations, and entries in the Problems panel.
+Visualizes "energy states" in Python, F#, TypeScript, Kotlin, and C++ code as you edit: parts of a file that are complex, deeply nested, or otherwise harder to understand and maintain get highlighted with colored gutter icons, inline decorations, and entries in the Problems panel.
 
 ## Features
 
-Real-time analysis of the active Python, F#, TypeScript, or Kotlin file, re-run on every edit and on editor focus change, via these detectors (see [docs/detectors](docs/detectors/README.md) for full detail on each):
+Real-time analysis of the active Python, F#, TypeScript, Kotlin, or C++ file, re-run on every edit and on editor focus change, via these detectors (see [docs/detectors](docs/detectors/README.md) for full detail on each):
 
 - [Cyclomatic complexity](docs/detectors/cyclomatic-complexity.md), too many independent execution paths.
 - [Cognitive complexity](docs/detectors/cognitive-complexity.md), too hard to read due to nesting.
@@ -36,14 +36,14 @@ The name is a deliberate analogy to thermodynamics: a function's "energy" is its
 The same detectors also run headlessly, without VS Code, useful for CI or for an AI coding agent that wants to check the complexity of code it just generated and keep refactoring until it's clean:
 
 ```bash
-npx energy-state-analyzer path/to/file.py   # or .fs / .fsx / .ts / .kt
+npx energy-state-analyzer path/to/file.py   # or .fs / .fsx / .ts / .kt / .cpp / .hpp
 ```
 
 See [docs/cli.md](docs/cli.md) for scanning a whole repo, aggregated markdown/JSON/human reports, and diffing a PR against a base branch.
 
 ## Requirements
 
-The extension activates automatically when you open a Python, F#, TypeScript, or Kotlin file; it bundles its own grammars for parsing (via `web-tree-sitter`), so no external tools are required. F# files only get a `fsharp` language ID (and so trigger analysis) if you have an F# language extension installed (e.g. [Ionide](https://ionide.io/)), VS Code otherwise treats `.fs` files as plain text.
+The extension activates automatically when you open a Python, F#, TypeScript, Kotlin, or C++ file; it bundles its own grammars for parsing (via `web-tree-sitter`), so no compiler or external parser is required. F# files only get a `fsharp` language ID (and so trigger analysis) if you have an F# language extension installed (e.g. [Ionide](https://ionide.io/)), VS Code otherwise treats `.fs` files as plain text. The CLI recognizes the full VS Code C++ suffix set, including compound template suffixes such as `.hpp.in`; see [Command-Line Usage](docs/cli.md#supported-file-suffixes).
 
 ## Development
 
@@ -91,4 +91,5 @@ To exclude files/folders (e.g. test fixtures, generated code) from both the exte
 ## Known Issues
 
 - TypeScript arrow functions aren't analyzed by complexity/parameter-count/coherence (same limitation Python already has for `lambda`), only named `function` declarations and class methods are.
+- C++ analysis is syntax-only: it does not preprocess macros, resolve includes, instantiate templates, or perform type checking. C++ lambdas are not treated as standalone functions by function-level detectors.
 - Several detectors have per-language gaps beyond the above, see the "Known limitations" section of the relevant [detector doc](docs/detectors/README.md).