@harperfast/template-react-ssr-studio 1.9.2 → 1.10.1

package/agent/skills/harper-best-practices/rules.manifest.yaml

@@ -2,7 +2,7 @@
 #
 # Declarative source of truth for rule taxonomy, sources, and generation mode.
 # Owned by humans; the generator reads this file and writes derived artifacts
-# (rule bodies, AGENTS.md). See docs/plans/docs-driven-skills.md for the
+# (rule bodies, AGENTS.md). See docs/plans-archive/docs-driven-skills.md for the
 # full schema definition and Manifest ↔ frontmatter reconciliation semantics.
 #
 # Phase 2 flipped vector-indexing to mode: generate.
@@ -53,7 +53,20 @@ rules:
     category: schema
     priority: 1
     order: 3
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/database/schema.md
+        section: 'Relationships'
+        role: primary
+      - path: reference/v5/rest/querying.md
+        section: 'Relationships and Joins'
+        role: supplemental
+    must_cover:
+      - '@relationship'
+      - 'from'
+      - 'to'
+      - 'one-to-many'
+      - 'many-to-one'
 
   - rule: vector-indexing
     description: How to enable and query vector indexes for similarity search in Harper.
@@ -79,14 +92,51 @@ rules:
     category: schema
     priority: 1
     order: 5
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/database/schema.md
+        section: 'Blob Type'
+        role: primary
+      - path: reference/v5/database/api.md
+        section: 'Streaming'
+        role: supplemental
+      - path: reference/v5/database/api.md
+        section: '`BlobOptions`'
+        role: supplemental
+      - path: reference/v5/database/api.md
+        section: 'Blob Coercion'
+        role: supplemental
+    must_cover:
+      - 'Blob'
+      - 'createBlob'
+      - 'saveBeforeCommit'
+      - '.bytes()'
+    cross_links:
+      - handling-binary-data
 
   - rule: handling-binary-data
     description: How to store and serve binary data like images or audio in Harper.
     category: schema
     priority: 1
     order: 6
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/database/api.md
+        section: 'Accepting Binary in JSON Requests'
+        role: primary
+      - path: reference/v5/database/api.md
+        section: 'Serving Binary from a Resource'
+        role: primary
+      - path: reference/v5/rest/content-types.md
+        section: 'Storing Arbitrary Content Types'
+        role: supplemental
+    must_cover:
+      - 'createBlob'
+      - 'Content-Type'
+      - 'application/octet-stream'
+      - 'base64'
+    cross_links:
+      - using-blob-datatype
 
   # ===========================================================================
   # API & Communication (priority 2 — HIGH)
@@ -176,21 +226,73 @@ rules:
     category: logic
     priority: 3
     order: 1
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/resources/overview.md
+        section: 'Custom External Data Source'
+        role: primary
+      - path: reference/v5/resources/overview.md
+        section: 'Exporting Resources as Endpoints'
+        role: primary
+      - path: reference/v5/components/javascript-environment.md
+        section: 'Module Loading'
+        role: supplemental
+    must_cover:
+      - 'extends Resource'
+      - 'export class'
+      - 'server.resources.set('
+      - 'static'
 
   - rule: extending-tables
     description: How to add custom logic to automatically generated table resources in Harper.
     category: logic
     priority: 3
     order: 2
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/resources/overview.md
+        section: 'Extending a Table'
+        role: primary
+      - path: reference/v5/resources/resource-api.md
+        section: 'Throwing Errors'
+        role: supplemental
+    must_cover:
+      - 'extends tables.'
+      - 'super.'
+      - '@export'
+      - 'statusCode'
 
   - rule: programmatic-table-requests
     description: How to interact with Harper tables programmatically using the `tables` object.
     category: logic
     priority: 3
     order: 3
-    mode: synthesized
+    mode: generate
+    sources:
+      - path: reference/v5/database/api.md
+        section: '`tables`'
+        role: primary
+      - path: reference/v5/resources/resource-api.md
+        section: 'Query Object'
+        role: primary
+      - path: reference/v5/database/api.md
+        section: '`transaction(context?, callback)`'
+        role: supplemental
+      - path: reference/v5/resources/resource-api.md
+        section: '`update(target: RequestTarget | Id, updates?: object): Promise<Resource>`'
+        role: supplemental
+      - path: reference/v5/resources/resource-api.md
+        section: '`addTo(property: string, value: number)`'
+        role: supplemental
+      - path: reference/v5/components/javascript-environment.md
+        section: 'Module Loading'
+        role: supplemental
+    must_cover:
+      - 'tables'
+      - 'conditions'
+      - 'search('
+      - 'addTo'
+      - 'select'
 
   - rule: typescript-type-stripping
     description: How to run TypeScript files directly in Harper without a build step.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@harperfast/template-react-ssr-studio",
-	"version": "1.9.2",
+	"version": "1.10.1",
 	"type": "module",
 	"repository": "github:HarperFast/create-harper",
 	"scripts": {},

package/skills-lock.json

@@ -5,7 +5,7 @@
       "source": "harperfast/skills",
       "sourceType": "github",
       "skillPath": "harper-best-practices/SKILL.md",
-      "computedHash": "83a152c96356e5c4c1429a96d1f1758738f11ef74aab3e045799bf6b7a4df2d4"
+      "computedHash": "142388c071178e7ae811bfd4f6241e85aef3f715dbfb0ceea1b75e8f370d8080"
     }
   }
 }

package/src/entry-server.jsx

@@ -3,8 +3,26 @@ import { StrictMode } from 'react';
 import { renderToString } from 'react-dom/server';
 
 /**
- * Server render entry. The Vite Harper plugin calls this for HTML navigations and injects the
- * returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ * Server render entry. The Vite Harper plugin calls this (awaiting it) for HTML navigations and
+ * injects the returned markup into the `<!--ssr-outlet-->` placeholder in index.html.
+ *
+ * To render with data already in place (no client-side fetch), read from Harper right here. The
+ * `tables` registry is the same live, process-wide object available everywhere in Harper — the SSR
+ * entry can reach it via `import { tables } from 'harper'` because Harper symlinks
+ * `node_modules/harper` to the running install (and `vite.config.js` keeps `harper` external). Make
+ * `render` async and query a table, e.g.:
+ *
+ *     import { tables } from 'harper';
+ *
+ *     // The template's App takes no props — update App.jsx to accept `product`.
+ *     export async function render(url) {
+ *       const product = await tables.Product.get(idFromUrl(url));
+ *       return renderToString(
+ *         <StrictMode>
+ *           <App product={product} />
+ *         </StrictMode>,
+ *       );
+ *     }
  *
  * @param {string} _url The request URL — use it to drive routing/data loading per request.
  * @returns {string}

package/vite.config.js

@@ -12,6 +12,13 @@ export default defineConfig({
 			'@': path.resolve(import.meta.dirname, './src'),
 		},
 	},
+	ssr: {
+		// Keep `harper` external so the SSR entry resolves it to Harper's running runtime instead of
+		// bundling it. `node_modules/harper` is symlinked to the running install, and symlinked deps
+		// aren't reliably auto-externalized for SSR — this is what lets `import { tables } from 'harper'`
+		// in entry-server read live data. See src/entry-server.jsx.
+		external: ['harper'],
+	},
 	build: {
 		outDir: 'dist',
 		emptyOutDir: true,