Commit Graph
3969 Commits
Author SHA1 Message Date
mesh-tools 461868b9fe Merge pull request 'Design 47 H1: a trunk build places every mesh package it names; the bus module's whole test waits for a fill pass (H-A-267)' (#728) from fix/47-H1-catalog-trunk-packages-and-nats-test into main 2026-11-21 14:49:34 +00:00
jschoubben 4fb3ab6df5 mesh-build-node: say a placed release outside the package file's range (H-A-276)
The latest release is placed whatever the range a package.json names
(ADR 0573 §2); one outside that range is now said in the journal, for
the SDK and every other mesh package, so a module built against a
release its range excludes is visible. A range of a form not read is
said as such.

Builds: design 47 H H-A-267, H-A-276
2026-11-21 15:47:46 +01:00
jschoubben a5976cf299 mesh-build-node: hold the member's-build precedence over the registry in a test (H-A-267)
A fetch naming a member's build of a mesh package the registry lacks
lays the build and waits on nothing; without the skip in
placeMeshPackages it waits for the registry's release.

Builds: design 47 H H-A-267
2026-11-21 15:45:10 +01:00
jschoubben 820840076f nats: the whole test waits for the first fill pass, not a first view's answer (H-A-268)
The keeper never marks a first view listing no module as answered
(A-367), so the subtest waited for what cannot come and hid every later
subtest. It waits for the first fill pass and takes it as the first.

Builds: design 47 H H-A-268
2026-11-21 15:37:46 +01:00
jschoubben 83802dc4a6 mesh-build-node: place every mesh package a module names at its latest release (H-A-267)
A trunk build put only the SDK into a module's node_modules; any other
@novox/mesh-* package its package.json names was left out of the install
and only a group or a member's build brought it, so the forge module's
build failed with "Cannot find module" for its contracts package. Each
such package is now placed at the latest release the registry holds, as
the SDK is; a group's packed package or a member's build still takes
precedence.

Builds: design 47 H H-A-267
2026-11-21 15:35:26 +01:00
mesh-tools efc8c52e68 Merge pull request 'Design 47 H1: the artifact sweep runs one pending pass from a followed view of the builds (H-A-250)' (#727) from fix/47-H1-artifact-sweep-one-pass into main 2026-11-21 11:08:08 +00:00
jschoubben 72872b045a Design 47 H1: a build's end comes from the builder's log; an unread end or view holds the pass loudly (H-A-258, H-A-260)
A done build whose history read failed was left out of the view for the whole process, so later passes judged from an
incomplete keep set, and every build cost one history read. A build's end is now taken from the build-ended entries of
the builder's log the pass already reads once, and only a build the log lacks is read from its history. While any done
key's end is unread, or the view is not yet taken in, no pass judges: it ends with the finding artifact-builds-unread,
written once and cleared by the next pass that judges. Every change heard while a watch's handover is gathered now goes
into that handover, so a build finished between the handover and its taking in is not lost by the swap (H-A-257).

Builds: design 47 H §H-A-255 (1), §H-A-257, §H-A-258, §H-A-260
2026-11-21 12:06:18 +01:00
jschoubben 603d4c7557 Design 47 H1: a watch of the builds asked again replaces the followed view whole (H-A-257)
A watch asked again after an error handed over the current values on top of the old view, so a key deleted while no
watch ran stayed in the keep set. Each handover is now gathered apart and replaces the view whole once it is in, and
the ends of keys it no longer holds are forgotten.

Builds: design 47 H §H-A-255 (1), §H-A-257
2026-11-21 12:01:58 +01:00
jschoubben 8d1c0d7d1d Design 47 H1: the artifact sweep judges from a followed view of the builds, not pages (H-A-255)
A page read costs the whole bucket per page, so the builder's builds are now a followed view: the watch's first view
at start, then its updates, kept in memory with each build's end read once from its history. A pass reads nothing of
the builds on the bus and judges nothing before the first view is in, so it never sweeps against an empty keep set.

Builds: design 47 H §H-A-250 (2), §H-A-255 (1)
2026-11-21 11:59:56 +01:00
jschoubben c01a816385 Design 47 H1: the artifact sweep runs one pending pass from one paged read, and stops on an unread list (H-A-250)
A finished build or a want change started a sweep and an observation each, every one reading the builder's builds key
by key and asking the registry's list again, queued behind one lock: a third of the night's bus flood. Now an event
marks the one pending pass, a pass running when marked runs once more, the builds are read in pages of the state with
each build's end from the page, and a list the registry seats cannot answer ends the pass with artifact-list-unread,
written once and cleared by a pass that reads it.

Builds: design 47 H §H-A-250 (1), (2), (3)
2026-11-21 11:54:46 +01:00
mesh-tools eb443cfc24 Merge pull request 'Design 47 H1: the bus module's warrant asks at approve level until a channel carries destroy; the router names the hold (H-A-237)' (#726) from fix/47-H1-nats-warrant-approve into main 2026-11-21 10:28:07 +00:00
jschoubben 7c6cf18532 Design 47 H1: a held destroy-level ask says its level; an offer with no channel named says so
The router held the bus module's destroy-level asks with the bare words
"no channel can carry it now", so the asker could not tell why. holdWhy
now names the destroy level and that no channel carries a destroy answer
yet. The bus module's tool says "offered, channel not yet named" for an
open record with no tickets, never "offered on :".

Builds: design 47 H H-A-237 (3), H-A-239 (2)
2026-11-21 11:26:19 +01:00
jschoubben a8f2316d08 Design 47 H1: the keeper's warrant asks at approve level; the tool says the router's standing
The bus module's drop and rebuild asks were at the destroy level, which no
channel carries yet, so the router held every one unshown until it expired
while the tool answered "the operator is asked". The ask is now at the
approve level for the caller's expires_minutes (5 to 1430, default 60,
refused outside), the keeper accepts an approve-level choice for these two
acts and bounds a request by its ask's own expiry, and the tool makes one
read of the router's record after the publish and says offered, held or
refused as it finds it; the request read shows that standing too.

Builds: design 47 H H-A-237 (1) (2), H-A-239 (1) (2)
2026-11-21 11:17:58 +01:00
mesh-tools af004a8ef6 Merge pull request 'Design 47 H1, proof 1 (second run): one line in feh' (#725) from proof/47-H1-feh-2 into main 2026-11-21 10:08:05 +00:00
jschoubben e1974b770e Design 47 H1, proof 1 (second run): one line in feh
Design lines: H §5 step 7. The first run's pipeline failed on the validate ask before the assigner fix.
2026-11-21 11:07:41 +01:00
mesh-tools c9beea9a38 Merge pull request 'Design 47 H1: the forge answers not-found for a missing directory in a trees listing (H-A-232)' (#724) from fix/47-H1-gitea-trees-not-found into main 2026-11-21 02:09:21 +00:00
jschoubben 74488f3e66 Design 47 H1: the seat git answers a listing's missing directory not-found (H-A-232)
A directory of a trees listing's files the commit does not hold was
thrown as a plain error and answered with the kind failed, so the
indexer took it for a forge that failed, never ran its one-directory
fallback (issue 1585), and published nothing of the repository.
commitTrees throws DirectoryNotInTree for it, and the seat's failure
answers it with the kind not-found, the error naming the directory.

Builds: design 47 H H-A-232 (2), H-A-234; issue 1585
2026-11-21 02:59:05 +01:00
mesh-tools 49cc5b3d7d Merge pull request 'Design 47 H1: the bus module counts every manifest's old-section entries as asked for (H-A-229)' (#723) from fix/47-H1-nats-old-sections into main 2026-11-21 01:33:10 +00:00
jschoubben 08ec25e367 Design 47 H1: a kept old-section entry keeps only the objects the keeper made; a kept state stays in the cap sum
Review round 1. keepOld took the old plan's objects whole, so a state's `<state>-objects` store
the grants part made beside a bucket the keeper made alone would have been compared, grown and,
on a recreate, deleted by the keeper: it now keeps only the old plan's objects the made record
already holds. CapSum skipped every kept entry as counted in the old sections' caps, which count
objects, logs and streams but never a state: it now skips only a kept objects, log or stream
entry, so a kept state's bucket stays in the sum.

At the delivery the plan digest changes once for every module with old sections (most modules,
since state counts): each plans again once, quietly, as its entries are compared with what the
bus holds and nothing is created or said where they agree.

Builds: design 47 H H-A-229, H-A-230, H-A-231; G §547
2026-11-21 02:32:01 +01:00
jschoubben ec305f08e6 Design 47 H1: the bus module counts every manifest's old-section entries as asked for (H-A-229)
The keeper read only a manifest's new-form asks, so the entries it had made for the artifact
registry and the forge, now declared in their old sections, stood as orphans with live data: a
rebuild refused, a drop offered. The keeper now reads every manifest's old sections (state,
objects, logs, streams) by the SDK's naming per section, as the grants part composes them. An
entry it made under one of those bus names is no orphan, is compared and grown to the declared
cap and rebuilt on request; it creates none of them and says no created for one, and counts a
kept one's cap once, in the old sections' sum.

Builds: design 47 H H-A-229, H-A-230, H-A-231
2026-11-21 02:26:20 +01:00
mesh-tools c050f23860 Merge pull request 'Design 47 H1, proof 1: one comment in feh, delivered by its pipeline' (#722) from proof/47-H1-feh into main 2026-11-21 00:43:52 +00:00
jschoubben ae9bb17e0f feh: name H1's proof 1 in the wallpaper file, the single-module change its pipeline delivers
A one-line comment in ~/.fehbg (the files archive) moves feh's fingerprint and
is readable on every machine that holds feh once it is delivered, with no hand act.

Design 47 H §5 runbook step 7: "Prove it. One single-module change (a comment in
a module with lint, unit and composition steps only), merged to main through a
merge call (merge-pull, design 47 H §734), followed from take-in.taken through
pipeline-ended to the node-engine's running and the gate's ended record, with no
hand act".
G §370: "The version reaches every artifact's build": the delivered files
archive carries the version the pipeline gave it.

Builds: design 47 H §5 step 7, G §370
2026-11-21 01:39:08 +01:00
mesh-tools be6eb0358f Merge pull request 'Design 47 H1: the Go build module takes a same-repository requirement from the tree at any version and reads the repository from the fetch (H-A-202, H-A-198, H-A-204)' (#721) from fix/47-H1-build-go-same-repo into main 2026-11-20 23:52:00 +00:00
jschoubben e1d2af8d6e mesh-build-go: build a same-repository requirement from the tree at any version (H item 6)
A requirement of the checked repository at a real version was fetched from the Go seat while the
indexer's fingerprint takes the tree, so the build and its key disagreed; and "same repository" was
read from the owner name novox/ written into the code. The fetch now takes every requirement of its
own repository from the fetched tree before anything is downloaded, at whatever version go.mod
names, keeps those directories in the narrowed tree, and judges "same repository" by the fetch's
repository as the ask names it.

Builds: design 47 H S31, S3, L8 (H-pins-spec-and-gaps section 8 item 6); H-A-204, H-A-202, H-A-198
2026-11-20 23:22:53 +01:00
mesh-tools 34a884ffcc Merge pull request 'Design 47 H1: disk-load declares its readings package, the gate accepts asks at 0.3, the Go build module refuses a build with no pin and keeps the same-repository tree (H-A-186, H-A-188, H-A-192, H-A-202)' (#720) from fix/47-H1-catalog-h1-owed into main go/v0.1.14 go/v0.1.15 go/v0.1.17 2026-11-20 21:39:11 +00:00
jschoubben b889075e21 H-A-202: the narrowed tree keeps the repository's packages a required package requires, transitively
A package artifact's go.mod may require a package of its repository that
requires another of it at the zero version; the narrowing kept only the
first level, so the build of the second found no module of that path. The
entry's paths keep the manifest's form; the Go build module reads each kept
package's go.mod in turn, each directory once, and keeps what it requires.

Builds: design 47 H H-A-202, H-A-198
2026-11-20 22:28:28 +01:00
jschoubben 3fd2e58072 H-A-192: the Go build module refuses a requirement with no pin of its own
Given no pin, the module took the version of another package of the same
repository, or the latest, and built against versions never published. A
requirement of another repository is now taken at the pin the ask names for
its own path, else the build fails naming the path; a same-repository
requirement is still built from the fetched tree.

Builds: design 47 H H-A-192, H-A-198, G §370
2026-11-20 22:20:12 +01:00
jschoubben dc507ec9ff H-A-186, H-A-188: declare diskreadings as a package artifact; the gate accepts asks at 0.3
disk-load's Go package diskreadings is imported by mesh-grants, whose build
waits for a publish no release made: an imported mesh package is a declared
artifact of its module, so every release publishes it. The gate imports the
assigner's asks, published in the assigner's series 0.3, so it names that
series in its packages.

Builds: design 47 H H-A-186, H-A-188, H-A-198, G §370
2026-11-20 22:13:25 +01:00
mesh-tools 3c402d766c Merge pull request 'Design 47 H1: proof 2, a two-module change along a dependency edge delivered by its pipeline (H §5 step 7)' (#719) from proof/47-H1-two-modules-2 into main 2026-11-20 17:55:45 +00:00
jschoubben 7de86ff471 Design 47 H1: proof 2, a two-module change along a dependency edge delivered by its pipeline (H §5 step 7) 2026-11-20 18:55:28 +01:00
mesh-tools e8924b9f5d Merge pull request 'Design 47 H1: proof 1, a single-module change delivered by its pipeline (H §5 step 7)' (#718) from proof/47-H1-single-module into main 2026-11-20 16:00:06 +00:00
jschoubben 2cd3f20cb2 Design 47 H1: proof 1, a single-module change delivered by its pipeline (H §5 step 7) 2026-11-20 16:59:41 +01:00
mesh-tools e01c21f19e Merge pull request 'distribution: versions on the artifact seat answers the blob a reference names (A-430a, design 51)' (#717) from fix/47-H1-engine-archive-digest into main 2026-11-20 15:21:37 +00:00
jschoubben b68de8f186 distribution: test versions' digest per seat; say why a version has none
Review round 1: versionsAnswer's choice of digest per seat had no test.
TestTheVerbsSpeakTheSeatsContract now holds it, with a store whose blob
and manifest digests differ. OCI.Blob refuses a manifest that keeps no
single blob, naming its layers, and versions says that in the journal:
the contract's answer has no field for why.

Notes for H2: OCI.Held (oci.go) compares the tag's manifest digest with
a bundle's or an archive's blob digest, the same kind as this fault;
versions answers kind "" since the tool reads a kind its input does not
take.

Builds: design 47 G A-430a (G-22-lead-answers-2), design 51 *One contract*
2026-11-20 16:20:00 +01:00
mesh-tools 05955b6349 Merge pull request 'mesh-build-node: narrow a step's workspace as H-A-136 and H-A-137 say; a narrowed-out package is no module of the step' (#716) from fix/47-H1-mesh-contracts-publish into main 2026-11-20 15:12:43 +00:00
jschoubben 6f4e85c656 distribution: versions on the artifact seat answers the blob a reference names
The node-engine resolves a want's version to an archive's digest through
oci-artifact-registry's verb versions and fetches /blobs/<digest> by it.
The holder answered the tag's manifest digest, so shanks asked
claude-code/files' manifest as a blob and got 404 (claude-code 0.1.17).
On the artifact seat versions now answers the manifest's one blob, the
digest the reference and the event published carry; the image seat
keeps the manifest digest.

Builds: design 47 G A-430a (G-22-lead-answers-2), design 51 *One contract* (the seats' events carry the digest), the seat's contract Artifact and Listed.artifact
2026-11-20 16:12:27 +01:00
jschoubben f4cd0e89fd mesh-build-node-narrowed-packages: narrow a step's workspace as H-A-136 and H-A-137 say
Review round 1. The node build module runs the seat generator's check at its unit level
(steprun.OutOfStep), so its narrowed workspace keeps what H-A-136 and H-A-137 name: every
generated-from directory of the module, and for a root module the seats/ directory and the
paths of every artifact naming generated-from. Narrowed bare, a step of one mesh-contracts
package named the generated files left out as out of step. The fetch and the steps verb now
narrow the same way, and the steps verb reads its narrowed tree as the levels do.

narrowTree and generatedFromDirs are copied from mesh-build-go without its Go part, not moved
into mesh-delivery-sdk's steprun: the move is a change to two more repositories and a group
delivery for some sixty lines, in a fix that unblocks the build steps now; the copy says so.
packageDir and narrowedAway share one path helper.

Builds: design 47 H H-A-136, H-A-137 (hq design/47-H1-answers-59), ADR 0499 clause 4
2026-11-20 16:10:08 +01:00
jschoubben 0b834bbca7 mesh-build-node-narrowed-packages: a package narrowed out of a step's workspace is no module of it
A step of one TypeScript package of a module with several (mesh-contracts' root:
ts-meshbroker beside ts-meshrecovery, pipeline main.3 of 2026-11-20) fetches a workspace
narrowed to that package's path. The fetch and the lint and test levels read every package
artifact of the manifest, and one whose path the narrowing left out fell back to the
module's directory, which holds no lock: every TypeScript step of mesh-contracts ended
"could not run: the package in . has no package-lock.json". Such a package is now left
out of the fetch's install and of the levels' targets; an unnarrowed tree is read as before.

Builds: design 47 H H-A-136 (a step's workspace holds the artifact's paths; nothing else is fetched), ADR 0499 clause 4
2026-11-20 16:01:19 +01:00
mesh-tools a0e86fc696 Merge pull request 'mesh-vault, claude-code: consume binding.changed.<consumer>, so binding moves are heard (H-A-142)' (#715) from fix/vault-hears-binding-changed into main 2026-11-20 14:18:18 +00:00
jschoubben 51a83ed3a8 mesh-vault, claude-code: consume binding.changed.<consumer>, so binding moves are heard
The licence manager says each binding change as binding.changed.<consumer>
(mesh.mod.claude-licence-manager.event.binding.changed.<consumer>), but both
manifests consumed claude-licence-manager.binding.changed, which the grants part
composes into the exact filter mesh.mod.claude-licence-manager.event.binding.changed:
the bus consumer never handed either module one change, and the vault kept only its
first view (2026-11-20: g14 refused a switched licence's token until the first view
was asked again by hand). The consumed pattern now names the further part, `*`.

Builds: design 47 G A-134; design 39 bus-and-switch §17, §19, §22
2026-11-20 15:09:45 +01:00
mesh-tools eb4e964fbf Merge pull request 'claude-code: a login not handed gives way to a newer lease of its own account (H-A-140)' (#714) from fix/licence-file-the-cli-accepts into main 2026-11-20 13:49:50 +00:00
jschoubben 121125aa50 claude-code: the latest login wins over a login not handed to the manager
A login not handed is kept only against a lease that does not succeed it; a lease
of the same account that succeeds it replaces it, said as login superseded. A login
to another account is kept until the manager adopts it.

Builds: ADR 0206, ADR 0209, design 39 §6, H-A-138 (hq design/47-H1-answers-59 175ed320), H-A-139 (hq design/47-H1-answers-59 e359911e), H-A-140 (hq design/47-H1-answers-59 b75d1386)
2026-11-20 14:47:49 +01:00
mesh-tools 947a68d274 Merge pull request 'claude-code: a login is succeeded by its own refresh, not only by a newer lineage (H-A-139)' (#713) from fix/licence-file-the-cli-accepts into main 2026-11-20 13:27:19 +00:00
jschoubben 0934292f47 claude-code: a login is succeeded by its own refresh, not only by a newer lineage
The manager's refresh keeps the licence's refresh-token expiry, so a grant of the
same lineage with a later access expiry replaces the login; a grant with no
mark, an older lineage or no later access expiry is the older lease and is kept.

Builds: ADR 0206, ADR 0209, design 39 §3 §6, design 14, H-A-138 (hq design/47-H1-answers-59 175ed320), H-A-139 (hq design/47-H1-answers-59 e359911e)
2026-11-20 14:25:47 +01:00
mesh-tools 1b706ca0b1 Merge pull request 'claude-code: the node side never writes a lease over a login the manager was not handed, and only a newer lineage over a handed one' (#712) from fix/licence-file-the-cli-accepts into main 2026-11-20 13:24:15 +00:00
jschoubben a8a0cfeb8f claude-code: a login handed is replaced only by a grant of a newer lineage
One reason, login kept, on both paths, with a journal line; the not-handed
return skips the binding's generation on purpose.

Builds: ADR 0206, ADR 0209, design 39 §3 §6, design 14, H-A-138 (hq design/47-H1-answers-59 175ed320)
2026-11-20 14:21:47 +01:00
jschoubben a7459c6e4f claude-code: never write a lease over a login the manager was not handed
A login made on a node (while the tool runner was stopped, or before the
manager asked claude_code_grant for it) was overwritten by the next apply
of the binding's older grant: Apply took any refresh token in the file as
one already handed, and forced the write. The person's login was lost and
the session asked for a login again.

The node side now keeps the fingerprint of the login claude_code_grant last
sealed (state login-handed, never the token). Apply leaves a file whose
login is not that one untouched (applied false, reason login-not-adopted);
its report makes it the manager's candidate, and the successor the manager
hands back replaces it, as before without a refresh token.

Builds: ADR 0206, ADR 0209; design 39 §6 (the latest login wins, a login
moves its node); design 14 (a node never holds a refresh token).
2026-11-20 14:02:37 +01:00
mesh-tools 677c149022 Merge pull request 'The claude-code module renders no shell guard; the wait-list hooks stay (the operator, 2026-11-20)' (#711) from fix/claude-code-no-shell-guard into main 2026-11-20 12:56:56 +00:00
mesh-tools 144bfd5626 Merge pull request 'The Go build module's step workspace holds the generated-from directories and the same-repository zero-version packages (design 47 H, H-A-136, H-A-137)' (#710) from fix/47-H1-zero-version-tree into main 2026-11-20 12:56:52 +00:00
jschoubben 1ae83499ba claude-code: drop the machines data only the guard read
With the guard gone nothing reads the machines' names, domains and
addresses: remove Machine, the name lookup and the ten-minute timer that
resolved them again, so the tools' table is read only when a followed
state changes. Also remove the now unused cut helper.
2026-11-20 13:15:52 +01:00