jschoubben
558a93c25b
A manifest marking a tool its tools do not list, a verb its claims do not serve or an event it does not carry, one name both a tool and an event, a marked tool or verb (or a held seat verb its seat marks) without operator-channel in uses, or a marked tool or verb while every bundle it builds is run by its own process, is refused by both paths, naming the entry and the rule. The login shell's captured manifest is copied at AM-K1, which gives it operator-channel. Builds: design 46 7-approval-mark §4, §7, §21; design 34 every-event §32; lead answers A-177, A-183 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
32 lines
2.2 KiB
Plaintext
32 lines
2.2 KiB
Plaintext
What a test reads of another repository when no merge check has cloned it beside this one (internal/beside,
|
|
novox/hq issue 432). Copied from the repositories at the commits below, never written by hand. Each
|
|
module.json is kept as module.json.captured: a module.json in this repository is a module of it to the
|
|
forge and the planner, and a merge would build and register it.
|
|
|
|
The copy carries the catalogue's private details: domains, first names in module names, a node name and
|
|
private addresses. That is acceptable while mesh-sdk is private; if it ever goes public, this copy is
|
|
a second place to clean besides the catalogue itself.
|
|
|
|
Only what go/catalogue's tests read is captured (R4b, issue 1379), copied here from mesh-sdk with the judge's tests
|
|
(issue 1585). mesh-host refreshed 2026-11-01 from its main, the catalogue 2026-10-21 from its main; before that it
|
|
was mesh-controller's copy, which still held two modules that had left the catalogue.
|
|
|
|
mesh-catalog b5dbfbb784507e211372a7c9640d91f7d6dadd84 modules/*/module.json, modules/*/files/**, modules/*/templates/**, predefined.json
|
|
mesh-host 233bb23bbcb1a829ce2a6164a31a5c5cc4f3d950 internal/apply/placement_guard.go
|
|
mesh-catalog 2d5358b8 (milestone 47/G's AM-K1) modules/zsh/module.json alone: the login shell uses operator-channel for
|
|
its seat's marked execute (design 46 approval mark §21), which the validator requires (§4)
|
|
|
|
To move them, from mesh-delivery's modules/mesh-delivery-indexer directory, with the two repositories checked out
|
|
beside mesh-delivery:
|
|
|
|
rm -rf testdata/beside/mesh-catalog testdata/beside/mesh-host
|
|
mkdir -p testdata/beside/mesh-catalog testdata/beside/mesh-host/internal/apply
|
|
git -C ../../../mesh-catalog archive <commit> -- predefined.json ':(glob)modules/*/module.json' \
|
|
':(glob)modules/*/files/**' ':(glob)modules/*/templates/**' | tar -x -C testdata/beside/mesh-catalog
|
|
find testdata/beside -name module.json -exec mv {} {}.captured \;
|
|
git -C ../../../mesh-host show <commit>:internal/apply/placement_guard.go \
|
|
> testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
|
|
|
|
and write the commits here. The placement guard is kept as .captured so no Go tool reads it as this
|
|
repository's code.
|