@volter/twin-standard 1.0.100 → 1.0.102

package/dist/src/create-pack.js

@@ -18,7 +18,7 @@ var __rewriteRelativeImportExtension = (this && this.__rewriteRelativeImportExte
 //                                                        sending each lane's host to it
 //                                                          (package.json, README.md, LICENSE, src/{manifest,fetch,server,cli,
 //                                                          index}.ts, src/semantics/{states,shared,doors}.ts,
-//                                                          journeys/demand.json): the author fills the manifest's
+//                                                          journeys/{demand,first-use}.json): the author fills the manifest's
 //                                                          vendor facts, the descriptor's hosts and the families
 //   bun scripts/create-pack.ts <unit> --index            write src/semantics/index.ts, the handler map, and src/fetch.ts from the
 //                                                          families' files (every exported function, by its name)
@@ -371,6 +371,16 @@ export function initFiles(vendor) {
         'tsconfig.json': TSCONFIG,
         'README.md': `# @volter/twin-${vendor}\n\nThe ${vendor} twin (Protocol 3). Its surface is derived from the vendor's spec (\`spec/\`, provenance in\n\`spec/SOURCE.md\`); what it serves and why is its manifest and semantics.\n\nRules, layout and tools: twin-world's architecture ("Protocol 3", "The catalog: where twins come from").\n`,
         'journeys/demand.json': `${JSON.stringify({ measured: 'FILL: when and how the applications were read', applications: [] }, null, 1)}\n`,
+        // Deliberately incomplete: the author supplies the SDK entry with the outline, before semantics. Keeping the file
+        // present prevents a new vendor from falling back to an older standard fixture; empty commands cannot qualify.
+        'journeys/first-use.json': `${JSON.stringify({
+            schemaVersion: 1,
+            source: 'FILL: the vendor quickstart and demand-pinned official SDK',
+            about: 'FILL: the customer outcome, identity, default SDK calls and stored result',
+            files: { 'package.json': '', '.env.example': '' },
+            run: [],
+            retention: { readback: [] },
+        }, null, 2)}\n`,
         'src/semantics/states.ts': `// ${vendor}'s state machines and state rulings, each transition cited (architecture, "State").\nexport const states = {};\n`,
         'src/semantics/shared.ts': `// What every family of ${vendor} shares: its stored shapes, who is calling, and the vendor's answers.\nimport type { HandlerContext } from '@volter/world-core';\n\nexport type Row = Record<string, unknown>;\nexport type { HandlerContext };\n`,
         'src/semantics/doors.ts': `// The World's doors (architecture, "Doors, screens and the gap"): what the vendor's own pages do that its API does\n// not, each declared in the manifest's \`doors\` (its id, method and path under \`/_twin/\`) and answered here by the\n// export its id names, over the contract's context.\nimport type { HandlerContext } from '@volter/world-core';\n\nexport type { HandlerContext };\n`,
@@ -391,6 +401,7 @@ export function laneInitFiles(vendor, lanes) {
         'package.json': single['package.json'].replace('"spec",', lanes.map((l) => `"${l}",`).join('\n    ')),
         'README.md': `# @volter/twin-${vendor}\n\nThe ${vendor} twin (Protocol 3), one lane per API: ${lanes.map((l) => `\`${l}/\``).join(', ')}, each derived from its own spec\n(\`<lane>/spec/\`, provenance in its SOURCE.md). FILL: what each lane is of.\n`,
         'journeys/demand.json': single['journeys/demand.json'],
+        'journeys/first-use.json': single['journeys/first-use.json'],
         'tsconfig.json': TSCONFIG,
         // the vendor's front, as data: its lanes and how its gateway routes them, its discovery facts, its descriptor. The
         // kernel serves it (createVendorFetch, from the generated fetch.ts); nothing routes by hand

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/twin-standard",
-  "version": "1.0.100",
+  "version": "1.0.102",
   "description": "The Protocol 3 standard for Volter twin packs: the criteria a pack is graded by, the grader, the gate a pack repository and the twin catalog run on every change and submission, and the spec derivation the grade checks against. Pin a version: every place a pack is judged judges by that standard.",
   "keywords": [
     "twin",
@@ -75,7 +75,7 @@
     "yaml": "2.9.0"
   },
   "peerDependencies": {
-    "@volter/world-core": "3.0.108",
+    "@volter/world-core": "3.0.110",
     "@volter/world-runtime": "*",
     "playwright": "^1.63.0"
   },

package/src/create-pack.ts

@@ -10,7 +10,7 @@
 //                                                        sending each lane's host to it
 //                                                          (package.json, README.md, LICENSE, src/{manifest,fetch,server,cli,
 //                                                          index}.ts, src/semantics/{states,shared,doors}.ts,
-//                                                          journeys/demand.json): the author fills the manifest's
+//                                                          journeys/{demand,first-use}.json): the author fills the manifest's
 //                                                          vendor facts, the descriptor's hosts and the families
 //   bun scripts/create-pack.ts <unit> --index            write src/semantics/index.ts, the handler map, and src/fetch.ts from the
 //                                                          families' files (every exported function, by its name)
@@ -362,6 +362,16 @@ export function initFiles(vendor: string): Record<string, string> {
     'tsconfig.json': TSCONFIG,
     'README.md': `# @volter/twin-${vendor}\n\nThe ${vendor} twin (Protocol 3). Its surface is derived from the vendor's spec (\`spec/\`, provenance in\n\`spec/SOURCE.md\`); what it serves and why is its manifest and semantics.\n\nRules, layout and tools: twin-world's architecture ("Protocol 3", "The catalog: where twins come from").\n`,
     'journeys/demand.json': `${JSON.stringify({ measured: 'FILL: when and how the applications were read', applications: [] }, null, 1)}\n`,
+    // Deliberately incomplete: the author supplies the SDK entry with the outline, before semantics. Keeping the file
+    // present prevents a new vendor from falling back to an older standard fixture; empty commands cannot qualify.
+    'journeys/first-use.json': `${JSON.stringify({
+      schemaVersion: 1,
+      source: 'FILL: the vendor quickstart and demand-pinned official SDK',
+      about: 'FILL: the customer outcome, identity, default SDK calls and stored result',
+      files: { 'package.json': '', '.env.example': '' },
+      run: [],
+      retention: { readback: [] },
+    }, null, 2)}\n`,
     'src/semantics/states.ts': `// ${vendor}'s state machines and state rulings, each transition cited (architecture, "State").\nexport const states = {};\n`,
     'src/semantics/shared.ts': `// What every family of ${vendor} shares: its stored shapes, who is calling, and the vendor's answers.\nimport type { HandlerContext } from '@volter/world-core';\n\nexport type Row = Record<string, unknown>;\nexport type { HandlerContext };\n`,
     'src/semantics/doors.ts': `// The World's doors (architecture, "Doors, screens and the gap"): what the vendor's own pages do that its API does\n// not, each declared in the manifest's \`doors\` (its id, method and path under \`/_twin/\`) and answered here by the\n// export its id names, over the contract's context.\nimport type { HandlerContext } from '@volter/world-core';\n\nexport type { HandlerContext };\n`,
@@ -383,6 +393,7 @@ export function laneInitFiles(vendor: string, lanes: string[]): Record<string, s
     'package.json': single['package.json']!.replace('"spec",', lanes.map((l) => `"${l}",`).join('\n    ')),
     'README.md': `# @volter/twin-${vendor}\n\nThe ${vendor} twin (Protocol 3), one lane per API: ${lanes.map((l) => `\`${l}/\``).join(', ')}, each derived from its own spec\n(\`<lane>/spec/\`, provenance in its SOURCE.md). FILL: what each lane is of.\n`,
     'journeys/demand.json': single['journeys/demand.json']!,
+    'journeys/first-use.json': single['journeys/first-use.json']!,
     'tsconfig.json': TSCONFIG,
     // the vendor's front, as data: its lanes and how its gateway routes them, its discovery facts, its descriptor. The
     // kernel serves it (createVendorFetch, from the generated fetch.ts); nothing routes by hand