Design 47 H: H-A-336, a TypeScript bundle's mesh packages are edges before its first build

This commit is contained in:
2026-11-21 22:02:57 +01:00
parent e320b964a9
commit fea6f12ebb
@@ -2027,3 +2027,11 @@ Where two preparers disagreed, the chosen one is named.
words are still derived from held modules' stub manifests pass by pass. H-A-306 (2) holds for every runtime process
the engine composes from module slices (the reads runtime's secret places included): a held module's slice is copied
from what runs. Fixed in the node-engine next, the same kind (fix-a-bug-met-twice). P3.
- **H-A-336 (a TypeScript bundle's mesh packages are edges before its first build, 22:02)** Met in the packet filter
group's review: the catalog graph gets a TypeScript bundle's package edges only after its first build (the Go side
reads imports with go list; the TypeScript side reads nothing at take-in), so a bundle newly importing a mesh
package (the holder importing the node-engine's and the packet filter's generated packages) is built before those
packages publish and refuses every verb. Owed, H2b, in the indexer and the Node build module: at take-in the
indexer reads a TypeScript module's package.json dependencies on @novox packages as edges of the catalog graph, as
it reads Go imports; until then the recovery of the moment is a rerun of the bundle's build step after the packages
publish. P-NATS-native, design-it-as-it-should-be (a gap built in the delivery system, not worked around).