kingwl
0a486f09c9
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).
12 lines
264 B
JSON
12 lines
264 B
JSON
{
|
|
"AGENTS.md": 1375,
|
|
"docs/AGENTS.md": 1100,
|
|
"docs/architecture.md": 1790,
|
|
"docs/cordis-primer.md": 550,
|
|
"docs/defensive-patterns.md": 550,
|
|
"docs/testing.md": 800,
|
|
"examples/AGENTS.md": 200,
|
|
"packages/AGENTS.md": 290,
|
|
"packages/README.md": 710
|
|
}
|