@deliciousmonster/datadog-agent-binary 7.82.1-next.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 HarperDB, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,138 @@
+# @deliciousmonster/datadog-agent-binary
+
+[![Datadog Agent Binaries](https://github.com/deliciousmonster/datadog-agent-binary/actions/workflows/build-release.yml/badge.svg)](https://github.com/deliciousmonster/datadog-agent-binary/actions/workflows/build-release.yml)
+
+A Harper v5 plugin that runs the Datadog core agent and trace-agent alongside a node, so host metrics and the spans the host application's own `dd-trace` produces reach Datadog. `dd-trace` itself is the application's, not shipped here. Both agents arrive as pre-compiled binaries, one npm package per platform, picked by `optionalDependencies`; nothing is downloaded at install time and no install script runs.
+
+The binaries are how the plugin does its job, not a product of their own. Running them outside a Harper node is not a surface this package supports.
+
+## Install
+
+```bash
+npm install @deliciousmonster/datadog-agent-binary
+```
+
+npm fetches only the platform package whose `os`/`cpu` match the host, so one agent pair arrives with the install. Two things in the node's own config then decide whether either agent starts.
+
+### Name it in the root config
+
+Harper hands a component a `Scope`, and so calls this plugin at all, only for one the node's root `harper-config.yaml` names. A directory it found by scanning `componentsRoot` loads, serves its resources and supervises nothing. The file is the one `settings_path` names in `~/.harperdb/hdb_boot_properties.file`, and the key is the component directory's own name, because a root entry resolves to `<componentsRoot>/<key>`:
+
+```yaml
+datadog-agent-binary: { package: "@deliciousmonster/datadog-agent-binary" }
+```
+
+Sixty seconds after the module loads with no plugin call, the component logs the entry it needs and the reason nothing started.
+
+### Allowlist both binaries
+
+Harper only lets a component spawn an executable listed by its exact absolute path in `applications.allowedSpawnCommands`. The other half of that gate, a `name` option on every spawn, the plugin passes itself. Two binaries launch here, not one:
+
+```sh
+ls -d "$PWD"/node_modules/@deliciousmonster/datadog-agent-binary-*/bin/*
+```
+
+```yaml
+applications:
+  allowedSpawnCommands:
+    - node
+    - /app/node_modules/@deliciousmonster/datadog-agent-binary-linux-x86_64/bin/datadog-agent
+    - /app/node_modules/@deliciousmonster/datadog-agent-binary-linux-x86_64/bin/trace-agent
+```
+
+A bare command name matches neither one. The paths carry no version, so an upgrade leaves them where they are; on Windows both end `.exe`. Keep `node` in the list too: where Harper does not supervise natively, the bundled guard spawns its reaper as `process.execPath` and then as a bare `node`, and a reaper that cannot start leaves the agents running after the node stops.
+
+Harper installs with `--ignore-scripts`, which costs this package nothing. `applications.allowInstallScripts` can stay off.
+
+## Configure
+
+The plugin does not configure Datadog. What follows is read from the environment, and `datadog.yaml` is rendered fresh on every worker start, so editing that file changes nothing.
+
+| Variable | Effect |
+| --- | --- |
+| `DD_API_KEY` | Measured on 7.82.1: without it the core agent starts and collects while the intake refuses every payload with a 403, and the trace-agent exits at once with "you must specify an API Key", binding no receiver. |
+| `DD_SITE` | Destination site, e.g. `datadoghq.eu`. Datadog's own default is `datadoghq.com`. |
+| `DD_ENV` | The `env` tag on everything sent. |
+| `DD_APM_RECEIVER_PORT` | Where `dd-trace` posts spans. Default 8126. |
+| `DD_EXPVAR_PORT` | The core agent's expvar. Default 5000. |
+| `DD_APM_DEBUG_PORT` | The trace-agent's own expvar. Default 5012. |
+
+`DD_API_KEY` and `DD_SITE` are never written to disk; both agents read them from the inherited environment. Those two and `DD_ENV` are also part of the fingerprint each agent's PID lock carries, so changing one makes the next worker start take the lock and SIGTERM the agent still running under the old value.
+
+Setting a port to `0` turns that endpoint off, and each one is load-bearing. Without the receiver `dd-trace` drops every span; without either expvar nothing can show that the process holding the port is the one this node started, and startup verification refuses rather than reporting healthy.
+
+## Diagnose
+
+Everything the plugin writes lands under `<rootPath>/datadog/<component directory>/`, with `rootPath` read from the node's own config chain, or from `ROOTPATH` where that is absolute. When no root resolves it falls back to `~/.harper-datadog/<component directory>/`. Under either root:
+
+| Path | What it holds |
+| --- | --- |
+| `datadog.yaml` | The config both agents read. |
+| `conf.d/` | The core checks this platform gets. Without them the core agent runs, reports healthy and collects no host metrics. |
+| `logs/agent.log`, `logs/trace-agent.log` | The agents' own logs. `log_to_console` is off, so none of this reaches the container's stdout. |
+| `logs/reaper.log` | The guard's reaper, where Harper is not supervising natively. |
+| `pids/` | One lock per agent, which is what holds a node to one agent pair rather than one trace-agent per worker thread. Clear it when a killed node leaves a stale lock behind. |
+
+The directory is named for the component, not just `datadog`: two installed copies sharing one `pids/` would share one lock.
+
+`GET /DatadogStatus/` is the plugin's one resource and takes Harper's own auth. It re-reads process state and the trace-agent's delivery counters on each request rather than replaying what boot found. Read in this order:
+
+- `supervision` is `harper` when the node's `Scope` carries the process sidecar API, `guard` when the bundled guard is holding the agents up instead.
+- `apiKey` is `set` or `MISSING`, never the value.
+- `processes[].verified` is a verdict on identity, not on liveness. The trace-agent's is taken by reading its expvar off the debug port and comparing the pid published there against the pid this node spawned, so something else holding the receiver port fails it rather than passing as healthy. `verifyDetail` names the case.
+- `delivery.verdict` is how far a span got. `delivering` and `rejected` are evidence either way; `traces-unconfirmed` means the stats hop landed and the trace hop is unproven. Every counter behind it is a one-minute window the agent resets, so read it twice before believing it.
+
+The agents answer directly too, which is the check that does not depend on the plugin:
+
+```sh
+curl -s  http://127.0.0.1:8126/info        # the APM receiver, at DD_APM_RECEIVER_PORT
+curl -s  http://127.0.0.1:5000/debug/vars  # the core agent's expvar, at DD_EXPVAR_PORT
+curl -sk https://127.0.0.1:5012/debug/vars # the trace-agent's expvar, at DD_APM_DEBUG_PORT
+```
+
+The last takes `-k` because the trace-agent serves its debug port under the self-signed IPC certificate it writes into `run/`.
+
+## Supported platforms
+
+| OS | Architecture | Status |
+| --- | --- | --- |
+| Linux | x86_64 | yes |
+| Linux | arm64 | yes |
+| Windows | x86_64 | yes |
+| Windows | arm64 | no |
+| macOS | x86_64 | no |
+| macOS | arm64 | yes |
+
+Windows arm64 waits on [Chocolatey](https://chocolatey.org) supporting arm64 natively. macOS x86_64 is out because GitHub retired the Intel runner, and a target with no leg in the release matrix publishes an optional dependency npm skips in silence.
+
+## Building from source (maintainers)
+
+This is how the published binaries are made; consumers do not need it. The build CLI is not in the published tarball, so it runs from a checkout, and it shells out to `dda`, `go` and `pip`, which belong in a developer shell or a CI runner rather than inside a Harper-managed process.
+
+```bash
+npm run build-agent               # current platform, at the version .datadog-agent-version pins
+node dist/src/cli.js platforms    # supported platforms
+node dist/src/cli.js version      # latest upstream version
+
+# a version other than the pin
+npm run build && node dist/src/cli.js build --datadog-version 7.50.0
+```
+
+Requires Go 1.23, Python 3.12, CMake, Git, a C toolchain, and the Node in `engines` (22.18+ or 24+).
+
+Output goes to `build/<platform>/` under the directory you run from: `src/` is the clone, `go/` the GOPATH it is symlinked into, `bin/` the built binaries. No flag moves it, because `scripts/create-platform-packages.js` reads the binaries back out of that path.
+
+Publishing is gated on the packed tarball rather than the working tree: both binaries present in every platform package, each carrying its required symbol and free of the Go build tag `--build-exclude` is there to drop.
+
+```bash
+npm test                 # component and e2e tiers
+npm run typecheck
+npm run test:binaries    # needs real binaries from a prior build-agent
+npm run test:live        # boots a real node; released Harper is pinned at 5.2.9, and the
+                         # native-supervision row needs DD_LIVE_HARPER_NATIVE set to a
+                         # Harper worktree whose Scope carries scope.processes
+```
+
+## License
+
+Apache License 2.0. The agent binaries built and distributed here are Apache 2.0 as specified in the [Datadog Agent repository](https://github.com/DataDog/datadog-agent), and the datadog-agent source is copyright Datadog, Inc.

package/conf.d/cpu.d/conf.yaml.default

@@ -0,0 +1,11 @@
+# system.cpu.* - user, system, idle, iowait, steal, guest, and num_cores.
+#
+# Upstream ships this as cpu.d/conf.yaml.default with every option commented out, so the
+# effective instance is the empty one below. cmd/agent/dist/conf.d/cpu.d/conf.yaml.default in
+# the Datadog source is the full option list; report_total_percpu is the only one, and it turns
+# one series into one per core.
+
+init_config:
+
+instances:
+  - {}

package/conf.d/disk.d/conf.yaml.default

@@ -0,0 +1,15 @@
+# system.disk.* and system.fs.inodes.*, one set of series per partition.
+#
+# use_mount tags by mount point instead of device; false is what upstream ships and what the
+# Datadog integration tile expects.
+#
+# The defaults enumerate every partition the platform reports, pseudo-filesystems included, so
+# in a container this covers the overlay and the tmpfs mounts as well as the data volume. That
+# is upstream's behaviour and the series are cheap, but if the tag cardinality matters, the
+# knobs are include_all_devices, mount_point_exclude, and file_system_exclude. The full option
+# list is cmd/agent/dist/conf.d/disk.d/conf.yaml.default in the Datadog source.
+
+init_config:
+
+instances:
+  - use_mount: false

package/conf.d/file_handle.d/conf.yaml.default

@@ -0,0 +1,11 @@
+# system.fs.file_handles.used and .max.
+#
+# Shipped on macOS as well, unlike upstream's package, which deletes file_handle.d there. The
+# check has a darwin implementation (file_handles_bsd.go, built for freebsd || darwin) and it
+# runs: only the packaging omits it. Running out of descriptors is a real way for a database
+# node to fail, and it fails the same way on a developer's Mac.
+
+init_config:
+
+instances:
+  - {}

package/conf.d/io.d/conf.yaml.default

@@ -0,0 +1,12 @@
+# system.io.* - per-device read/write rates, await, and utilization.
+#
+# Every value is a rate, so the first run of a fresh agent emits nothing: the check needs two
+# samples. That silence is normal and lasts one interval.
+#
+# device_exclude_re is worth setting on a host with many LVM logical volumes or transient
+# loopback devices. Left unset, as upstream leaves it.
+
+init_config:
+
+instances:
+  - {}

package/conf.d/load.d/conf.yaml.default

@@ -0,0 +1,6 @@
+# system.load.1/5/15 and the .norm variants, divided by core count.
+
+init_config:
+
+instances:
+  - {}

package/conf.d/load.d/platforms

@@ -0,0 +1,4 @@
+# Windows has no load average, and the check is a stub there
+# (pkg/collector/corechecks/system/cpu/load/stub.go). Upstream deletes load.d from the Windows
+# package for the same reason.
+linux darwin

package/conf.d/memory.d/conf.yaml.default

@@ -0,0 +1,10 @@
+# system.mem.* and system.swap.*.
+#
+# collect_memory_pressure adds the /proc/vmstat allocstall and pgscan counters on Linux. Left
+# off, as upstream leaves it: they are kernel-reclaim internals, and the pressure they describe
+# shows up in system.mem.usable first.
+
+init_config:
+
+instances:
+  - {}

package/conf.d/network.d/conf.yaml.default

@@ -0,0 +1,10 @@
+# system.net.* - per-interface bytes and packets, TCP/UDP counters.
+#
+# collect_connection_state shells out to enumerate sockets and is off by default upstream. It
+# is the expensive option in this file; leave it off unless the connection-state breakdown is
+# what you came for.
+
+init_config:
+
+instances:
+  - collect_connection_state: false

package/conf.d/network.d/platforms

@@ -0,0 +1,4 @@
+# There is no macOS network check to configure. The v1 check builds for linux || aix and the v2
+# check for linux || windows, so on darwin the catalog has no "network" entry at all and this
+# config would surface as a Loading Error in `datadog-agent status` rather than as metrics.
+linux win32

package/conf.d/uptime.d/conf.yaml.default

@@ -0,0 +1,6 @@
+# system.uptime. One gauge, no options.
+
+init_config:
+
+instances:
+  - {}

package/config.yaml

@@ -0,0 +1,11 @@
+# Replaces Harper's component defaults outright; there is no merge. `jsResource` makes resources.js the
+# entry the application loader compiles, and `pluginModule` is what hands that same module a Scope.
+
+rest: true
+
+jsResource:
+  files: resources.js
+
+# handleApplication(scope) is the only path that starts an agent, and Harper calls it only for a component
+# the node's root harper-config.yaml names. A directory found by scanning componentsRoot has its module discarded.
+pluginModule: resources.js

package/package.json

@@ -0,0 +1,81 @@
+{
+	"name": "@deliciousmonster/datadog-agent-binary",
+	"version": "7.82.1-next.0",
+	"description": "Harper component that runs the Datadog trace-agent and core-agent alongside a node, with pre-built binaries installed per platform",
+	"type": "module",
+	"scripts": {
+		"build": "tsc",
+		"dev": "tsc --watch",
+		"start": "node dist/src/cli.js",
+		"typecheck": "tsc --noEmit",
+		"clean": "rm -rf dist/ build/ npm/",
+		"build-agent": "npm run build && node dist/src/cli.js build",
+		"// all-platform-packages": "unlike platform-package, this assumes binaries were already built out-of-band (build-release.yml's publish job calls create-platform-packages.js directly, not through either npm script)",
+		"all-platform-packages": "npm run build && node scripts/create-platform-packages.js --all",
+		"platform-package": "npm run build-agent && node scripts/create-platform-packages.js",
+		"// update-optional-deps": "npm run build stays: run through npm version's `version` lifecycle in build-release.yml's publish job, this is the only thing that compiles dist/ there, and create-platform-packages.js and verify-package.js both read it in the two steps that follow",
+		"update-optional-deps": "npm run build && node scripts/update-optional-deps.js",
+		"// verify-package": "requires dist/ already built - in build-release.yml's publish job, the version-bump step's `version` lifecycle supplies it (see // update-optional-deps)",
+		"verify-package": "node scripts/verify-package.js",
+		"lint": "prettier --write .",
+		"lint:check": "prettier --check .",
+		"prepare": "husky",
+		"version": "npm run update-optional-deps",
+		"// test": "--test-timeout, because node --test defaults to 0 and a supervision change that hangs then reads as a stuck machine rather than a failure; the slowest test in this tier is 1.4s, so 120s only ever fires on a hang",
+		"test": "npm run build && node --test --test-timeout=120000 \"test/component/**/*.test.js\" \"test/e2e/**/*.test.js\"",
+		"// test:windows": "the Windows leg's stand-in for `test`: same two directories, minus the suites scripts/windows-gate.mjs lists as unrunnable there, and it fails rather than exits 0 on a run that executed nothing",
+		"test:windows": "npm run build && node scripts/windows-gate.mjs",
+		"test:live": "npm run build && node --test \"test/live/**/*.test.js\"",
+		"// test:binaries": "requires real binaries already built at build/<platform>/bin, from a prior `npm run build-agent` or a CI step that already built them; this script itself only runs `npm run build` (tsc), same as test:live for the same real-binaries dependency; excluded from `test` for that reason",
+		"test:binaries": "npm run build && node --test \"test/binaries/**/*.test.js\""
+	},
+	"keywords": [
+		"datadog",
+		"agent",
+		"build",
+		"cross-platform"
+	],
+	"author": "",
+	"license": "Apache-2.0",
+	"dependencies": {
+		"@deliciousmonster/harper-process-guard": "0.1.0-next.1"
+	},
+	"devDependencies": {
+		"@types/node": "^26.0.0",
+		"commander": "^15.0.0",
+		"dd-trace": "^6.13.0",
+		"husky": "^9.1.7",
+		"lint-staged": "^17.4.1",
+		"prettier": "^3.9.6",
+		"typescript": "^7.0.2"
+	},
+	"files": [
+		"conf.d/",
+		"config.yaml",
+		"resources.js",
+		"runtime/",
+		"README.md"
+	],
+	"engines": {
+		"node": "^22.18.0 || >=24.0.0"
+	},
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/deliciousmonster/datadog-agent-binary.git"
+	},
+	"bugs": {
+		"url": "https://github.com/deliciousmonster/datadog-agent-binary/issues"
+	},
+	"homepage": "https://github.com/deliciousmonster/datadog-agent-binary#readme",
+	"optionalDependencies": {
+		"@deliciousmonster/datadog-agent-binary-linux-x86_64": "7.82.1-next.0",
+		"@deliciousmonster/datadog-agent-binary-linux-arm64": "7.82.1-next.0",
+		"@deliciousmonster/datadog-agent-binary-macos-arm64": "7.82.1-next.0",
+		"@deliciousmonster/datadog-agent-binary-windows-x86_64": "7.82.1-next.0"
+	},
+	"lint-staged": {
+		"*.{ts,js,json}": [
+			"prettier --check"
+		]
+	}
+}