mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00

Files

kingwl 0a486f09c9 chore: adopt node-addon-landlock-run source as native/ subtree

Bring the node-addon-landlock-run tree (tag v0.0.1, commit 614f7fd) into
native/landlock-run as its source of record: launcher development happens
here, next to the harness consumers, and the standalone repository becomes
the release mirror the tree is exported to for packing and publishing
(procedure in native/README.md). The subtree keeps its own pnpm workspace
and lockfile and is NOT added to the harness workspace: harness installs,
gates, and CI never touch it. The mirror's .github/ stays out of the
subtree; a separate manually-dispatched workflow
(.github/workflows/landlock-run.yml) runs the subtree's CI legs — the
per-architecture native builds, real-kernel launcher proofs, and pack
rehearsal — adapted with working-directory/cache paths.

eslint ignores the subtree like vendor/; AGENTS.md gains the native/
layout line (+5 words on its budget ceiling).

2026-07-14 23:39:58 +08:00

839 B

Raw Blame History

node-addon-landlock-run-linux-x64

Prebuilt bin/landlock-run Landlock launcher for linux-x64 — a static musl binary compiled natively (no cross toolchain) from the C source shipped in node-addon-landlock-run. npm's os/cpu fields select this package at install time; the entry package resolves it to a file path — it ships no JavaScript and is never imported.

The binary is git-ignored and rides the npm tarball via the files list; the prepack gate refuses to pack when it is missing or has the wrong ELF architecture, and the release pipeline byte-pins the packed binary against the CI build it came from. Static musl linking means one binary for glibc and musl distros alike — hence no libc suffix in the name.

Sibling: node-addon-landlock-run-linux-arm64.

839 B Raw Blame History

node-addon-landlock-run-linux-x64

839 B

Raw Blame History