@venturewild/workspace 0.5.3 → 0.6.0

package/server/src/bazaar/seed-recipes/personal-portfolio/recipe.json

@@ -1,24 +1,24 @@
-{
-  "id": "personal-portfolio",
-  "title": "Personal portfolio site",
-  "producer": { "name": "Nia", "handle": "nia", "kind": "maker" },
-  "pitch": "A sharp one-page portfolio — intro, projects, contact — live in one shot.",
-  "vendorDescription": "Nia's portfolio template. The layout that landed her three freelance clients: a confident intro, a project grid, and a contact line that converts.",
-  "summary": "A single-page portfolio: hero intro, a grid of project cards, and a contact section. Swap the text and images to make it yours.",
-  "outcomeScore": 0.81,
-  "outcomeStats": { "builds": 40, "working": 32 },
-  "safetyBadge": "tested",
-  "rating": { "stars": 4.3, "count": 21 },
-  "tags": [
-    "portfolio", "personal site", "personal website", "resume site", "cv site",
-    "about me", "showcase", "designer portfolio", "developer portfolio", "projects"
-  ],
-  "reward": {
-    "model": "one-time",
-    "unit": "per build",
-    "perUseValue": 0,
-    "oneTimeValue": 5.0,
-    "note": "Nia earns a one-time share each time her portfolio know-how is used."
-  },
-  "buildDir": "portfolio"
-}
+{
+  "id": "personal-portfolio",
+  "title": "Personal portfolio site",
+  "producer": { "name": "Nia", "handle": "nia", "kind": "maker" },
+  "pitch": "A sharp one-page portfolio — intro, projects, contact — live in one shot.",
+  "vendorDescription": "Nia's portfolio template. The layout that landed her three freelance clients: a confident intro, a project grid, and a contact line that converts.",
+  "summary": "A single-page portfolio: hero intro, a grid of project cards, and a contact section. Swap the text and images to make it yours.",
+  "outcomeScore": 0.81,
+  "outcomeStats": { "builds": 40, "working": 32 },
+  "safetyBadge": "tested",
+  "rating": { "stars": 4.3, "count": 21 },
+  "tags": [
+    "portfolio", "personal site", "personal website", "resume site", "cv site",
+    "about me", "showcase", "designer portfolio", "developer portfolio", "projects"
+  ],
+  "reward": {
+    "model": "one-time",
+    "unit": "per build",
+    "perUseValue": 0,
+    "oneTimeValue": 5.0,
+    "note": "Nia earns a one-time share each time her portfolio know-how is used."
+  },
+  "buildDir": "portfolio"
+}

package/server/src/bazaar/seed-recipes/receipt-sorter/know-how.md

@@ -1,31 +1,31 @@
-# Sam's receipt-sorter — how to build it
-
-> Absorb this and build the user a receipt-sorting tool in one shot. Single
-> self-contained `index.html` (inline CSS + JS), no build step, runs offline.
-
-## Build steps
-
-1. Create `receipt-sorter/index.html`.
-2. The page:
-   - A **textarea** to paste receipts, one per line, in a loose form like
-     `2026-03-04  Uber  18.50` or `Adobe subscription 52.99`. Prefill with ~6
-     realistic example lines so it's usable immediately.
-   - A **"Sort receipts"** button.
-   - A **results table**: columns Date · Vendor · Category · Amount, best-effort
-     parsed from each line. Below it, a **category breakdown** (sum per category)
-     and a **grand total**.
-3. Categorize with a simple keyword map you can extend, e.g. Uber/Lyft/taxi →
-   Travel; restaurant/coffee/lunch → Meals; Adobe/Figma/subscription/SaaS →
-   Software; staples/paper/supplies → Supplies; everything else → Other.
-4. Parse the amount as the last number on the line; parse a leading ISO date if
-   present. Be forgiving — never crash on a weird line, just put it in "Other".
-5. House style: clean, tabular, easy to scan. One accent color. A small "Export
-   CSV" button that downloads the table is a nice touch.
-
-## Finish
-
-After writing the files:
-
-1. Call **`launch_preview`** with `{ "dir": "receipt-sorter" }`.
-2. Call **`record_use`** with recipe id `receipt-sorter` and a short summary.
-3. Tell the user it's live in the preview, briefly.
+# Sam's receipt-sorter — how to build it
+
+> Absorb this and build the user a receipt-sorting tool in one shot. Single
+> self-contained `index.html` (inline CSS + JS), no build step, runs offline.
+
+## Build steps
+
+1. Create `receipt-sorter/index.html`.
+2. The page:
+   - A **textarea** to paste receipts, one per line, in a loose form like
+     `2026-03-04  Uber  18.50` or `Adobe subscription 52.99`. Prefill with ~6
+     realistic example lines so it's usable immediately.
+   - A **"Sort receipts"** button.
+   - A **results table**: columns Date · Vendor · Category · Amount, best-effort
+     parsed from each line. Below it, a **category breakdown** (sum per category)
+     and a **grand total**.
+3. Categorize with a simple keyword map you can extend, e.g. Uber/Lyft/taxi →
+   Travel; restaurant/coffee/lunch → Meals; Adobe/Figma/subscription/SaaS →
+   Software; staples/paper/supplies → Supplies; everything else → Other.
+4. Parse the amount as the last number on the line; parse a leading ISO date if
+   present. Be forgiving — never crash on a weird line, just put it in "Other".
+5. House style: clean, tabular, easy to scan. One accent color. A small "Export
+   CSV" button that downloads the table is a nice touch.
+
+## Finish
+
+After writing the files:
+
+1. Call **`launch_preview`** with `{ "dir": "receipt-sorter" }`.
+2. Call **`record_use`** with recipe id `receipt-sorter` and a short summary.
+3. Tell the user it's live in the preview, briefly.

package/server/src/bazaar/seed-recipes/receipt-sorter/recipe.json

@@ -1,25 +1,25 @@
-{
-  "id": "receipt-sorter",
-  "title": "Sort receipts into a tidy expense table",
-  "producer": { "name": "Sam", "handle": "sam", "kind": "maker" },
-  "pitch": "Paste a pile of receipts and get a clean, categorized expense table with totals — built in one shot.",
-  "vendorDescription": "Sam built this to stop drowning in shoebox receipts at tax time. Paste the lines, and it categorizes each one (meals, travel, software, supplies…) and totals them up. His agent packaged it so anyone can use it.",
-  "summary": "A single page where you paste receipt lines and get a sorted, categorized table with a running total and a category breakdown. No spreadsheet skills needed.",
-  "outcomeScore": 0.83,
-  "outcomeStats": { "builds": 22, "working": 18 },
-  "safetyBadge": "tested",
-  "rating": { "stars": 4.4, "count": 14 },
-  "tags": [
-    "receipts", "receipt", "expenses", "expense", "bookkeeping", "spreadsheet",
-    "csv", "accounting", "invoices", "invoice", "tax", "taxes", "sort",
-    "categorize", "budget", "finance", "money tracking"
-  ],
-  "reward": {
-    "model": "one-time",
-    "unit": "per build",
-    "perUseValue": 0,
-    "oneTimeValue": 5.0,
-    "note": "Sam earns a one-time share each time his receipt-sorter know-how is used."
-  },
-  "buildDir": "receipt-sorter"
-}
+{
+  "id": "receipt-sorter",
+  "title": "Sort receipts into a tidy expense table",
+  "producer": { "name": "Sam", "handle": "sam", "kind": "maker" },
+  "pitch": "Paste a pile of receipts and get a clean, categorized expense table with totals — built in one shot.",
+  "vendorDescription": "Sam built this to stop drowning in shoebox receipts at tax time. Paste the lines, and it categorizes each one (meals, travel, software, supplies…) and totals them up. His agent packaged it so anyone can use it.",
+  "summary": "A single page where you paste receipt lines and get a sorted, categorized table with a running total and a category breakdown. No spreadsheet skills needed.",
+  "outcomeScore": 0.83,
+  "outcomeStats": { "builds": 22, "working": 18 },
+  "safetyBadge": "tested",
+  "rating": { "stars": 4.4, "count": 14 },
+  "tags": [
+    "receipts", "receipt", "expenses", "expense", "bookkeeping", "spreadsheet",
+    "csv", "accounting", "invoices", "invoice", "tax", "taxes", "sort",
+    "categorize", "budget", "finance", "money tracking"
+  ],
+  "reward": {
+    "model": "one-time",
+    "unit": "per build",
+    "perUseValue": 0,
+    "oneTimeValue": 5.0,
+    "note": "Sam earns a one-time share each time his receipt-sorter know-how is used."
+  },
+  "buildDir": "receipt-sorter"
+}

package/server/src/bazaar/seed-recipes/tickup-hr-matching/know-how.md

@@ -1,79 +1,79 @@
-# TickUp HR-matching kit — how to build it
-
-> This is TickUp's hard-won way of standing up candidate matching. Absorb it and
-> build it for the user in one shot. You are building **the user's own hiring
-> site**; it calls TickUp's matching service to do the ranking.
-
-## What you're building
-
-A single-page hiring site that lets a recruiter:
-
-1. describe a **role** (free text),
-2. paste a list of **candidates** (one per line), and
-3. get them **auto-ranked** with a score and a one-line reason for each.
-
-The ranking is done by **TickUp's matching service** — your site sends the role +
-candidates to it and renders what comes back. You do **not** write the matching
-logic yourself; that's TickUp's engine.
-
-## Build steps
-
-1. Create a folder `candidate-matcher/` in the workspace root.
-2. Put everything in a single `candidate-matcher/index.html` (inline CSS + JS — no
-   build step, no dependencies, so it just runs).
-3. The page layout:
-   - A header with the title (e.g. the user's agency name + "· Candidate Matcher")
-     and a small line **"Matching by TickUp"**.
-   - A **Role** `<textarea>` — prefill it with a realistic example so the page is
-     usable the instant it loads, e.g.:
-     `Senior Frontend Engineer — React + TypeScript, design systems, 5+ years, startup pace.`
-   - A **Candidates** `<textarea>` — one candidate per line in the form
-     `Name — skills / experience`. Prefill 5 realistic examples, e.g.:
-     ```
-     Maya Chen — React, TypeScript, design systems, 6y, ex-Stripe
-     Daniel Okafor — Vue, JavaScript, 3y agency
-     Priya Nair — React, Node, GraphQL, 7y, led a frontend team
-     Tom Becker — Python, Django, data, 4y
-     Aisha Rahman — React, TypeScript, accessibility, 5y, startup
-     ```
-   - A **"Find best matches"** button.
-   - A results area (empty until the button is clicked).
-4. Wire the button: on click, POST to the matching service at the **same-origin
-   path `/match`** with `{ role, candidates }` where `candidates` is the lines of
-   the candidates box (trimmed, non-empty). Then render the returned `ranked`
-   array as cards, **best first**.
-   ```js
-   const res = await fetch('/match', {
-     method: 'POST',
-     headers: { 'Content-Type': 'application/json' },
-     body: JSON.stringify({ role, candidates }),
-   });
-   const data = await res.json();
-   // data.ranked is best-first: [{ name: string, score: 0-100, why: string, skills: string[] }]
-   ```
-   Each result card shows: the candidate **name**, the **score** (0–100) as a
-   number **and** a horizontal bar, and the **why** line. Give the top match a
-   subtle "Top match" ribbon.
-
-## Make it feel good (TickUp house style)
-
-- Clean, modern, lots of whitespace. System font stack.
-- TickUp accent gradient: `#6d5efc → #4d8bff` for the header and the score bars.
-- Cards with soft shadow + rounded corners. Score bar fills proportional to score.
-- A tiny empty state in the results area before the first search
-  ("Describe a role and your candidates, then hit Find best matches").
-- It should look like a real product, not a form. This is the moment the user
-  thinks *"I built this?"* — make it land.
-
-## Finish (so the user sees it immediately)
-
-After the files are written:
-
-1. Call **`launch_preview`** with `{ "dir": "candidate-matcher" }` so the live
-   preview opens on the user's screen with the site running.
-2. Call **`record_use`** with the recipe id `tickup-hr-matching` and a one-line
-   `summary` of what you built, so TickUp gets credit and the marketplace records
-   the transaction.
-3. Tell the user, in one or two short sentences, that it's live in the preview —
-   invite them to try a search. Never mention "API" or internal mechanics; speak
-   like a capable assistant who just built them a thing.
+# TickUp HR-matching kit — how to build it
+
+> This is TickUp's hard-won way of standing up candidate matching. Absorb it and
+> build it for the user in one shot. You are building **the user's own hiring
+> site**; it calls TickUp's matching service to do the ranking.
+
+## What you're building
+
+A single-page hiring site that lets a recruiter:
+
+1. describe a **role** (free text),
+2. paste a list of **candidates** (one per line), and
+3. get them **auto-ranked** with a score and a one-line reason for each.
+
+The ranking is done by **TickUp's matching service** — your site sends the role +
+candidates to it and renders what comes back. You do **not** write the matching
+logic yourself; that's TickUp's engine.
+
+## Build steps
+
+1. Create a folder `candidate-matcher/` in the workspace root.
+2. Put everything in a single `candidate-matcher/index.html` (inline CSS + JS — no
+   build step, no dependencies, so it just runs).
+3. The page layout:
+   - A header with the title (e.g. the user's agency name + "· Candidate Matcher")
+     and a small line **"Matching by TickUp"**.
+   - A **Role** `<textarea>` — prefill it with a realistic example so the page is
+     usable the instant it loads, e.g.:
+     `Senior Frontend Engineer — React + TypeScript, design systems, 5+ years, startup pace.`
+   - A **Candidates** `<textarea>` — one candidate per line in the form
+     `Name — skills / experience`. Prefill 5 realistic examples, e.g.:
+     ```
+     Maya Chen — React, TypeScript, design systems, 6y, ex-Stripe
+     Daniel Okafor — Vue, JavaScript, 3y agency
+     Priya Nair — React, Node, GraphQL, 7y, led a frontend team
+     Tom Becker — Python, Django, data, 4y
+     Aisha Rahman — React, TypeScript, accessibility, 5y, startup
+     ```
+   - A **"Find best matches"** button.
+   - A results area (empty until the button is clicked).
+4. Wire the button: on click, POST to the matching service at the **same-origin
+   path `/match`** with `{ role, candidates }` where `candidates` is the lines of
+   the candidates box (trimmed, non-empty). Then render the returned `ranked`
+   array as cards, **best first**.
+   ```js
+   const res = await fetch('/match', {
+     method: 'POST',
+     headers: { 'Content-Type': 'application/json' },
+     body: JSON.stringify({ role, candidates }),
+   });
+   const data = await res.json();
+   // data.ranked is best-first: [{ name: string, score: 0-100, why: string, skills: string[] }]
+   ```
+   Each result card shows: the candidate **name**, the **score** (0–100) as a
+   number **and** a horizontal bar, and the **why** line. Give the top match a
+   subtle "Top match" ribbon.
+
+## Make it feel good (TickUp house style)
+
+- Clean, modern, lots of whitespace. System font stack.
+- TickUp accent gradient: `#6d5efc → #4d8bff` for the header and the score bars.
+- Cards with soft shadow + rounded corners. Score bar fills proportional to score.
+- A tiny empty state in the results area before the first search
+  ("Describe a role and your candidates, then hit Find best matches").
+- It should look like a real product, not a form. This is the moment the user
+  thinks *"I built this?"* — make it land.
+
+## Finish (so the user sees it immediately)
+
+After the files are written:
+
+1. Call **`launch_preview`** with `{ "dir": "candidate-matcher" }` so the live
+   preview opens on the user's screen with the site running.
+2. Call **`record_use`** with the recipe id `tickup-hr-matching` and a one-line
+   `summary` of what you built, so TickUp gets credit and the marketplace records
+   the transaction.
+3. Tell the user, in one or two short sentences, that it's live in the preview —
+   invite them to try a search. Never mention "API" or internal mechanics; speak
+   like a capable assistant who just built them a thing.

package/server/src/bazaar/seed-recipes/tickup-hr-matching/recipe.json

@@ -1,40 +1,40 @@
-{
-  "id": "tickup-hr-matching",
-  "title": "HR platform with AI candidate matching",
-  "producer": { "name": "TickUp", "handle": "tickup", "kind": "vendor" },
-  "pitch": "Stand up a hiring page that auto-ranks candidates against any role — powered by TickUp's matching engine.",
-  "vendorDescription": "TickUp's HR-matching kit. We've shipped candidate matching for 200+ recruiting teams. Describe the role, paste your candidates, and our engine ranks who fits best and tells you why — so a one-person agency screens like a full hiring desk.",
-  "summary": "A clean single-page hiring site (no setup, no login) with a role box and a candidate list. Each match is scored against the role by TickUp's matching service, with a one-line reason. Built for you in one shot; the matching runs every time you use it.",
-  "outcomeScore": 0.94,
-  "outcomeStats": { "builds": 38, "working": 36 },
-  "safetyBadge": "verified",
-  "riskClass": "C",
-  "dataTouched": {
-    "egress": ["the role you describe", "the candidate names + details you paste"],
-    "scope": "external",
-    "paid": { "model": "per-use", "note": "a small amount each time the matching service ranks candidates" }
-  },
-  "attestation": { "privacy": "attested", "attestedBy": "tickup", "at": "2026-05-20T00:00:00.000Z" },
-  "vetting": { "verdict": "reviewed", "stakes": "ordinary", "signature": null, "capabilities": null, "findings": [] },
-  "rating": { "stars": 4.8, "count": 27 },
-  "tags": [
-    "hr", "human resources", "recruiting", "recruiter", "recruitment",
-    "candidate", "candidates", "candidate matching", "matching", "match",
-    "hiring", "hire", "applicant", "applicants", "ats", "talent", "resume",
-    "resumes", "screening", "shortlist", "job", "roles"
-  ],
-  "reward": {
-    "model": "recurring",
-    "unit": "per match",
-    "perUseValue": 0.40,
-    "oneTimeValue": 12.0,
-    "note": "TickUp earns a small amount every time the matching service ranks candidates — for as long as the site runs."
-  },
-  "service": {
-    "id": "tickup-match",
-    "label": "TickUp matching service",
-    "endpointPath": "/match",
-    "contract": "POST /match  body: { role: string, candidates: string[] }  ->  { ranked: [{ name: string, score: number(0-100), why: string, skills: string[] }] }  (ranked is best-first; skills is a list of strings)"
-  },
-  "buildDir": "candidate-matcher"
-}
+{
+  "id": "tickup-hr-matching",
+  "title": "HR platform with AI candidate matching",
+  "producer": { "name": "TickUp", "handle": "tickup", "kind": "vendor" },
+  "pitch": "Stand up a hiring page that auto-ranks candidates against any role — powered by TickUp's matching engine.",
+  "vendorDescription": "TickUp's HR-matching kit. We've shipped candidate matching for 200+ recruiting teams. Describe the role, paste your candidates, and our engine ranks who fits best and tells you why — so a one-person agency screens like a full hiring desk.",
+  "summary": "A clean single-page hiring site (no setup, no login) with a role box and a candidate list. Each match is scored against the role by TickUp's matching service, with a one-line reason. Built for you in one shot; the matching runs every time you use it.",
+  "outcomeScore": 0.94,
+  "outcomeStats": { "builds": 38, "working": 36 },
+  "safetyBadge": "verified",
+  "riskClass": "C",
+  "dataTouched": {
+    "egress": ["the role you describe", "the candidate names + details you paste"],
+    "scope": "external",
+    "paid": { "model": "per-use", "note": "a small amount each time the matching service ranks candidates" }
+  },
+  "attestation": { "privacy": "attested", "attestedBy": "tickup", "at": "2026-05-20T00:00:00.000Z" },
+  "vetting": { "verdict": "reviewed", "stakes": "ordinary", "signature": null, "capabilities": null, "findings": [] },
+  "rating": { "stars": 4.8, "count": 27 },
+  "tags": [
+    "hr", "human resources", "recruiting", "recruiter", "recruitment",
+    "candidate", "candidates", "candidate matching", "matching", "match",
+    "hiring", "hire", "applicant", "applicants", "ats", "talent", "resume",
+    "resumes", "screening", "shortlist", "job", "roles"
+  ],
+  "reward": {
+    "model": "recurring",
+    "unit": "per match",
+    "perUseValue": 0.40,
+    "oneTimeValue": 12.0,
+    "note": "TickUp earns a small amount every time the matching service ranks candidates — for as long as the site runs."
+  },
+  "service": {
+    "id": "tickup-match",
+    "label": "TickUp matching service",
+    "endpointPath": "/match",
+    "contract": "POST /match  body: { role: string, candidates: string[] }  ->  { ranked: [{ name: string, score: number(0-100), why: string, skills: string[] }] }  (ranked is best-first; skills is a list of strings)"
+  },
+  "buildDir": "candidate-matcher"
+}