Commit Graph
3344 Commits
Author SHA1 Message Date
jschoubben a3db292b8d Read each module's own manifest through mesh-sdk's catalogue reader (H-A-498)
The fifteen desktop modules' tools tests failed on every manifest with
"json: unknown field class": a test helper copied into each module decoded
module.json into its own struct, refusing unknown fields. Manifest
strictness is the catalog check's alone, and the manifest's form is a
contract read through mesh-sdk's catalogue package, so the copied
`manifest` struct and its reader go from the fifteen desktop modules and
pacman; each test reads module.json with catalogue.Decode and asserts only
the module's own promises (claims, files, tools) on catalogue.Manifest.

Builds: design 47 H2 H-A-498, H-A-498 addendum
2026-11-22 21:32:03 +01:00
mesh-tools bf972d1d34 Merge pull request 'mesh-build-go: a mesh Go package comes from the Go package registry alone, two download passes (design 47 H2 H-A-494)' (#743) from fix/goproxy-registry-only into main 2026-11-22 20:14:41 +00:00
jschoubben 837cd2570a mesh-build-go: take mesh packages from the Go package registry alone
The public proxy serves the forge's paths from git tags and direct reaches
the forge's git, so a version missing from the registry was found elsewhere
instead of failing loudly. The fetch now downloads in two passes over every
directory: first each pinned mesh package with GOPROXY=<seat>,off (a miss says
"the Go package registry holds no <pkg>@<v>"; no binding refuses "no Go
package registry bound"), and every zero-version requirement of the graph is
taken or refused then; second the rest of the build list with the public
proxy alone, no direct. Before either, a go.mod naming a mesh package at a
version other than the zero version is refused, so no forge path can reach
the public proxy; a pull request head is placed only for an ask's commit, and
the placement of go.mod-named pins goes. Every other go command (test, lint,
compile) runs with GOPROXY=off; GOPRIVATE and the account's ssh settings leave
goEnv, as repository fetches set their own.

Builds: design 47 H2 H-A-494, H-A-494 addendum (two downloads), H-A-494 second addendum (a forge path at a real version is refused), H-A-494 third addendum (a pull request head places only an ask's commit pin); design 51 Go packages (the recipe test refuses direct)
2026-11-22 21:10:09 +01:00
jschoubben 3ff4df5c6e mesh-cli: nox licence is the licences' overview; the controller's leftovers go
The operator typed `nox licence` and got the retired controller's refusal
instead of the licences. `nox licence` and `nox licence list` now call the
licence manager's licences and bindings and print one table of each, every
time local (1126/AC1); `nox licence usage [<licence>]` prints the usage
readings as a table (1126/AC2). `--json` prints the raw answer on every
rendered line, `nox nodes` included: one behaviour for one flag; for the
two calls one object {licences, bindings} (1126/AC3).

In the same change, the operator (2026-11-22 20:41): "why are there still
references to the controller?". Every retired controller line nox answered
with "this was the controller's" (its `instead` lines and the `unowned`
map) is deleted with its text: none has a seat verb of the same job; a
retired line now answers "is not a command" with exit 2, and nothing nox
prints names the controller (1126/AC4). The comments, help and README no
longer name the controller or issue 1126.

Builds: issue 1126 note 151, answers 1-5, and the note after it (acceptance
1126/AC1..AC4, the operator's 20:41 line); one-question-one-tool;
principle 4, a module is steered by its tools.
2026-11-22 20:50:22 +01:00
jschoubben 6476e3595a Node build module: install what a placed mesh package declares (H-A-491)
A mesh package's tarball is unpacked straight into node_modules, so its own
dependencies were never there: the forge module's bundle failed with esbuild
"Could not resolve blakejs" from the SDK's seal code. After every mesh package
is placed, the fetch installs the dependencies they declare (not their
devDependencies, not a mesh package, not one already present) through the
same npm path as the module's own, before the bundle.

Builds: design 47 H H-A-491 (addendum)
2026-11-22 20:03:48 +01:00
jschoubben 5326fb6142 Node build module: a test level's bounds follow the steps in hand (H-A-488)
The Node build module judged its levels by the same fixed bounds, and its
integration setup took 40 s against 30 s while three nodes' checks ran.
The rule is the kind's, not the Go module's: its bounds, and the
MESH_TEST_LEVEL_BOUND its scripts get, are now their defaults times the
steps the seat has in hand at the step's start (at least 1), and the
result names them (bound, setup_bound).

Builds: design 47 H2 H-A-488, H-A-488 addendum
2026-11-22 19:43:42 +01:00
jschoubben af8173651b Go build module: a test level's bounds follow the steps in hand (H-A-488)
On a loaded build node the integration level's setup took 34-37 s against
its 30 s bound three times today: the node-engine twice, the assigner once.
The bounds were judging the node's load, not the tests. A level's bounds,
and the MESH_TEST_LEVEL_BOUND its tests get, are now their defaults times
the steps the seat has in hand at the step's start (at least 1). The step's
result keeps naming the bounds it was judged by (bound, setup_bound).

Builds: design 47 H2 H-A-488
2026-11-22 19:41:33 +01:00
jschoubben fb71ff5439 A failed build step keeps the head of its error, not the tail alone (H-A-475)
The Node build module kept only the last half of its bound of a failed
command's stderr, so esbuild's error line was pushed out by its Node
launcher's stack trace ("esbuild for code: status 1" with no cause). The
image build module's reason and journal line kept stderr's tail alone too,
and so did the Node module's toolchain install. Each now keeps the head and
the tail within its bound, with "… <n> bytes left out …" between them. The
Go build module keeps a failure's first line, not its tail, and is left as
it is.

Builds: design 47 H2 H-A-475
2026-11-22 14:51:52 +01:00
jschoubben 7d07459c8e The artifact store judges a held version by the artifact's own digest (H-A-474)
Held compared the version tag's manifest digest with a bundle's or an
archive's blob digest, so every second publish of such a version was
refused even at the same bytes. It now compares like with like: a bundle's
or an archive's stored layer, an image's manifest. The same digest is
already held (ended, published said, nothing stored), on a repeated ask too;
another digest is refused naming the held one. The fake store keeps a
manifest digest beside the layer's, and a row runs the module's OCI code
over a store in memory.

Builds: design 47 H2 H-A-474, design 47 H H-A-393
2026-11-22 14:47:37 +01:00
mesh-tools 3b64060968 Merge pull request 'Healers manifest test expects the finding stream's 8 MiB (§783)' (#738) from fix/healers-test into main 2026-11-22 13:44:25 +00:00
mesh-tools fb2ff9e9db Merge pull request 'Orphaned durables: removable by the bus module, left out of the behind check, not composed again (H-A-472)' (#737) from fix/orphan-durables into main 2026-11-22 13:42:30 +00:00
jschoubben 3443760205 nats: nats_consumer_remove removes only a durable that is itself an orphan
Review round 1: a durable whose twin is current was removed without
reading the durable itself, so of the five live pairs where both twins
have pulls waiting either one would have gone. The tool now reads the
named durable too and refuses it while pulls wait on it, both read from
the bus at the call. "Current" is the setting twin-current-hours (24 by
default) of the manifest, read from the configuration at each call, the
field name the grants part's manifest names too.

Builds: design 47 H2 H-A-472 (1) and its third addendum (1), (2); review round 1 findings (1), (2)
2026-11-22 14:33:01 +01:00
jschoubben 7ae223d4ff gitea: merge-pull merges plainly only from a watched-branches view read since the last change
An unread or stale view held no entry for a watched repository, so every
member would have merged plainly with the note no delivery: a merge that
reports success and delivers nothing. The registrations holder now keeps
the time of its last read and of the last registration-changed heard; the
merge call refuses every member ("the watched branches are not read yet")
while the view is not read since that change, and a read that fails is
said and asked again with the module's growing wait until it answers.

Builds: design 47 H2 H-A-471 (second addendum); review finding H-A-471 addendum (2)
2026-11-22 14:14:09 +01:00
jschoubben 33bb6e8e41 Healers manifest test: the finding stream holds 8 MiB
H2 set finding-events to max-mib 8 on every module that binds it; the
healers' manifest test still expected 16 MiB and failed at main.

Builds: design 47 H2 §783, §812; H-A-411 (1), H-A-430 (3)
2026-11-22 14:09:05 +01:00
jschoubben 319f535002 gitea: merge-pull merges a repository with no watched branch plainly
The operator wants the merge call to work for a repository of no module,
such as hq. A member whose repository has no watched branch (no entry, or
an empty set, in the registrations' watched branches) is judged against
nothing of the module graph (no failed required step at a fingerprint),
merged in the order named, answered and kept merged with the note "no
delivery: the repository has no watched branch", and left out of
merge-called by that kept note, at the call and at the start's re-say, so
it starts no delivery. A group mixing it with watched members judges and
delivers those as before. A watched repository whose base is unwatched
stays refused. The holder answers at the seat git's form 3.

Builds: design 47 H2 H-A-471 and its addendum (1), (2)
2026-11-22 14:01:03 +01:00
jschoubben e0bd0bedc4 nats: nats_consumer_remove removes an orphaned durable whose twin is current
A module that moved into the tool runner left its program's durable
<node>_<module>, and one that runs its own program again left
<node>_<module>_tools: about 110 such orphans the tool refused by name.
It now removes a module's durable when its twin on the same stream has
pulls waiting and a delivery within the day, and names the twin in the
hand act; a module's only durable stays refused.

Builds: design 47 H2 H-A-472 (1), H-A-127, H-A-128, G A-340
2026-11-22 14:00:11 +01:00
jschoubben 1a54a432cf GT1 review round 2: the record's end clears its record-too-large from the findings state
The entries whose refusal a record's end must clear were kept in process
memory, so after a restart a refusal of an entry never written (an act's
first write, a mover's) was never cleared. A record-too-large finding now
names its record as its subject (its id stays the refused entry), and the
record's end clears every held one whose subject is the record, read from
the gate's own findings state; the in-memory map goes. A finding raised
before this change names its entry as its subject and clears when that
entry is next written within 64 KiB.

Review finding: record-too-large cleared at the record's end only from
process memory (movers.go:228-233, Records.refused).

Builds: design 47 H2 §809, H-A-455 (3), H-A-460
2026-11-22 03:10:24 +01:00
jschoubben 758a8ad653 GT1: each owed act is a ledger entry of its own; every ledger write is measured
An act the gate owes the forge is now the entry act/<branch.source.act.id>
(type act, index acts on its record's key in the manifest), removed when
the forge bridge performed it; the head entry holds the record's fields
alone, and the record's acts are joined from their entries when read.
The record type keeps no act operation: a head written before this change
is read for its fields and the acts embedded in it are ignored (they are
notes and views of the few records in flight at the delivery; losing them
changes nothing the operator relies on). A view act's text is the record's
summary, the head's fields and a count of movers per outcome, so it fits
64 KiB for any record; gate_record still shows the whole record. The
64 KiB refusal measures every write, the head's, a mover's and an act's,
raising record-too-large, which the record's end clears for every entry
of it. The gate's whole test gains the step: 126 movers write 127 entries
plus their acts, none over 64 KiB, the head counting 126 and holding no
act; a take-in said again with a why past 64 KiB raises record-too-large
and the record's end clears it.

Builds: design 47 H2 §809, H-A-385, H-A-391, H-A-453 (3), H-A-455, H-A-457, H-A-459
2026-11-22 02:58:39 +01:00
jschoubben 3dd92f1c4b C4 whole: the forge holds one token for the account after the bundle's own mint
The seat git's whole test configures no token: the bundle mints the tools'
account's token at the fixture forge with the admin's login, writes it
through the vault seat's two-step own-put (sealed to the call's key) and
reads it through get (sealed to the process's key), both answered by the
test, with the mint's lease watched as the runtime delivers it. After the
mint the forge holds exactly one token for the account, mesh-tools-1, the
one the vault keeps at generation 1; the old fixed-name token is gone.

Builds: design 47 H2 §808 (whole: the forge holds one token for the account after), H-A-422, H-A-430 (1), H-A-439, H-A-453 (3)
2026-11-22 02:49:12 +01:00
jschoubben 4150402020 SC1 whole: the self-check's whole test raises and clears over-budget from the gate's times
The review found §810's probe proven only at the unit level (H-A-453 (3)): the whole test now enables the budget
probe, answers gate_times with a core delivery 11 minutes from its merge call, reads over-budget for core naming its
record and longest phase, and a core delivery within its budget at the next run clears it.

Builds: design 47 H2 §810, H-A-453 (3)
2026-11-22 02:37:08 +01:00
jschoubben 2b06ab31d7 M1: the forge module declares tweetnacl, which its test bus imports
test/fakebus.ts imports tweetnacl to seal as the vault does; it came only through mesh-sdk's own dependency, so the
forge module's tests named nothing they import (the review's finding; H-A-453). Pinned as mesh-sdk pins it, an
external package as the rule allows.

Builds: design 47 H2 §808, §822; H-A-407, H-A-453
2026-11-22 02:36:15 +01:00
jschoubben 5dc8cb343b GT2 whole: the gate's whole test ends a record and reads its delivery time and class
The review found §810's whole criterion proven only at the unit level (H-A-453 (3)): the whole test now ends its
record through the wants seat's wanted and pipeline-wanted and the node-engine seat's running, over the real bus, and
reads the head's delivery-time and class core from a core mover's catalog entry.

Builds: design 47 H2 §810, H-A-453 (3)
2026-11-22 02:34:05 +01:00
jschoubben 98da0e0b68 M1 check-needs: a package outside every Go artifact's from takes the manifest's own check-needs
The forge module's internal/seatgit whole test needs the Node build seat, and no Go artifact's from holds it, so
nothing named its need and the Go build seat ran it on a node without the Node toolchain. The manifest now says the
need at its top level, read by the Go build module for such packages; gitea declares node-build-node
(review round 1, mesh-catalog, finding on §800; H-A-453 (2)).

Builds: design 47 H2 §800, H-A-453 (2)
2026-11-22 02:27:36 +01:00
jschoubben 30a3e665e0 GT: an owed act ended not-needed is ended, never said as a refusal
A pull request closed unmerged is a fact of the forge, not a fault of the
act, so the gate no longer keeps a refusal for an act the forge bridge
ends not-needed: the record's acts and gate_record show it ended with
that outcome, and delivery_status says no refusal of it. Every other
outcome other than performed is still said as a refusal.

Builds: design 47 H2 §807; H-A-432 (2), H-A-444
2026-11-22 02:06:45 +01:00
jschoubben 4500d98ca6 Merge feat/47-H2-c into feat/47-H2
The side branch's manifest rows, gate, forge, packet-filter and
package-manager changes join the build modules' share; no file was
touched by both.

Builds: design 47 H2 (the merged commits' own Builds: lines)
2026-11-22 01:56:19 +01:00
jschoubben 2785c69d95 GT: an act the forge bridge ends not-needed is ended in its record
The forge bridge ends an act whose pull request closed unmerged with the
outcome not-needed. The gate keeps it in the record's acts as ended, as it
keeps performed and could not be performed, and no longer counts it as
owed. The gate's code takes any outcome forgemsg reads, so the change is
forgemsg's outcome list at mesh-delivery feat/47-H2-a. The row in the
owed-acts test fails where forgemsg refuses not-needed.

Builds: design 47 H2 §807; H-A-432 (2)
2026-11-22 01:54:05 +01:00
jschoubben 280adcce68 C4: the vault keeps the forge token with the scopes it was minted with
The file beside the token that kept its scopes went with C4, and with it
the re-mint of a token carrying a scope beyond the tools' (write:admin).
The value written through own-put now holds the token and its scopes; a
token minted with other scopes, or a value naming none, is minted again
unasked and the one it replaces deleted at the forge. The Go bundles read
the token out of that value. The lost test is back as a row of the scope
test in test/token.test.ts.

Builds: design 47 H2 §808; H-A-439
2026-11-22 01:52:24 +01:00
jschoubben 22b92b827d BM publish version: the build modules' bundle asks name the ask's version, as the SDK now refuses one without
A bundle publishes under the version its ask reserved, and the delivery SDK's
publish refuses an empty one loudly; the tests' bundle asks carry a version, a
bundle asked with none is shown refused, and an archive still publishes by its
digest alone.

Builds: design 47 H2 H-A-373, H-A-373 addendum
2026-11-22 01:50:30 +01:00
jschoubben ed14a10006 GT: each act the gate owes names its delivery record
The gate's owed event carries record, the delivery record's source
revision <branch>.<source> (the record's key), said and kept in the
record's acts alike, so the forge bridge keeps it with the act and
bridge_owed_again finds a record's acts in its own state. Built against
the seat mesh-delivery's Owed.record on mesh-delivery feat/47-H2-a.

Builds: design 47 H2 §807; H-A-432 (1)
2026-11-22 01:48:18 +01:00
jschoubben 3ec18c9cd2 M1: nftables' setting allowances-max is marked runtime
The packet filter holder's tools read allowances-max themselves (config at
tools/index.ts); no file places it, so the manifest says "runtime": true
and the judge's placed-nowhere rule holds it as read by the module's code.

Builds: design 47 H2 H-A-430 (4)
2026-11-22 01:45:28 +01:00
jschoubben 872ed19648 M1: every module's findings stream holds 8 MiB, not only the delivery modules'
The eleven other modules that bind finding-events (claude-code, mesh-healers,
mesh-knowledge, mesh-provisioner, mesh-recovery, mesh-self-check,
mesh-watcher, minio, nfs-server, restic, zfs) set max-mib 8 for 7 days, as
the delivery modules' already do, so the indexer's finding-events rule (I6)
judges every manifest alike.

Builds: design 47 H2 §783; H-A-411 (1), H-A-430 (3)
2026-11-22 01:44:03 +01:00
jschoubben 39ed20c5bc C4: the forge module's tokens live in the vault, one process mints at a time
Two processes that minted at once left the forge two tokens by one name, and a token kept in a file in the
runtime state is a plain state. Both accounts' tokens (mesh-tools, mesh-packages) are now the module's own
secrets in the vault, written through the seat mesh-vault's own-put and read through its get, sealed to the
reading process's key. A refused or expired (token-ttl) token is minted again only by the holder of the lease
mint in the state token-lease (mint-lease); each mint is named <account>-<generation>, and the token it
replaces is deleted by id only after own-put landed. The Go bundles read their tokens through get at start
and at secret-changed; the MESH_GITEA_*_TOKEN_FILE words go. forge_token_lease reads the lease and each
token's age, never the token.

Builds: design 47 H2 §808, §822; H-A-407, H-A-422, H-A-426, H-A-430 (1)
2026-11-22 01:41:30 +01:00
jschoubben d3d9ff5183 M1: the build modules and the registry say their class and name every store's cap; detected-steps is pruned
Each of the four is core. Every state that named no cap names one, from its
live fill read 2026-11-22 01:4x CET (mesh-broker show, nats_streams on novox):
mesh-build-go steps 16.0 MiB (16,783,695 bytes) -> 128 MiB; mesh-build-node
steps 2.35 MiB (2,463,833 bytes) -> 16 MiB; every other state under 2 MiB ->
8 MiB (largest: distribution holds 1,844,287 bytes, mesh-build-go
detected-steps 868,554, distribution transfers 846,359, findings 668,161, idle
401,736, mesh-build-go pauses 254,366). The Go build module's finding-events is
8 MiB for 7 days. The objects stores already name their caps; none keeps a log.
The Go and Node build modules prune their state detected-steps (each key an
artifact's steps as detected, detected again when gone) at their own writes,
past prune-mark 70 % down to prune-target 50 %, and serve
<module>_state_prune_now and <module>_state_keep; no other state of the four is
prunable (each is truth: running steps, pauses, keys, toolchains, findings,
holds, transfers, windows, mirrors, taken asks).

Builds: design 47 H2 §812, §820; H-A-411 (1), (2), (3), H-A-437
2026-11-22 01:39:49 +01:00
jschoubben 1697b7041c BM4: each build module keeps a run's test output in its outputs objects
The Go build module's level answers its text in output (test2json's Output
lines), the Node build module's what its commands wrote; the delivery SDK's step
run keeps it as <node>.<ask> in the module's outputs objects, which each module
asks for in requires (1 GiB, kept 7 days) and reads through the verb output at
form 2. Each module's kit test runs the SDK's SeatVerbs.

Builds: design 47 H2 §791, §820; H-A-412 (1), H-A-412 second addendum (a), H-A-421, H-A-434
2026-11-22 01:32:40 +01:00
jschoubben 46990669de BM4: the bus module's keeper keeps an objects store's objects for its max-age-days
The objects template takes max-age-days (absent keeps an object for good): the
keeper plans it as the object store's max age, which the bus applies as the
store's TTL, so a build module's outputs objects go at their seven days.

Builds: design 47 H2 §820 (outputs: 7 days, the store's max-age), §791; H-A-434
2026-11-22 01:32:03 +01:00
jschoubben e335e859d5 BM3: the Node build module installs a module's npm tree and publishes it as <module>:node-modules
An install ask's body runs npm ci from the lock with no install script and no
link, packs the tree alone under modules/<module>/node_modules, publishes it to
the artifact store as the archive <module>:node-modules under the ask's version
and answers its reference, which the step's end carries. The package.json npm
ci needs is written from the lock's root entry, a lock without one refused. The
integration level's setup bound in code goes: half of the level's bound, which
each level's script gets as MESH_TEST_LEVEL_BOUND.

Builds: design 47 H2 §800; H-A-399 (2), H-A-403, H-A-427
2026-11-22 01:24:44 +01:00
jschoubben 1d8839640e BM4b: the build modules keep an oversized end in steps-objects, read by the verb answer
The delivery SDK replaced the output chunks with the verb answer over the
steps state's objects and output at form 2: each build module keeps an end
over the steps state's value with KeepAnswerIn, serves AnswerTool and
OutputTool over its steps state, and its steps name their outputs objects.

Builds: design 47 H2 §791, H-A-412 addendum, H-A-412 second addendum (b), H-A-399 (1)
2026-11-22 01:19:00 +01:00
jschoubben 9afbd35759 NP1: the NFS server and package manager modules' tests fold into one test per file, within 50 as the check counts
The check counts every test the integration level runs, untagged ones in: the NFS server
module held 51 and the package manager module 121, over the budget of 50. Each folded file's
tests run in order as rows of one test that keeps the first one's name and logs each case
before it runs; the root helper's test sockets are numbered per call, as one test now holds
several listeners, and the case that skips without pacman-conf runs last. Counts now 48 and 42.

Builds: design 47 H2 §819; H-A-349 DQ-14
2026-11-22 01:18:06 +01:00
jschoubben 7519191861 BM5: the steps read tools list an ask's steps under its asker, so they are never empty while asks run
Each build module's steps read tool listed only `<node>.<id>` keys and so
skipped every ask's step, kept as `<asker>.<node>.<id>`: it now reads every key
of its node, newest id first. The Go build module's test of capacity 0 also
holds the seat's current at form 2: no ask taken, why not capacity 0, then
paused.

Builds: design 47 H2 §801; H-A-399 (1)
2026-11-22 01:10:54 +01:00
jschoubben c63b4ae31d BM2: a test that cannot run says NOT RUN; the level's bound and the install archive reach the tests
The Go build module's level result carries not-run (the SDK reader's NOT RUN
skips), its tests get MESH_TEST_LEVEL_BOUND, the level's bound, from which
mesh-sdk's helpers take the setup bound; a test call naming an install archive
reads it from the artifact store by its reference and unpacks it into the
workspace's tree before go test. check-needs is read from the module's
manifest, on the Go artifact whose path holds the package, and the marker
file goes: the Node build module's manifest declares it on its bundle.

Builds: design 47 H2 §800; H-A-294, H-A-350 DMC-6, H-A-368, H-A-399 (1) (2) (3)
2026-11-22 01:07:45 +01:00
jschoubben a6132b32f6 C6: a source-only check's step-ended is heard on its escaped subject part
The manifest validator takes no # in consumes, and a key part escapes its
dots (mesh-sdk keys.EscapeName), so the forge module keeps hearing
step-ended.*.*.*: a source-only check's module source.<owner>.<name> is one
escaped subject part, and its body names it whole. The whole test says it so.

Builds: design 47 H2 §815; H-A-408
2026-11-22 01:07:28 +01:00
jschoubben bff5e98b30 C6: merge-pull refuses a source-only head whose check failed, naming the step
The runner's step-ended of a source-only check names the registration's key
source.<owner>.<name> as its module and the commit's root tree hash as its
fingerprint, so its subject holds more parts than a module's: the forge
module hears every subject under step-ended and judges it as a module's.
The seat's whole test refuses an hq pull request whose unit step failed.

Builds: design 47 H2 §815; H-A-408
2026-11-22 01:05:16 +01:00
jschoubben 74dd8af699 M1: the gate prunes its state heads toward its cap at its own writes
heads is written through the SDK's pruned state, which judges the fill each
put answers and past prune-mark (70 %) prunes the oldest keys to
prune-target (50 %); the gate serves mesh-delivery-gate_state_prune_now and
mesh-delivery-gate_state_keep, each written in the hand-act log.

Builds: design 47 H2 §812; H-A-380, H-A-386, H-A-411 (3)
2026-11-22 01:03:06 +01:00
jschoubben ac4ed46359 M1: every manifest says its class; the delivery modules' stores name their caps
A module that claims a seat is core, one that claims none a leaf (141
manifests; the build modules and the registry are the other developer's).
The forge module's, the gate's and the sweep's states each name 8 MiB, and
their findings stream 8 MiB for 7 days.

Builds: design 47 H2 §810, §812, §783, §820; H-A-394 (1), H-A-411 (1), (2), H-A-378
2026-11-22 01:01:26 +01:00
jschoubben ee5e7f232f P1: the packet filter holder reads a port's scope from its derived rule's comment
A derived accept rule's one comment says derived <modules> <protocol>/<port>
scope <any|private-network|local-network>, its module list cut with a count
past 128 bytes; allow without a source is refused for a port whose derived
rules name no scope any, read from the comments, never from a rule's shape.

Builds: design 47 H2 §813 (4); H-A-357, H-A-384 (1), H-A-349 DQ-11
2026-11-22 00:55:14 +01:00
jschoubben 6b17965d98 C5: forge_merged lists a repository's merged pull requests by number
From..to inclusive, each read from the forge one by one, with its merge
commit, when it was merged and the merge call that made it when a kept call
names it merged; at most 768 KB, capped with the next number as the cursor.

Builds: design 47 H2 §812, §811; H-A-402
2026-11-22 00:52:01 +01:00
jschoubben b93253e698 C2: the forge module takes an act of the seat git once by its ask id
Each act (status, comment, view, note, merge-pull, tag) carrying an ask id is
taken in the state taken, key git.<ask>, for the setting ask-taken-bound
(10m, read from MESH_CONFIG_ASK_TAKEN_BOUND): a repeat while the act runs
joins it; after it ended, the repeat answers what the forge holds of the act,
read afresh (a merge call's pull requests merged with their merge commits),
and the act is never done twice. An act that performed nothing drops its
key, so the kept call's repeat acts.

Builds: design 47 H2 §775, §820; H-A-381, H-A-400, H-A-359a
2026-11-22 00:51:01 +01:00
jschoubben 681de09f04 RG2: the registry's list pages by module and cursor; the sweep reads it page by page
oci-artifact-registry's list filters by name or module while it reads and
answers at most 768 KB a page with capped, total and the cursor next, in
order of the names; container-image-registry's answers whole as its form
says. The registry takes a removal for retention whoever asks it: the
refusal "not the sweep's" and its read of the sweep seat's holder go. The
sweep reads the list from its cursor until no page is left.

Builds: design 47 H2 §813 (7), §811, §779; H-A-350 DMC-10, H-A-399
2026-11-22 00:49:42 +01:00
jschoubben 54fe0dd7cc C1: the forge module says away when the forge or its store is away
A 401, 502, 503 or connection fault is judged by the forge's own
unauthenticated version read: the read failing, or naming the store
unavailable, answers the kind away with part and words, which every caller
reads as a transport fault; the read passing, a 401 (the fresh token refused
too) is the forge refusing the mesh's admin account, never worded as an
account to create.

Builds: design 47 H2 §776; H-A-350 DMC-2, H-A-354
2026-11-22 00:45:38 +01:00
jschoubben cb5de6fd31 MR1: the recovery module's whole test waits its start by the setup bound
The module's start is the test's setup: its two waits on the bus take
testbus.SetupBound (half of MESH_TEST_LEVEL_BOUND) and say a starved setup
in the one line testbus.Starved writes; its 30 s values go.

Builds: design 47 H2 §800; H-A-327, H-A-368
2026-11-22 00:43:38 +01:00