npm - spexcode - Versions diffs - 0.2.8 → 0.3.0 - Mend

spexcode 0.2.8 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (97) hide show

package/spec-dashboard/dist/index.html CHANGED Viewed

@@ -19,8 +19,8 @@
         } catch (e) { /* localStorage/matchMedia unavailable — default (light) stands */ }
       })()
     </script>
-    <script type="module" crossorigin src="/assets/index-BhIslAau.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-uGs9v_9o.css">
+    <script type="module" crossorigin src="/assets/index-Ce0wDyQS.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-Cc26X4ce.css">
   </head>
   <body>
     <div id="root"></div>

package/{spec-yatsu → spec-eval}/src/cache.ts RENAMED Viewed

@@ -6,9 +6,11 @@ import { gitCommonDir } from '../../spec-cli/src/layout.js'
 export const MISS_BLOB = 'miss original file'
 // every cache fn takes an optional `dir` (defaulting to the live cache dir) so the logic is testable
-// against a temp dir without a git repo.
+// against a temp dir without a git repo. The dir is a PER-CLONE cache (never tracked): renaming it
+// (yatsu-blobs → evidence, v0.3.0) migrated no bytes — a missing blob re-fills via `spex evidence put`
+// (putBlob is idempotent by content) or streams from the backend on a `get` miss.
 export function cacheDir(): string {
-  return join(gitCommonDir(), 'spexcode', 'yatsu-blobs')
+  return join(gitCommonDir(), 'spexcode', 'evidence')
 }
 // a content-addressed blob name = the sha256 of its bytes (64 hex). The backstop recognises a stray one.
@@ -60,9 +62,10 @@ export function getBlob(sha: string | null, dir = cacheDir()): Buffer | null {
   return hasBlob(sha, dir) ? readFileSync(blobPath(sha!, dir)) : null
 }
-// is a staged repo path a stray content-addressed blob? (a 64-hex basename, or anything under a
-// yatsu-blobs dir). The pre-commit backstop rejects these so pixels never leak into git history.
+// is a staged repo path a stray content-addressed blob? (a 64-hex basename, or anything under a copied-in
+// evidence cache dir — the retired `yatsu-blobs` name included, since a stray copy of an ARCHIVED cache is
+// the same mistake). The pre-commit backstop rejects these so pixels never leak into git history.
 export function isStrayBlob(path: string): boolean {
   const base = path.slice(path.lastIndexOf('/') + 1)
-  return BLOB_NAME.test(base) || path.includes('/yatsu-blobs/')
+  return BLOB_NAME.test(base) || path.includes('spexcode/evidence/') || path.includes('/yatsu-blobs/') // dead-words-ok: archived cache dir name — a stray copy of the retired cache is still rejected
 }