@uniweb/projections 0.3.6 → 0.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/projections",
-  "version": "0.3.6",
+  "version": "0.4.0",
   "description": "Projections of a Uniweb site's content — agent index, per-page markdown, search index. Pure JS, runs anywhere.",
   "type": "module",
   "exports": {
@@ -32,7 +32,7 @@
   },
   "dependencies": {
     "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/core": "^0.12.1"
+    "@uniweb/core": "^0.13.0"
   },
   "devDependencies": {
     "vitest": "^4.1.7",

package/src/index.js

@@ -57,7 +57,7 @@ export {
   extractSearchContent,
   generateSearchIndex,
   mergeSearchIndexes,
-  generateCollectionIndex,
+  generateRecordSearchIndex,
   isSearchEnabled,
   getSearchConfig,
   getSearchIndexFilename,

package/src/search/generate.js

@@ -85,7 +85,7 @@ export function generateSearchIndex(siteContent, options = {}) {
  * describe *where the index lives* — only whether it serves queries.
  *
  * @param {Object} pagesIndex - Result of {@link generateSearchIndex}
- * @param {Object[]} [collectionIndexes] - Results of `generateCollectionIndex`
+ * @param {Object[]} [collectionIndexes] - Results of `generateRecordSearchIndex`
  * @returns {Object} One index carrying every entry
  */
 export function mergeSearchIndexes(pagesIndex, collectionIndexes = []) {

package/src/search/index.js

@@ -43,4 +43,4 @@ export {
   getSearchIndexFilename
 } from './generate.js'
 
-export { generateCollectionIndex } from './collections.js'
+export { generateRecordSearchIndex } from './records.js'

package/src/search/{collections.js → records.js}

@@ -63,7 +63,29 @@ const isPrimitive = (v) =>
  */
 const DISPLAY_VALUE_MAX = 200
 
-export function generateCollectionIndex(name, config, collectionData, locale) {
+/**
+ * Search-index entries for one named group of records.
+ *
+ * ⛔ RENAMED from `generateCollectionIndex` — 2026-08-27, and the old name was
+ * wrong in two ways that mattered.
+ *
+ * 1. **"Collection" is FRAMEWORK'S build concept** — a named set our build
+ *    compiles to one file. The live lane has no such thing: a host calls this
+ *    with records it fetched from a folder, so the name put our build
+ *    vocabulary into a function whose main caller is a host. `record` is true on
+ *    both lanes and is what the argument actually holds.
+ * 2. **It never said `search`** — every sibling here does (`generateSearchIndex`,
+ *    `mergeSearchIndexes`, `extractSearchContent`), and "collection index" reads
+ *    as an index OF collections or a collection's own listing. It is neither: it
+ *    is a search index derived FROM records.
+ *
+ * ⚠️ The RESULT still carries the old vocabulary — `type: 'collection'`,
+ * `collection: name`, and `id: "collection:<name>:<slug>"`. That is a data shape
+ * with live consumers (`kit`'s endpoint search provider and hosting's search both
+ * read `entry.collection`), so it is a separate, larger decision than this rename
+ * and is deliberately NOT bundled into it.
+ */
+export function generateRecordSearchIndex(name, config, collectionData, locale) {
   // ⛔ NO DEFAULT FIELD LIST. This was `|| ['title']` — a claim about someone
   // else's schema, and wrong for any collection without a `title` (a `people`
   // collection has `name`, a `products` one has `label`). The failure was