mikser-io 9.67.0 → 9.70.0

package/CLAUDE.md

@@ -200,6 +200,28 @@ brevity.
   of folder names written in the plugin. A hardcoded list misses every
   collection a project registers through `sources()`, which produced 63
   false warnings per build on a real site.
+- `src/plugins/render/asset.js` / `resource.js` — URL helpers that BUILD
+  a path from a naming convention instead of looking an entity up, so
+  they cannot fail: a preset that never ran yields a well-formed link to
+  nothing on a green build. Each records its destination via
+  `track.asset()`; `engine.js` checks the collected set against
+  `outputFolder` in `onFinalized` (`reportAssetUse` / `assetUse` in
+  report.js, `reportMissingAssets` in engine.js), warning under
+  `asset-missing` / `asset-missing-summary`. `existsSync` FOLLOWS
+  symlinks, which is required — the assets folder is deployed into the
+  output as a symlink. Handlebars appends an options object to every
+  helper call, so a trailing optional arg (`format`) must be discarded
+  when it looks like one (`'hash' in format`); without that, `asset 'web'
+  '/x.jpg'` built `/assets/web/x.[object Object]` — the bug the finalize
+  check found on its first run, present since the helper took a format.
+- Postprocess failures are RENDER ERRORS. The dispatcher's catch used to
+  log one uncoded `Postprocess error:` line and stop there — exit code 0,
+  nothing in `--json` `errors`, `🟢 Mikser completed`. A build missing
+  every PDF it was asked for reported success. It now calls `reportError`
+  with the failing `postprocessor`, so a stage that wrote no file counts
+  the same as a render that threw. `entity.origin` is deliberately NOT
+  unlinked on failure (it is on success): a retry needs it as input, and
+  for a converter it is real content.
 - `render.js` / `postprocess.js` — Piscina worker entry points AND the
   default-export functions the INLINE/SERIAL dispatcher calls directly.
   Each receives entity + options + config + state; the WORKER path also
@@ -246,7 +268,10 @@ brevity.
   `--explain`) forward too — they read, so a local run damaged nothing,
   but a catalogue another process is mid-write in is not one anyone can
   answer from. `runReportOnly()` in engine.js is the one implementation
-  both paths call. Exit code comes from `renderErrorCount()`, not
+  both paths call. `--server` / `--watch` are NOT forwardable — they ask
+  to BECOME the instance, and a running engine cannot open a port on
+  someone's behalf — so they exit 1 with a message when one is already
+  there. Exit code comes from `renderErrorCount()`, not
   `process.exitCode` — the engine suppresses that in watch mode by
   design. Config mismatch is refused by resolved PATH; config drift
   under a running instance is detected by stat over `configCoverage`.

package/app.js

@@ -2,7 +2,7 @@
 import path from 'node:path'
 
 import { setup } from './index.js'
-import { forward } from './src/instance.js'
+import { forward, isInstanceLive } from './src/instance.js'
 
 // Before anything is imported or read.
 //
@@ -26,6 +26,12 @@ function locate(argv) {
     }
     const has = (...names) => names.some(n => argv.includes(n) || argv.some(a => names.some(x => a.startsWith(`${x}=`))))
 
+    // Asking to BECOME the instance, rather than asking one for something.
+    // Not forwardable in principle: a running engine cannot open a listener on
+    // someone else's behalf, and forwarding it built, printed "completed" and
+    // exited with nothing on the port.
+    const longRunning = has('--watch', '-w', '--server', '-s')
+
     // What to ask the instance for. Report-only commands go over the same
     // socket as a build: they read, so running them locally never damaged
     // anything, but a catalogue being written by another process is not a
@@ -40,6 +46,7 @@ function locate(argv) {
         : { type: 'build', clear: has('--clear') }
 
     return {
+        longRunning,
         workingFolder: value('--working-folder', '-i') ?? '.',
         config: value('--config', '-c') ?? 'mikser.config.js',
         // Commander's negated form: `attach` is true unless --no-attach said so.
@@ -50,9 +57,25 @@ function locate(argv) {
 
 async function main() {
     const where = locate(process.argv.slice(2))
-    if (where.attach !== false) {
+    const workingFolder = path.resolve(where.workingFolder)
+
+    // A second server or watcher is the hazard this whole surface exists to
+    // remove, and it is the one shape that cannot be answered by forwarding.
+    // So it stops, rather than silently doing something else.
+    if (where.attach !== false && where.longRunning) {
+        if (await isInstanceLive(workingFolder)) {
+            process.stderr.write(
+                'mikser: another mikser is already running in this folder, and a server or watcher cannot be '
+                + 'forwarded to it — it would have to open a port on your behalf.\n'
+                + 'Stop that one, or pass --no-attach to run a second engine here (two engines share the '
+                + 'catalogue and the output tree, with no lock between them).\n')
+            process.exit(1)
+        }
+    }
+
+    if (where.attach !== false && !where.longRunning) {
         const code = await forward({
-            workingFolder: path.resolve(where.workingFolder),
+            workingFolder,
             config: path.resolve(where.workingFolder, where.config),
             request: where.request,
         })

package/docs/diagnostics.md

@@ -756,6 +756,10 @@ Three things it refuses or reports rather than guessing:
 - **A config that moved under the instance.** It stats every file in
   `config.files` and tells you to restart rather than building with a config
   you have since edited.
+- **A second server or watcher.** `mikser --server` and `mikser --watch` ask
+  to *become* the instance, which is not something a running one can do for
+  you — it would have to open a port in your process. They exit 1 and say so,
+  rather than building and leaving nothing on the port.
 - **A folder held by someone else.** `--no-attach` runs a private engine
   anyway — for checking that a cold start works — and says the folder is held.
 
@@ -846,10 +850,11 @@ surfaces that turn silence into a statement:
 - **A pattern or query that matched nothing** — several plugins warn on
   this now (layout patterns, preset matching, null filters). The warnings
   carry stable `code`s in `--json`.
-- **Output that does not match the config** — the config's bytes take
-  part in cache invalidation, so a config change forces a rebuild; but a
-  module the config *imports* does not. If you changed a helper the config
-  pulls in, use `--force`.
+- **Output that does not match the config** — the config's checksum
+  covers the local module graph it imports, not just its own bytes, so
+  editing a helper the config pulls in forces a rebuild the same way
+  editing the config does. A change *outside* that graph — inside an npm
+  dependency — still does not, so use `--force` after upgrading one.
 - **A tool that answers emptily because it is broken** — check
   [`faults`](#faults) before reading an empty result as a fact about the
   site. This is the one case where the answer and the failure are the same
@@ -857,6 +862,21 @@ surfaces that turn silence into a statement:
 - **A plugin that appears to do nothing** — `No plugins loaded` with a
   config present is a warning naming the file. A config that fails to
   load now exits non-zero rather than loading as empty.
+- **A postprocess that could not run** — a stage whose external
+  dependency is absent (no chrome for a PDF, no binary for a conversion)
+  reports a fault naming the subsystem, and each page that wanted that
+  output fails as an ordinary render error. The fault says why once; the
+  errors say who, and set the exit code. A missing dependency does not
+  fail the whole build — the HTML is already written and correct — but it
+  does not pass as clean either.
+- **A link to a file nothing produced** — helpers like `asset()` and
+  `resource()` *build* a URL from a naming convention rather than looking
+  an entity up, so they cannot fail: a preset that never ran, or a
+  template naming an extension the preset no longer emits, yields a
+  well-formed URL to nothing. Every such call is recorded on the render
+  track and checked against the output folder at finalize; what is missing
+  is warned under `asset-missing`, naming the path and the pages that
+  linked it.
 
 ## See also
 

package/docs/rendering.md

@@ -375,6 +375,25 @@ Generates relative URLs to transformed assets (output of the assets plugin). Ret
 
 The underlying path is: `/{assetsFolder}/{preset}/{path}[.{format}]`
 
+#### Checked against the output
+
+The path is *built* from that convention, not looked up, so the helper
+cannot fail — it returns a well-formed URL whether or not anything ever
+produced the file. A preset that did not run, a source that is not
+matched by the preset's patterns, or a template naming a format the
+preset no longer emits all yield a link to nothing, on a build that
+reports success.
+
+So every `asset()` and `resource()` call records its destination on the
+render track, and at finalize the engine checks each one against the
+output folder. Anything missing is warned under the `asset-missing` code,
+naming the path and the pages that linked it, with a summary under
+`asset-missing-summary`. The check follows symlinks, so an assets folder
+deployed into the output as a link resolves normally.
+
+It is a warning, not an error: a build can legitimately link a file that
+some later step supplies. What it removes is the silence.
+
 ---
 
 ### `render-resource` — CDN Resource Mapping
@@ -542,6 +561,16 @@ Return shapes the dispatcher accepts:
 
 A chain is all-or-nothing. The first stage to throw or return `{success: false}` fails the entry; the dispatcher unlinks every intermediate it produced and the final destination, then re-throws. No partial output leaks.
 
+The renderer's own output (`entity.origin`) is the exception: on success the
+dispatcher unlinks it, on failure it stays. It is the input a retry needs, and
+for a converter it is content in its own right — the HTML of a report whose PDF
+could not be produced.
+
+A failed entry counts as a **render error**: it lands in `errors` under `--json`
+with the failing `postprocessor` named, and sets the exit code. It wrote no
+file, so it has to count the same as a render that threw — otherwise a build
+missing every PDF it was asked for reports success.
+
 ### Execution mode
 
 Postprocess inherits the layout's `task:` setting. `task: worker` routes both render and postprocess through the lazy Piscina pool (right for CPU-heavy stages: PDF, image compose, big MJML compilations). Default INLINE is right for everything else.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mikser-io",
-  "version": "9.67.0",
+  "version": "9.70.0",
   "description": "A mixer for content: entities in, configurable render pipelines, outputs of any kind. Static sites are the canonical recipe, not the definition — the same engine renders PDFs, emails and whatever a renderer plugin produces. Files are the source of truth, every lifecycle phase is observable, and the build graph is queryable by an agent.",
   "main": "index.js",
   "exports": {

package/src/engine.js

@@ -11,7 +11,7 @@ import { useJournal, updateEntry } from './journal.js'
 import { globby } from 'globby'
 import { OPERATION, TASKS } from './constants.js'
 import { changeExtension, formatErrorContext, projectMeta, lookupKeys } from './utils.js'
-import { reportRendered, reportSkipped, reportError, renderErrorCount, emitReport, finishCycle } from './report.js'
+import { reportRendered, reportSkipped, reportError, renderErrorCount, emitReport, finishCycle, reportAssetUse, assetUse } from './report.js'
 import { toolSchemas, invokeTool, toolResultText, toolResultFailed } from './tools.js'
 import { registerBuiltinTools } from './builtin-tools.js'
 import { useDatabase } from './database/index.js'
@@ -89,6 +89,43 @@ function workerSafeOptions(opts) {
     return result
 }
 
+// Warn for anything a render linked to that is not in the output.
+//
+// Deliberately phrased as what was OBSERVED. Only entities that rendered this
+// cycle recorded anything, so an incremental build checks the pages it built
+// and says nothing about the rest — the same reasoning the assets plugin
+// already applies to its preset warning, and for the same reason: a warning
+// that overclaims gets filtered, and the filtered-out line is the real one.
+async function reportMissingAssets(logger) {
+    const used = assetUse()
+    if (!used.length) return
+    const outputFolder = runtime.options.outputFolder
+    if (!outputFolder) return
+
+    const missing = []
+    for (const [destination, ids] of used) {
+        const file = path.join(outputFolder, destination.replace(/^\//, ''))
+        if (!existsSync(file)) missing.push([destination, ids])
+    }
+    if (!missing.length) return
+
+    // Capped, with the total alongside. One broken preset can be referenced by
+    // every page on the site, and a thousand lines of it buries whatever else
+    // the build said.
+    const SHOWN = 10
+    for (const [destination, ids] of missing.slice(0, SHOWN)) {
+        logger.warn({ code: 'asset-missing', destination, referencedBy: ids },
+            'Linked but not in the output: %s — referenced by %s', destination,
+            ids.slice(0, 3).join(', ') + (ids.length > 3 ? ` and ${ids.length - 3} more` : ''))
+    }
+    logger.warn({ code: 'asset-missing-summary', missing: missing.length, checked: used.length },
+        '%d of %d linked file(s) are not in the output%s. A URL helper builds the path rather than looking it '
+        + 'up, so this is a link to something nothing produced — usually a preset that did not run, or a '
+        + 'template naming an extension the preset no longer emits.',
+        missing.length, used.length,
+        missing.length > SHOWN ? `, ${SHOWN} shown` : '')
+}
+
 // The report-only commands, as functions that RETURN their exit code.
 //
 // They used to be inline here and call process.exit, which is fine for a
@@ -677,6 +714,15 @@ export async function setup(options) {
                     result = rendered?.output
                     if (rendered?.track) mergeTrack(track, rendered.track)
 
+                    // Which files this entity's template linked to. Harvested
+                    // here because this is the one place that has both the
+                    // track and the entity that produced it — a worker's track
+                    // has just been folded in, so a worker render is covered
+                    // the same as an inline one.
+                    for (const destination of track.assets ?? []) {
+                        reportAssetUse(destination, renderEntity.id)
+                    }
+
                     if (!signal.aborted) {
                         // Meta reads ride on `output`, which is already
                         // free-form JSON on the journal row, rather than in
@@ -1014,6 +1060,17 @@ export async function setup(options) {
                         if (!signal.aborted) {
                             await updateEntry({ id, output: { success: false } })
                             logger.error('Postprocess error: %s%s %s', entity.id, formatErrorContext(entity, err, runtime.options), err.message)
+                            // A failed postprocess wrote no file, so it has to
+                            // count the same as a failed render. It did not:
+                            // this line was the whole of it, the exit code
+                            // stayed 0, and `errors` in --json never mentioned
+                            // it — a build with output missing reporting
+                            // success, which is the exact shape of bug the
+                            // rest of this file exists to make impossible.
+                            reportError(entity, err, {
+                                postprocessor: options.postprocessor ?? null,
+                                layout: entity.layout?.id ?? null,
+                            })
                         }
                         logger.debug('Postprocess canceled')
                     }
@@ -1070,6 +1127,19 @@ export async function setup(options) {
         if (failed) logger.error('Mikser completed with %d render error%s', failed, failed === 1 ? '' : 's')
         else logger.notice('Mikser completed')
 
+        // Is everything the templates linked to actually there?
+        //
+        // The URL helpers build paths; they do not resolve them. So a preset
+        // that never ran, a library that was not copied, or a template naming
+        // an extension the preset stopped producing all yield a well-formed
+        // link to a file that does not exist — and the only symptom is a
+        // missing image on the deployed site, found by a person.
+        //
+        // Checked at the end of the cycle because that is the first moment the
+        // answer is stable: derivatives are produced during the cycle, so
+        // asking any earlier would report files that were about to appear.
+        await reportMissingAssets(useLogger())
+
         // After the cycle, and only under --json. stdout has been kept clear
         // for exactly this (the logger writes to stderr under --json), so the
         // document is the only thing on it and can be piped to jq.

package/src/instance.js

@@ -149,6 +149,35 @@ export function forward({ workingFolder, config, request }) {
     })
 }
 
+// Is somebody already holding this folder?
+//
+// Used by the commands that cannot be forwarded because they are not requests
+// at all — `--server` and `--watch` ask to BECOME the instance. Forwarding one
+// builds and exits, and the port never opens: the caller asked for a server on
+// 3010, got "completed", and has nothing listening.
+//
+// Same stale-socket rule as forward(): connect-and-fail means nobody is there,
+// never a wait.
+export function isInstanceLive(workingFolder) {
+    const endpoint = socketPath(workingFolder)
+    return new Promise((resolve) => {
+        const probe = net.connect(endpoint)
+        let settled = false
+        const answer = (live) => {
+            if (settled) return
+            settled = true
+            try { probe.destroy() } catch { /* already gone */ }
+            if (!live && process.platform !== 'win32' && existsSync(endpoint)) {
+                try { unlinkSync(endpoint) } catch { /* another client won the race */ }
+            }
+            resolve(live)
+        }
+        probe.on('connect', () => answer(true))
+        probe.on('error', () => answer(false))
+        setTimeout(() => answer(false), 1000).unref?.()
+    })
+}
+
 // ── server ──────────────────────────────────────────────────────────────
 
 // Requests run one at a time, to completion.
@@ -409,10 +438,17 @@ export async function warnIfHeld({ workingFolder, attached }) {
 export function instanceControl() {
     serveInstance()
     onLoaded(async () => {
-        if (runtime.options.watch || runtime.options.server) return
+        // Only --no-attach reaches this now. Everything else either forwarded
+        // (a build, a report) or refused before setup ran (a second server or
+        // watcher), so a process that is still here and not attaching is one
+        // that deliberately opted out — and that is exactly the case worth
+        // saying something about, long-running or not. The earlier gate
+        // skipped watch and server, which excluded `--no-attach --server`:
+        // the very command that puts two engines on one folder.
+        if (runtime.options.attach !== false) return
         await warnIfHeld({
             workingFolder: runtime.options.workingFolder,
-            attached: runtime.options.attach,
+            attached: false,
         })
     })
 }

package/src/plugins/assets.js

@@ -231,6 +231,13 @@ export function assets(options = {}) {
             for (let entityPreset of assetsMap[entityToRender.id] || []) {
                 const entity = _.cloneDeep(entityToRender)
                 entity.preset = presets[entityPreset]
+                // Named in config but with no module in presets/ and no
+                // mikser-io-preset-* package: there is nothing to render with.
+                // Loading already reported this preset ('Preset not found'),
+                // and the finalize check names the links left dangling. A line
+                // per entity here would just be that fact a third time, once
+                // per matched file.
+                if (!entity.preset) continue
                 // Per-preset config options override the preset module's
                 // defaults. Looked up at render time so config edits are
                 // picked up on the next cycle without rebuilding the

package/src/plugins/render/asset.js

@@ -15,7 +15,7 @@ import { changeExtension } from '../../utils.js'
 // derivative may simply not have been generated, and this cannot tell.
 // `meta.presets` (ADR-0011) is the looked-up answer where a caller has the
 // entity; this helper exists for the case where they have a path.
-export function load({ runtime, entity, state, options, logger }) {
+export function load({ runtime, entity, state, options, logger, track }) {
     const presets = state?.assets?.presets ?? {}
     const warned = new Set()
     const warnOnce = (key, code, message, ...args) => {
@@ -27,6 +27,15 @@ export function load({ runtime, entity, state, options, logger }) {
     runtime.asset = (preset, url, format) => {
         if (url[0] != '/') url = `/${url}`
 
+        // Handlebars appends its own options object to every helper call, so a
+        // two-argument `{{asset 'web' '/media/hero.jpg'}}` arrives here with a
+        // third. Taken as a format it stringifies, and the helper cheerfully
+        // built `hero.[object Object]` — a well-formed link to a file that
+        // could never exist. file.js strips it for the same reason; this one
+        // never did, and nothing noticed until the output check started
+        // looking at what these URLs point at.
+        if (format && typeof format === 'object' && 'hash' in format) format = undefined
+
         const declared = presets[preset]?.format
 
         // A preset name nothing declares. The URL still gets built — it is a
@@ -57,6 +66,11 @@ export function load({ runtime, entity, state, options, logger }) {
         // happened to be rendering.
         const relative = `${state.assets.assetsFolder}/${preset}${effective ? changeExtension(url, effective) : url}`
         const destination = '/' + relative
+        // Recorded so the engine can check at the end of the cycle whether
+        // this file exists. It is the one thing this helper cannot answer for
+        // itself — it takes a path, not an entity, so there is nothing to look
+        // up and the URL is well-formed whether or not anything produced it.
+        track?.asset?.(destination)
         const from = path.dirname(entity.destination || '/')
         return { url: path.relative(from, destination) }
     }

package/src/plugins/render/resource.js

@@ -1,6 +1,6 @@
 import path from 'node:path'
 
-export function load({ runtime, entity, state, options }) {
+export function load({ runtime, entity, state, options, track }) {
     runtime.resource = (url) => {
         const { resourceLib } = state.resources
         for (let library in resourceLib) {
@@ -9,6 +9,10 @@ export function load({ runtime, entity, state, options }) {
                 const name = url.replace(origin, `${resourceLib[library]}`)
                 const relative = url.replace(origin, `${state.resources.resourcesFolder}/${resourceLib[library]}`)
                 const destination = '/' + relative
+                // Same reason as the asset helper: this builds a URL rather
+                // than resolving one, so a library that was never copied
+                // yields a link to nothing on a green build.
+                track?.asset?.(destination)
                 const from = path.dirname(entity.destination || '/')
                 return { url: path.relative(from, destination), name }
             }

package/src/report.js

@@ -115,6 +115,10 @@ export function resetReport() {
     runtime.state.renderErrors = []
     // Per cycle, unlike the wipe: what changed is a fact about THIS build.
     runtime.state.changed = { ids: [], count: 0 }
+    // Per cycle too: an asset referenced by a page that did not re-render this
+    // time was not re-checked, and claiming otherwise would be the kind of
+    // completeness this codebase keeps having to walk back.
+    runtime.state.assetUse = new Map()
 }
 
 // Published on the runtime so runtime.js can start a fresh cycle for a
@@ -209,6 +213,38 @@ export function reportEvaluated(scope, { evaluated, of } = {}) {
     store().evaluated[scope] = { evaluated: evaluated ?? 0, ...(Number.isFinite(of) ? { of } : {}) }
 }
 
+// Files a render linked to, and who linked to them.
+//
+// The URL helpers build paths rather than resolving them, so nothing they hand
+// a template has been checked against a file: a preset that never ran, or one
+// whose format changed under a template still naming the old extension,
+// produces a well-formed link to nothing. The page renders, the build is
+// green, and the image is missing until somebody looks at the site.
+//
+// Keyed by destination with the referencing entities attached, because "this
+// file is missing" is only actionable next to "and these pages point at it".
+//
+// NOT gated on reportWanted(): the check that reads this runs on every build,
+// and gating it would make a broken link visible only to someone who already
+// suspected one.
+export function reportAssetUse(destination, entityId) {
+    if (!destination) return
+    const store = assetUseStore()
+    if (!store.has(destination)) store.set(destination, new Set())
+    if (entityId) store.get(destination).add(entityId)
+}
+
+function assetUseStore() {
+    runtime.state ??= {}
+    runtime.state.assetUse ??= new Map()
+    return runtime.state.assetUse
+}
+
+// Everything referenced this cycle, as [destination, [entity ids]].
+export function assetUse() {
+    return [...assetUseStore()].map(([destination, ids]) => [destination, [...ids]])
+}
+
 // An entity whose SOURCE did not change is gated at import and never becomes
 // a render task at all — so it appears in neither `rendered` nor `skipped`,
 // and the two lists would not reconcile with the corpus size without saying

package/src/track.js

@@ -40,7 +40,7 @@ export function filterKey(filter) {
 // The returned object exposes `partials: Set<string>` and
 // `queries: Array<filter | null>` directly. Consumers iterate either
 // shape; both are owned by the track for the lifetime of the run.
-export function createTrack({ partial = true, query = true, lookup = true, meta = false, consumed = false } = {}) {
+export function createTrack({ partial = true, query = true, lookup = true, meta = false, consumed = false, assets = true } = {}) {
     const track = {}
     if (lookup) {
         // Lookups a TEMPLATE made by name: runtime.href('/contacts'),
@@ -122,6 +122,26 @@ export function createTrack({ partial = true, query = true, lookup = true, meta
             paths.add(path)
         }
     }
+    if (assets) {
+        // Files a template asked for by URL: a preset derivative, a resource
+        // from a library. Recorded so the engine can check at the end of the
+        // cycle whether the thing being linked to is actually in the output.
+        //
+        // The helpers BUILD these paths — nothing they return has been checked
+        // against a file — so a preset that never ran, or one whose format
+        // changed, produces a perfectly well-formed link to nothing. The page
+        // renders, the build is green, and the image is missing until a person
+        // notices.
+        //
+        // The output-relative destination, not the page-relative url the
+        // helper returns: `../../assets/web/hero.webp` cannot be resolved
+        // without knowing which page asked, and this is the form that maps
+        // straight onto a path under the output folder.
+        const assetRefs = new Set()
+        track.assets = assetRefs
+        track.asset = (destination) => { if (destination) assetRefs.add(destination) }
+    }
+
     if (query) {
         const queries = []
         const queryKeys = new Set()
@@ -282,6 +302,7 @@ export function serializeTrack(track) {
         partials:  track.partials  ? [...track.partials]  : undefined,
         queries:   track.queries   ? [...track.queries]   : undefined,
         metaReads: track.metaReads ? [...track.metaReads] : undefined,
+        assets:    track.assets    ? [...track.assets]    : undefined,
         lookups:   track.lookups   ? [...track.lookups].map(([k, v]) => [k, [...v]]) : undefined,
         consumedReads: track.consumedReads
             ? [...track.consumedReads].map(([k, v]) => [k, [...v]]) : undefined,
@@ -296,6 +317,7 @@ export function mergeTrack(target, data) {
     for (const p of data.partials  ?? []) target.partial?.(p)
     for (const q of data.queries   ?? []) target.query?.(q)
     for (const m of data.metaReads ?? []) target.metaRead?.(m)
+    for (const a of data.assets    ?? []) target.asset?.(a)
     for (const [name, ids] of data.lookups ?? []) target.lookup?.(name, ids)
     for (const [id, paths] of data.consumedReads ?? []) {
         for (const path of paths) target.consumedRead?.(id, path)