mikser-io 9.19.0 → 9.19.1

package/docs/diagnostics.md

@@ -106,9 +106,16 @@ there is no manifest to check against.
 npx mikser --verify || echo "output folder has drifted"
 ```
 
-`Orphan` is the one to read carefully — it is normal for files that
-another plugin writes (assets, files, data), and a real signal for a page
-whose layout stopped producing it.
+A destination is resolved against the output folder first and, when that
+finds nothing, treated as a filesystem path — assets carry an absolute
+destination built from `assetsFolder`, which may sit outside the output
+folder entirely.
+
+`Orphan` still needs reading with that in mind: only files under the
+output folder are walked, and a file is an orphan when no snapshot claims
+it. That is normal for anything written without a render snapshot (the
+`files` and `data` plugins), and a real signal for a page whose layout
+stopped producing it.
 
 ### The rest, briefly
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mikser-io",
-  "version": "9.19.0",
+  "version": "9.19.1",
   "description": "<p align=\"center\">   <img src=\"mikser-lockup-stacked.svg\" alt=\"mikser\" width=\"198\" /> </p>",
   "main": "index.js",
   "exports": {

package/src/engine.js

@@ -265,8 +265,15 @@ export async function setup(options) {
             for (const e of unverifiable) logger.warn('No hash:    %s (entity %s)', e.destination, e.id)
             for (const e of orphaned)    logger.warn('Orphan:     %s', e.path)
 
+            // Level picked from the verdict, because the level IS the marker
+            // in pino-pretty's messageFormat: notice renders 🟢, warn 🟡,
+            // error 🔴. A fixed `notice` prints a green tick next to the word
+            // FAIL, which reads as success at a glance even though the exit
+            // code is right.
             const verdict = errors > 0 ? 'FAIL' : (warnings > 0 ? 'WARN' : 'OK')
-            logger.notice('Verify %s: %d snapshots, %d missing, %d mismatched, %d unverifiable, %d orphaned',
+            const report = errors > 0 ? logger.error : (warnings > 0 ? logger.warn : logger.notice)
+            report.call(logger,
+                'Verify %s: %d snapshots, %d missing, %d mismatched, %d unverifiable, %d orphaned',
                 verdict, total, missing.length, mismatched.length, unverifiable.length, orphaned.length)
             process.exit(errors > 0 ? 2 : (warnings > 0 ? 1 : 0))
         }

package/src/manifest.js

@@ -66,7 +66,10 @@ import { useDatabase, registerSchema } from './database/index.js'
 // PK index, no separate id index needed. Parent index is for pagination
 // cleanup (drop all children of X). WITHOUT ROWID keeps the file
 // smaller.
-registerSchema('mikser_snapshots', `
+// Exported so tests build against the real schema rather than a copy. A
+// copy drifts the moment a column is added, and the failure is a bare
+// SQLITE_ERROR that names nothing.
+export const SNAPSHOTS_SCHEMA = `
     CREATE TABLE IF NOT EXISTS mikser_snapshots (
         id          TEXT NOT NULL,
         destination TEXT NOT NULL,
@@ -78,7 +81,8 @@ registerSchema('mikser_snapshots', `
         PRIMARY KEY (id, destination)
     ) WITHOUT ROWID;
     CREATE INDEX IF NOT EXISTS idx_mikser_snapshots_parent ON mikser_snapshots(parent) WHERE parent IS NOT NULL;
-`)
+`
+registerSchema('mikser_snapshots', SNAPSHOTS_SCHEMA)
 
 // Module-level DB handle + prepared statements for the lifecycle
 // integration. Tests build their own via `createManifest(db)` —
@@ -548,8 +552,41 @@ export function createManifest(db) {
             for (const row of stmtSelectAll.iterate()) {
                 const snap = rowToSnap(row)
                 if (!snap.destination) continue
-                claimed.add(snap.destination.replace(/^\/+/, ''))
-                const filePath = path.join(outputFolder, snap.destination)
+                // `destination` arrives in two shapes and both are legitimate.
+                // A page's is output-relative with a leading slash
+                // (`/bg/index.html`); an asset's is a real filesystem path,
+                // because assets.js builds it from
+                // `runtime.options.assetsFolder` — which resolves inside the
+                // WORKING folder and may sit outside outputFolder entirely
+                // (a `derived/` tree that `shares` symlinks into each language
+                // root is the case that proves it).
+                //
+                // `path.isAbsolute` cannot tell them apart: on POSIX
+                // `/bg/index.html` is absolute too. So resolve by EXISTENCE,
+                // output-relative first — that is the dominant shape, and a
+                // page destination interpreted as a filesystem path would
+                // otherwise be looked for at the root of the disk.
+                //
+                // Only the fallback path is a filesystem path, so it is only
+                // tried when the destination is absolute and joining changed
+                // nothing that resolves.
+                const joined = path.join(outputFolder, snap.destination)
+                let filePath = joined
+                if (!existsSync(joined)
+                    && path.isAbsolute(snap.destination)
+                    && existsSync(snap.destination)) {
+                    filePath = snap.destination
+                }
+                // Orphan detection compares against a globby walk of
+                // outputFolder, so `claimed` has to hold exactly the relative
+                // form that walk produces. A destination resolving outside
+                // outputFolder can never appear in it and is not claimable;
+                // one inside it must be claimed by its relative path, not by
+                // the raw string with its leading slashes stripped.
+                const relative = path.relative(outputFolder, filePath)
+                if (relative && !relative.startsWith('..') && !path.isAbsolute(relative)) {
+                    claimed.add(relative)
+                }
                 if (!existsSync(filePath)) {
                     missing.push({ id: snap.id, destination: snap.destination })
                     continue