plccheck 2.6.2 → 2.8.0

package/README.md

@@ -13,7 +13,7 @@ npx plccheck check ./path/to/project
 - `plccheck serve` (LSP server over stdio)
 - `plccheck check <files-or-folders...>`
 - `plccheck emit --target <language> <file>`
-- `plccheck test [--filter <text>] [--events-json] [--coverage-json <file>] [--coverage-lcov <file>] [--coverage-branches] <file-or-folder>`
+- `plccheck test [--filter <text>] [--events-json] [--coverage-json <file>] [--coverage-lcov <file>] <file-or-folder>`
 - `plccheck version`
 
 ## Testing and Coverage
@@ -36,13 +36,13 @@ For zero-config discovery in the Coverage Gutters VS Code extension, write the L
 npx plccheck test ./my-plc-project --coverage-json coverage.json --coverage-lcov lcov.info
 ```
 
-Keep the default Stage 1 line-focused coverage view, but opt into additive Stage 2 branch data when needed:
+Note: `--events-json` prints a stream of execution events to stdout, while `--coverage-json` writes a finalized coverage report to a file. Coverage artifacts include statement, function, and branch data where runtime data is available. For AI analysis, use the file artifact from `--coverage-json`.
 
-```bash
-npx plccheck test ./my-plc-project --coverage-json coverage.json --coverage-branches
-```
+## Telemetry
+
+The npm wrapper marks CLI invocations so the Go binary can send minimal operational telemetry: subcommand, outcome, duration, safe option shape, aggregate `check` counts, and bounded diagnostic-code counts. It does not send file paths, PLC root names, source text, diagnostic messages, or raw command arguments.
 
-Note: `--events-json` prints a stream of execution events to stdout, while `--coverage-json` writes a finalized coverage report to a file. By default, the JSON artifact stays statement/line-focused and still includes function summaries/details where available, and LCOV includes the matching function records. `--coverage-branches` widens the JSON artifact with additive branch summaries/details and also adds LCOV branch records where branch runtime data is available. For AI analysis, use the file artifact from `--coverage-json`.
+CI invocations include a `ci` tag. Set `PLCCHECK_TELEMETRY=0` or `DO_NOT_TRACK=1` to disable this reporting. Set `PLCCHECK_TELEMETRY_ENDPOINT` to send logs to a different `/v1/logs` endpoint.
 
 ## Publishing (maintainers)
 

package/bin/plccheck.js

@@ -384,8 +384,14 @@ async function main(argv = process.argv.slice(2)) {
 
   args = reorderTestArgs(args);
 
+  const childEnv = {
+    ...process.env,
+    PLCCHECK_INVOCATION_SOURCE: process.env.PLCCHECK_INVOCATION_SOURCE || (binaryPath === 'go' ? 'npm_wrapper_dev' : 'npm_wrapper'),
+    PLCCHECK_CLI_VERSION: process.env.PLCCHECK_CLI_VERSION || readOptionalDepVersion(pkg) || '',
+  };
+
   return new Promise((resolve) => {
-    const child = spawn(executable, args, { stdio: 'inherit' });
+    const child = spawn(executable, args, { stdio: 'inherit', env: childEnv });
 
     child.on('error', (err) => {
       console.error(`plccheck: failed to start binary: ${binaryPath}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plccheck",
-  "version": "2.6.2",
+  "version": "2.8.0",
   "description": "Siemens PLC language checker + LSP CLI (SCL/ST/LAD/FBD, etc.)",
   "license": "CC-BY-NC-4.0",
   "bin": {
@@ -14,12 +14,12 @@
     "version": "node ../scripts/plccheck-npm-version-hook.mjs"
   },
   "optionalDependencies": {
-    "@danielv123/plccheck-win-x64": "2.6.2",
-    "@danielv123/plccheck-win-arm64": "2.6.2",
-    "@danielv123/plccheck-linux-x64": "2.6.2",
-    "@danielv123/plccheck-linux-arm64": "2.6.2",
-    "@danielv123/plccheck-darwin-x64": "2.6.2",
-    "@danielv123/plccheck-darwin-arm64": "2.6.2"
+    "@danielv123/plccheck-win-x64": "2.8.0",
+    "@danielv123/plccheck-win-arm64": "2.8.0",
+    "@danielv123/plccheck-linux-x64": "2.8.0",
+    "@danielv123/plccheck-linux-arm64": "2.8.0",
+    "@danielv123/plccheck-darwin-x64": "2.8.0",
+    "@danielv123/plccheck-darwin-arm64": "2.8.0"
   },
   "repository": {
     "type": "git",