@synap-core/workspace-templates 0.10.0 → 0.12.0

package/package.json

@@ -1,13 +1,11 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "type": "module",
-  "packageManager": "pnpm@9.15.4",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
-      "node": "./dist/index.js",
       "default": "./dist/index.js"
     }
   },
@@ -15,16 +13,6 @@
     "dist",
     "src"
   ],
-  "scripts": {
-    "type-check": "tsc --noEmit",
-    "build:yaml": "node --experimental-strip-types build.mjs",
-    "check:converters": "node scripts/check-converters.mjs",
-    "check:concepts": "node scripts/check-concepts.mjs",
-    "build": "node --experimental-strip-types build.mjs && tsup && node scripts/check-converters.mjs && node scripts/check-concepts.mjs",
-    "provision": "node scripts/provision.mjs",
-    "eval": "node scripts/eval-standard.mjs",
-    "prepublishOnly": "node --experimental-strip-types build.mjs && tsup && node scripts/check-converters.mjs && node scripts/check-concepts.mjs"
-  },
   "dependencies": {
     "zod": "^3.0.0",
     "js-yaml": "^4.1.0"
@@ -37,15 +25,18 @@
   },
   "publishConfig": {
     "registry": "https://registry.npmjs.org",
-    "access": "public",
-    "main": "./dist/index.js",
-    "module": "./dist/index.js",
-    "types": "./dist/index.d.ts",
-    "exports": {
-      ".": {
-        "types": "./dist/index.d.ts",
-        "default": "./dist/index.js"
-      }
-    }
-  }
-}
+    "access": "public"
+  },
+  "scripts": {
+    "type-check": "tsc --noEmit",
+    "build:yaml": "node --experimental-strip-types build.mjs",
+    "check:converters": "node scripts/check-converters.mjs",
+    "check:concepts": "node scripts/check-concepts.mjs",
+    "build": "node --experimental-strip-types build.mjs && tsup && node scripts/check-converters.mjs && node scripts/check-concepts.mjs",
+    "provision": "node scripts/provision.mjs",
+    "eval": "node scripts/eval-standard.mjs"
+  },
+  "main": "./dist/index.js",
+  "module": "./dist/index.js",
+  "types": "./dist/index.d.ts"
+}

package/src/base.template.test.ts

@@ -8,14 +8,14 @@
  * seeders be deleted (Wave 4) without silently changing what every workspace
  * gets.
  *
- * FIDELITY MECHANISM. The report prompts are the product — a single altered
- * character is a regression. Importing `REPORT_AUTOMATION_FLOW` from
- * `@synap/database` into this frontend package would be an upward layering
- * violation, so instead the byte-for-byte guardrail is a COMMITTED, GENERATED
- * fixture (`__fixtures__/report-automation-flow.json`) snapshotted from the
- * backend const at authoring time, never hand-typed. The chain the test proves:
- *     compiled base flow  ===  fixture  (=== REPORT_AUTOMATION_FLOW at capture).
- * Same for the 23-ish relation defs via `__fixtures__/default-relation-defs.json`.
+ * FIDELITY MECHANISM. base.yaml is now the SINGLE source of the report flow —
+ * the backend `REPORT_AUTOMATION_FLOW` const it was once snapshotted against was
+ * retired, and with it the `__fixtures__/report-automation-flow.json` copy-pin
+ * (a copy pinned to a copy caught no upstream drift). The report flow is guarded
+ * here directly instead: the prompt-fragment smoke check below proves the product
+ * content survived, and `templates-freshness.test.ts` pins templates.ts == the
+ * YAML source. The 23-ish relation defs KEEP their byte-for-byte fixture
+ * guardrail (`__fixtures__/default-relation-defs.json`).
  */
 
 import { readFileSync } from "fs";
@@ -55,18 +55,13 @@ describe("Task A — report automation, byte-faithful", () => {
     expect(automation?.description).toMatch(/Gather this workspace's state/);
   });
 
-  it("flow BYTE-MATCHES the REPORT_AUTOMATION_FLOW snapshot", () => {
-    const fixture = readFixture("report-automation-flow.json");
-    // deep-equal: the compiled template's flow is JSON.stringify(parsed YAML), so
-    // a deep-equal against the JSON snapshot of the source const proves the
-    // transcription is lossless (nodes, edges, and every prompt string).
-    expect(automation?.flow).toEqual(fixture);
-  });
-
   it("preserves the load-bearing hardened prompt fragments (v13)", () => {
-    // A coarse smoke check that the specific product content survived — the
-    // deep-equal above is authoritative, but these named fragments make a
-    // regression legible if the fixture is ever regenerated wrongly.
+    // The primary guardrail that the report flow's product content survived in
+    // base.yaml. (A byte-for-byte fixture pin used to sit above this, snapshotting
+    // the retired backend `REPORT_AUTOMATION_FLOW` const; with that const gone
+    // base.yaml is the single source, so a copy-pinned-to-a-copy proved nothing
+    // and was dropped. `templates-freshness.test.ts` pins templates.ts == the
+    // YAML source.)
     const flowStr = JSON.stringify(automation?.flow);
     for (const marker of [
       "COUNTS — the exact number of records gathered",
@@ -77,6 +72,17 @@ describe("Task A — report automation, byte-faithful", () => {
       expect(flowStr).toContain(marker);
     }
   });
+
+  it("carries the v15 retry policy on all four AI rounds (regression guard)", () => {
+    // v15's fix for the 2026-08-03 finishReason=length incident: each of the four
+    // ai.generate rounds (analyze/relate/assemble/summarize) gets ONE retry with a
+    // 5s delay. This field dropped SILENTLY once — the 700→2000 fix ported maxTokens
+    // into base.yaml but not the retry policy, so it went missing on the reconcile-
+    // winning path. Assert it here (base.yaml is the SSOT now) so it can't drift again.
+    const flowStr = JSON.stringify(automation?.flow);
+    expect((flowStr.match(/"retryDelay":5000/g) ?? []).length).toBe(4);
+    expect((flowStr.match(/"maxRetries":1(?=[,}])/g) ?? []).length).toBe(4);
+  });
 });
 
 describe("Task B — relation defs, full coverage", () => {

package/src/base.yaml

@@ -455,9 +455,11 @@ automations:
                 Notes — {{steps.gather-notes.output.count}} found: {{steps.project-notes.output.result}}
                 People — {{steps.gather-people.output.count}} found: {{steps.project-people.output.result}}
                 Companies — {{steps.gather-companies.output.count}} found: {{steps.project-companies.output.result}}
-              maxTokens: "700"
+              maxTokens: "2000"
             errorHandling:
               continueOnError: true
+              maxRetries: 1
+              retryDelay: 5000
         - id: relate
           type: capability
           position:
@@ -537,9 +539,11 @@ automations:
                 is busy, a company with people but no tasks. Write only observations
                 that span TWO OR MORE records or kinds. If there are none, say what you
                 checked and did not find — never answer with nothing.
-              maxTokens: "700"
+              maxTokens: "2000"
             errorHandling:
               continueOnError: true
+              maxRetries: 1
+              retryDelay: 5000
         - id: assemble
           type: capability
           position:
@@ -724,6 +728,9 @@ automations:
                 RELATE ROUND MATERIAL:
                 {{steps.relate.output}}
               maxTokens: "2000"
+            errorHandling:
+              maxRetries: 1
+              retryDelay: 5000
         - id: summarize
           type: capability
           position:
@@ -742,6 +749,9 @@ automations:
                 Material to summarize (may be an error object if the round failed):
                 {{steps.analyze.output}}
               maxTokens: "500"
+            errorHandling:
+              maxRetries: 1
+              retryDelay: 5000
         - id: guard-assembled
           type: guard
           position:

package/src/blockchain-ecosystem.yaml

@@ -47,6 +47,10 @@ profiles:
     description: A liquidity provider — makes markets and provides depth for a token.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -81,6 +85,10 @@ profiles:
     description: A security firm or individual that audits smart contracts and protocols.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -115,6 +123,10 @@ profiles:
     description: An outsourced engineering studio or build partner.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -149,6 +161,10 @@ profiles:
     description: A brand, growth, or content marketing agency.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -183,6 +199,10 @@ profiles:
     description: A performance / paid-media buying agency.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -217,6 +237,10 @@ profiles:
     description: A key opinion leader or influencer who amplifies reach.
     scope: shared
     profileKind: role
+    # Shared supply-role category → the intro-matcher's roster spans ALL roles
+    # tagged "provider" via entity.query { roleCategory: "provider" } (no per-role
+    # hardcoding). Keep this string in sync with networking.yaml's solution-provider.
+    roleCategory: provider
     applicableKinds:
       - company
       - person
@@ -243,6 +267,88 @@ profiles:
         valueType: string
         inputType: textarea
 
+  # ── Grant Program (the per-chain funding PROGRAM — parent of a round) ───────
+  # The 3-layer grants spine is PROGRAM ≠ ROUND ≠ APPLICATION. `round` (in
+  # grants.yaml) is the funding-cycle/deadline carrier; a program is the
+  # long-lived, chain-scoped funder above it (e.g. Stellar SCF, Optimism RetroPGF).
+  # It lives HERE, with the web3 vocabulary, because a program IS a blockchain-
+  # ecosystem thing (it carries a `blockchain` and program mechanics), and it is
+  # a real-world entity referenced from every workspace — hence pod-wide, mirroring
+  # company/person in ecosystem.yaml (`entityScope: pod`). `scope: shared` makes
+  # the profile DEF pod-wide too, so a REUSING template (grants.yaml `require`s this
+  # overlay) resolves `grant-program` for its `round → belongs_to → grant-program`
+  # edge and deadline view. `defaultPlaybook` is a text ref for now — Wave 2 will
+  # create the actual per-chain playbook and bind it.
+  - slug: grant-program
+    displayName: Grant Program
+    icon: landmark
+    color: emerald
+    description: A per-chain funding program (e.g. Stellar SCF, Optimism RetroPGF) — the long-lived funder above a round.
+    profileKind: kind
+    entityScope: pod
+    scope: shared
+    properties:
+      - slug: blockchain
+        label: Blockchain / Chain
+        valueType: string
+        inputType: text
+      - slug: programName
+        label: Program Name
+        valueType: string
+        inputType: text
+      - slug: programType
+        label: Program Type
+        valueType: string
+        inputType: select
+        enumValues:
+          - direct
+          - retroactive
+          - quadratic
+          - rfp
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - active
+          - paused
+          - retired
+      - slug: url
+        label: Program URL
+        valueType: string
+        inputType: url
+      - slug: cadence
+        label: Cadence
+        valueType: string
+        inputType: text
+        placeholder: every 6 weeks
+      - slug: nextDeadline
+        label: Next Deadline
+        valueType: date
+        inputType: date
+      - slug: submissionTracks
+        label: Submission Tracks
+        valueType: array
+        inputType: text
+      - slug: trancheModel
+        label: Tranche Model
+        valueType: string
+        inputType: text
+        placeholder: 4 tranches / 90 days
+      - slug: defaultPlaybook
+        label: Default Playbook
+        valueType: string
+        inputType: text
+        # Defaults to the BASE grant playbook (grants.yaml `Grant Process`), the
+        # data-driven process that reads THIS program's cadence/tracks/tranche
+        # model at runtime. Override per-program only for a differently-shaped chain.
+        constraints:
+          defaultValue: Grant Process
+      - slug: description
+        label: Description
+        valueType: string
+        inputType: textarea
+
 # Web3 actor↔actor relations (company→company). `company` resolves from the
 # Ecosystem base — not redeclared here.
 entityLinks:

package/src/builder.yaml

@@ -1,6 +1,17 @@
 # Builder workspace template
 # Developer + agent intelligence layer.
-# Generated from synap-app/apps/devplane/lib/builderWorkspaceDefinition.ts (source of truth).
+#
+# ✅ SINGLE SOURCE OF TRUTH for the Builder workspace, on every door.
+# Both doors now derive from this file:
+#   • apps/devplane/lib/builderWorkspaceDefinition.ts → the devplane onboarding
+#     path (trpc.workspaces.createFromDefinition) — since 2026-09-05 that module
+#     is a five-line `toWorkspaceDefinition("builder-workspace")` derivation
+#   • the registry / marketplace install path — same seam
+# Until 2026-09-05 the TS file held a ~1,150-line hand-typed PEER copy of this
+# workspace and nothing compared the two, which produced five real divergences
+# (four capabilities, a dead-Coolify seed pair, defaultApp/primarySurface, an
+# unprefixed calendar dateField, and this file's playbooks/onboarding). Edit the
+# schema HERE; there is no second copy to keep in sync.
 
 meta:
   slug: builder-workspace
@@ -23,6 +34,13 @@ workspace:
     - builder.deployments
     - builder.agents
     - builder.packages
+    # Tier-1 signal for `resolveWorkspaceForScope` — must match the DevPlane app
+    # manifest's `defaultScope.capability` (browser/…/apps/manifest.ts) and the
+    # `workspaceCapabilities` list the devplane door derives from this block.
+    # Without it a workspace created through THIS door fails all four resolver tiers
+    # (no capability · subtype "builder" ≠ kind "devplane" · name "Builder" ≠ "DevPlane")
+    # and the workspace press falls silently to a setup card.
+    - devplane.workspace
 
 profiles:
   - slug: devplane_app