create-ailk 0.24.0 → 0.26.0

package/templates/database/content/schema.prisma

@@ -1,339 +0,0 @@
-// content namespace — chat + artifact substrate (AgentSession, ConversationEvent,
-// SessionReadReceipt, Artifact, ArtifactVersion, Asset)
-//
-// Backs the event-sourced conversation transport + artifact persistence in
-// docs/research/ploy-capture/BACKEND-REQUIREMENTS.md (§1 transport R-T1..R-T7,
-// §2 event envelope, §3 endpoints). Workspaces own all domain content, so every
-// table here carries a non-null `workspaceId` tenant scope.
-//
-// Per ADR 0009 invariant 1: workspaceId / userId are plain String stable IDs —
-// NO @relation into the auth namespace (Workspace/User live in database/auth/).
-// Relations WITHIN this namespace (event → session, version → artifact) are
-// real FKs. Cross-namespace assembly (e.g. tenant guard resolving a session's
-// workspace) routes through apps/api/src/services/ (invariant 4).
-//
-// Generator + datasource blocks live in database/schema.prisma (the root schema
-// file). This file holds only model definitions for the content namespace.
-
-/// AgentSession — one agent conversation ("session"/captured "ploy") within a
-/// workspace. lastSeq is the append watermark for the event log (R-T1).
-model AgentSession {
-  id            String    @id @default(dbgenerated("('agsess_'::text || (uuidv7())::text)")) @db.Text
-  workspaceId   String    @map("workspace_id")
-  title         String?
-  status        String    @default("idle")
-  lastSeq       Int       @default(0) @map("last_seq")
-  lastMessageAt DateTime? @map("last_message_at")
-  draftMessage  String?   @map("draft_message")
-  createdAt     DateTime  @default(now()) @map("created_at")
-  updatedAt     DateTime  @updatedAt @map("updated_at")
-
-  events       ConversationEvent[]
-  artifacts    Artifact[]
-  readReceipts SessionReadReceipt[]
-
-  @@index([workspaceId, lastMessageAt(sort: Desc)])
-  @@map("agent_sessions")
-}
-
-/// ConversationEvent — append-only, seq-ordered event log entry (R-T1/R-T4).
-/// Envelope: { agentId, seq, type, turnId, payload, createdAt } (§2).
-/// workspaceId is denormalized so the scope layer filters events without a
-/// join through agent_sessions.
-model ConversationEvent {
-  id          String   @id @default(dbgenerated("('convev_'::text || (uuidv7())::text)")) @db.Text
-  sessionId   String   @map("session_id")
-  workspaceId String   @map("workspace_id")
-  agentId     String   @map("agent_id")
-  seq         Int
-  type        String
-  turnId      String?  @map("turn_id")
-  payload     Json
-  createdAt   DateTime @default(now()) @map("created_at")
-
-  session AgentSession @relation(fields: [sessionId], references: [id], onDelete: Cascade)
-
-  @@unique([sessionId, seq])
-  @@index([workspaceId])
-  @@map("conversation_events")
-}
-
-/// SessionReadReceipt — per-user read position for a session (R-T7 mark-read;
-/// drives unread badges). userId is a stable auth-namespace ID — no FK.
-model SessionReadReceipt {
-  id          String   @id @default(dbgenerated("('receipt_'::text || (uuidv7())::text)")) @db.Text
-  sessionId   String   @map("session_id")
-  workspaceId String   @map("workspace_id")
-  userId      String   @map("user_id")
-  lastReadSeq Int      @default(0) @map("last_read_seq")
-  updatedAt   DateTime @updatedAt @map("updated_at")
-
-  session AgentSession @relation(fields: [sessionId], references: [id], onDelete: Cascade)
-
-  @@unique([sessionId, userId])
-  @@index([workspaceId])
-  @@map("session_read_receipts")
-}
-
-/// Artifact — a piece of the WORKSPACE's versioned content (#3846, generalized
-/// by #5800 / roadmap D1). Originally "a session's produced output"; a session
-/// is now PROVENANCE, not ownership — `sessionId` is optional and `SetNull`, so
-/// deleting the conversation that produced a page leaves the page standing.
-///
-/// `contentType` is the discriminator the content store reads: `text/page` is
-/// what the editor writes, `text/document` the legacy chat artifact. A page's
-/// public identity is `(workspaceId, contentType, locale, slug)`; `slug` stays
-/// NULL until publish, and NULLs never collide in a Postgres unique index, so a
-/// workspace may hold any number of unpublished drafts.
-///
-/// `publishedVersionId` is a plain pointer at the ArtifactVersion the public
-/// read serves — deliberately NOT a relation (a FK back into `versions` would
-/// make the delete order of an artifact's own history circular), and
-/// deliberately NOT `ArtifactVersion.isCurrent`, which is the DRAFT TIP and is
-/// never the publish mechanism. Saving a draft moves `isCurrent`; only publish
-/// moves this pointer.
-///
-/// `type` is the LEGACY discriminator. It predates `contentType` and is still
-/// read by apps/api/src/routes/workspaces/sessions.ts (the session-artifacts
-/// route, a hard-floor surface), so #5800 added `contentType` beside it and
-/// backfilled it from `type` rather than renaming the column out from under a
-/// live consumer. New code reads `contentType`; retiring `type` belongs to the
-/// card that moves that route.
-model Artifact {
-  id                 String   @id @default(dbgenerated("('artif_'::text || (uuidv7())::text)")) @db.Text
-  sessionId          String?  @map("session_id")
-  workspaceId        String   @map("workspace_id")
-  type               String   @default("text/document")
-  contentType        String   @default("text/document") @map("content_type")
-  locale             String   @default("en")
-  slug               String?
-  title              String
-  publishedVersionId String?  @map("published_version_id")
-  createdAt          DateTime @default(now()) @map("created_at")
-  updatedAt          DateTime @updatedAt @map("updated_at")
-
-  session  AgentSession?     @relation(fields: [sessionId], references: [id], onDelete: SetNull)
-  versions ArtifactVersion[]
-
-  @@unique([workspaceId, contentType, locale, slug])
-  @@index([sessionId])
-  @@index([workspaceId])
-  @@index([workspaceId, contentType, updatedAt])
-  @@map("artifacts")
-}
-
-/// ArtifactVersion — auto-saved version history; exactly one isCurrent per
-/// artifact (enforced at the service layer on save/restore).
-model ArtifactVersion {
-  id          String   @id @default(dbgenerated("('artiv_'::text || (uuidv7())::text)")) @db.Text
-  artifactId  String   @map("artifact_id")
-  workspaceId String   @map("workspace_id")
-  content     Json
-  isCurrent   Boolean  @default(true) @map("is_current")
-  savedAt     DateTime @default(now()) @map("saved_at")
-
-  artifact Artifact @relation(fields: [artifactId], references: [id], onDelete: Cascade)
-
-  @@index([artifactId, savedAt(sort: Desc)])
-  @@index([workspaceId])
-  @@map("artifact_versions")
-}
-
-/// Asset — a workspace's uploaded binary (#5800 / roadmap D7), following the
-/// `DeliverableAsset` precedent in the inbox namespace: the bytes live in the
-/// row, not in object storage. That precedent was deliberate — no new
-/// infrastructure — and only the resolver changes if blob storage arrives later.
-///
-/// `workspaceId` is a plain String stable id with no @relation (ADR 0009
-/// invariant 1), and `(workspaceId, key)` is the addressable identity. Ids are
-/// UUIDv7 (ADR 0031), so a re-upload is a NEW id and a served asset can be
-/// cached immutably. The upload route itself is #5802's scope, not this model's.
-///
-/// Since #6310: this is also the store a magnet's `deliverables.assets[].assetKey`
-/// resolves against FIRST (by `(workspaceId, key)`), ahead of the legacy
-/// `DeliverableAsset` fallback (database/inbox/schema.prisma) — read through
-/// the scoped boundary in apps/api/src/lib/deliverable-asset-store.ts, never
-/// a raw query.
-model Asset {
-  id          String   @id @default(dbgenerated("('asset_'::text || (uuidv7())::text)")) @db.Text
-  workspaceId String   @map("workspace_id")
-  /// The caller-chosen name an artifact's content references the asset by.
-  key         String
-  /// Download filename (Content-Disposition). Stored RAW; sanitize at SERVE
-  /// time, exactly as the DeliverableAsset download route does.
-  filename    String
-  contentType String   @map("content_type")
-  bytes       Bytes
-  size        Int
-  /// Owner-authored display name, shown above the filename in the lightbox
-  /// (#6092, S4/D10). NULL means the owner has not written one — distinct from
-  /// an empty string, which means they cleared it. Never backfilled from
-  /// `filename`: the two are different facts (demo.html:782 renders both).
-  title       String?
-  /// Owner-authored longer description. Same NULL-vs-empty contract as `title`.
-  description String?
-  /// Owner-controlled tag SLUGS (`ad-creative`, `workspace-memory`, …), never
-  /// the human labels — the label is presentation, resolved by the surface from
-  /// its own vocabulary (demo.html:358 `ATAGS`, :794 the Docs set). Free-form
-  /// by design: the asset vocabulary and the document vocabulary (D8/D9) ride
-  /// this one column, and the "fixed set" of D10 is a UI affordance, not a
-  /// database constraint (#6092, D2 of the spec).
-  tags        String[] @default([])
-  createdAt   DateTime @default(now()) @map("created_at")
-
-  @@unique([workspaceId, key])
-  @@index([workspaceId])
-  @@map("assets")
-}
-
-// ============================================================================
-// Usage-billing metering (FEAT-047 P1.S1, #3709 — Epic #3704)
-//
-// The metering event + its org-level aggregates. Per ADR 0009 D2 (roadmap §4),
-// the metering event + UsagePeriod + UsageBillingReport live in `content`;
-// balances/plans (S2) live in auth/config. organizationId/workspaceId/userId
-// are plain String stable-ids — no @relation into auth (ADR 0009 invariant 1).
-// Field roster ported from docs/research/wt-billing-capture/schema.md, modeled
-// on WT's TraceLog billing columns (spec D1), with workspaceId/userId added to
-// the event grain (spec D2). Cross-namespace assembly (e.g. resolving an
-// event's owning Workspace) routes through apps/api/src/services/.
-// ============================================================================
-
-/// ModelTier — the pricing tier at event time. BASE is unlimited/free-ish;
-/// PREMIUM/FRONTIER consume credits. Defined here (S1, the dependency root)
-/// per spec OQ-1 — S2's LlmModel references the same enum through the merged
-/// prismaSchemaFolder (one logical schema; an enum reference needs no
-/// @relation, so this is not a cross-namespace FK).
-enum ModelTier {
-  BASE
-  PREMIUM
-  FRONTIER
-}
-
-/// UsageBillingStatus — UsageBillingReport lifecycle: PENDING → REPORTED →
-/// INVOICED → PAID, or FAILED.
-enum UsageBillingStatus {
-  PENDING
-  REPORTED
-  INVOICED
-  PAID
-  FAILED
-}
-
-/// UsageEvent — one row per billable AI call (the metering event; modeled on
-/// WT's TraceLog billing columns, spec D1). org+workspace+user grain (spec
-/// D2); all three scope ids are plain String stable-ids — no cross-namespace
-/// @relation (ADR 0009 invariant 1, spec D3). The three attribution portion
-/// columns are the load-bearing billing split; only onDemandPortionCents is
-/// ever reported to Stripe (P4, spec D4). completionStatus 'success' rows
-/// drive billing — aggregation (P2) filters on it.
-model UsageEvent {
-  id             String @id @default(dbgenerated("('usagev_'::text || (uuidv7())::text)")) @db.Text
-  organizationId String @map("organization_id")
-  workspaceId    String @map("workspace_id")
-  userId         String @map("user_id")
-
-  provider String
-  model    String
-
-  // Cache-aware token breakdown.
-  inputTokensCacheWrite   Int @map("input_tokens_cache_write")
-  inputTokensNoCacheWrite Int @map("input_tokens_no_cache_write")
-  cacheReadTokens         Int @map("cache_read_tokens")
-  outputTokens            Int @map("output_tokens")
-  thinkingTokens          Int @map("thinking_tokens")
-  totalTokens             Int @map("total_tokens")
-
-  providerCostUsd Decimal @map("provider_cost_usd") @db.Decimal(10, 6)
-  billedCostUsd   Decimal @map("billed_cost_usd") @db.Decimal(10, 6)
-  markupPercent   Decimal @map("markup_percent") @db.Decimal(5, 2)
-
-  modelTier    ModelTier @default(BASE) @map("model_tier")
-  wasAutoModel Boolean   @map("was_auto_model")
-
-  // Attribution split — billedCostUsd apportioned across the three buckets;
-  // only onDemandPortionCents is ever Stripe-metered (P4, spec D4).
-  includedPortionCents      Int @default(0) @map("included_portion_cents")
-  creditBalancePortionCents Int @default(0) @map("credit_balance_portion_cents")
-  onDemandPortionCents      Int @default(0) @map("on_demand_portion_cents")
-
-  completionStatus String   @map("completion_status")
-  createdAt        DateTime @default(now()) @map("created_at")
-
-  @@index([organizationId, createdAt])
-  @@index([workspaceId, createdAt])
-  @@index([userId, createdAt])
-  @@index([provider, model])
-  @@index([modelTier, wasAutoModel])
-  @@map("usage_events")
-}
-
-/// UsagePeriod — one row per (organizationId, periodStart); the org-scoped
-/// spend/tier rollup the P2 write path upserts as UsageEvent rows land.
-/// Carries the event-grain roll-up support for the Org → Workspace → User
-/// aggregation (spec D2) — whether this model itself gains per-workspace
-/// sub-rows is a P2 decision, not a P1 schema requirement (spec OQ-2).
-model UsagePeriod {
-  id             String @id @default(dbgenerated("('usagper_'::text || (uuidv7())::text)")) @db.Text
-  organizationId String @map("organization_id")
-
-  periodStart DateTime @map("period_start")
-  periodEnd   DateTime @map("period_end")
-
-  tokensConsumed         BigInt @default(0) @map("tokens_consumed")
-  baseTokensConsumed     BigInt @default(0) @map("base_tokens_consumed")
-  premiumTokensConsumed  BigInt @default(0) @map("premium_tokens_consumed")
-  frontierTokensConsumed BigInt @default(0) @map("frontier_tokens_consumed")
-
-  usageSpendCents Int @default(0) @map("usage_spend_cents")
-
-  @@unique([organizationId, periodStart])
-  @@index([baseTokensConsumed, premiumTokensConsumed, frontierTokensConsumed], map: "usage_periods_tier_tracking_idx")
-  @@map("usage_periods")
-}
-
-/// UsageBillingReport — one per (organizationId, periodStart, periodEnd); the
-/// Stripe-reporting unit rolled up from UsageEvent by P2 aggregation. Only
-/// onDemandCents is ever reported to Stripe (P4, spec D4) — includedCents/
-/// creditBalanceCents are informational attribution, never metered.
-model UsageBillingReport {
-  id             String @id @default(dbgenerated("('usagrept_'::text || (uuidv7())::text)")) @db.Text
-  organizationId String @map("organization_id")
-
-  periodStart DateTime @map("period_start")
-  periodEnd   DateTime @map("period_end")
-
-  // AGGREGATE precision (#3738 H2) — these hold a MONTH of events, not one
-  // event, so they must NOT reuse UsageEvent's per-event widths. At the
-  // original Decimal(10,6)/Int, an org whose month crossed $9,999.999999 (or
-  // 2.15B tokens) overflowed the column, the upsert threw, and the report was
-  // never written on ANY subsequent run — silently stalling revenue for the
-  // largest customers, worsening monotonically. Decimal(20,6) ≈ $1e14 and int8
-  // give headroom far above the service's own MAX_TOTAL_USD / token caps, so
-  // the service's loud `aggregate_overflow` assertion is always the gate and a
-  // silent DB overflow is unreachable. See usage-aggregation.ts § Bounds.
-  totalProviderCost Decimal @map("total_provider_cost") @db.Decimal(20, 6)
-  totalMarkupAmount Decimal @map("total_markup_amount") @db.Decimal(20, 6)
-  totalBilledAmount Decimal @map("total_billed_amount") @db.Decimal(20, 6)
-
-  totalTokens BigInt @map("total_tokens")
-  eventCount  Int    @map("event_count")
-
-  // Attribution split — only onDemandCents is ever Stripe-metered (P4, spec D4).
-  includedCents      Int @default(0) @map("included_cents")
-  creditBalanceCents Int @default(0) @map("credit_balance_cents")
-  onDemandCents      Int @default(0) @map("on_demand_cents")
-
-  stripeUsageRecordId String?   @map("stripe_usage_record_id")
-  reportedToStripeAt  DateTime? @map("reported_to_stripe_at")
-  stripeInvoiceId     String?   @map("stripe_invoice_id")
-
-  status       UsageBillingStatus @default(PENDING)
-  errorMessage String?            @map("error_message")
-
-  @@unique([organizationId, periodStart, periodEnd], map: "usage_billing_reports_period_key")
-  @@index([organizationId, status])
-  @@index([status])
-  @@index([periodStart])
-  @@map("usage_billing_reports")
-}

package/templates/database/eslint.config.mjs

@@ -1,69 +0,0 @@
-// Self-contained ESLint flat config for this scaffolded package.
-//
-// It deliberately does NOT depend on @working-theory/eslint-config — that
-// package is internal to the AI Launch Kit monorepo and is not published, so
-// it cannot be a dependency of a scaffolded starter. Everything below comes
-// from public npm packages already pinned as devDependencies (see
-// package.json): @eslint/js, globals and typescript-eslint.
-//
-// Source file name (#5556): this file is checked in as `_eslint.config.mjs`,
-// not `eslint.config.mjs` — build-templates.mjs renames it at snapshot time
-// (renameScaffoldLintConfigs()). A file literally named `eslint.config.mjs`
-// anywhere under this monorepo (even one this repo's own root eslint.config.ts
-// lists in its `ignores`) is auto-discovered by ESLint's flat-config nested
-// resolution as a competing config root, which breaks the monorepo's own
-// lint runs (verified live: typescript-eslint's "multiple candidate
-// TSConfigRootDirs" parser error across unrelated packages/create-ailk
-// files). The underscore prefix keeps it invisible to that discovery while
-// it lives in this checkout; only the snapshot in templates/ — which ships
-// to the customer, not this repo — gets the real filename.
-import js from "@eslint/js";
-import globals from "globals";
-import tseslint from "typescript-eslint";
-
-export default tseslint.config(
-  {
-    ignores: [
-      "**/.next/**",
-      "**/dist/**",
-      "**/generated/**",
-      "**/node_modules/**",
-    ],
-  },
-  js.configs.recommended,
-  ...tseslint.configs.recommended,
-  {
-    languageOptions: {
-      globals: {
-        ...globals.node,
-        ...globals.browser,
-        ...globals.jest,
-      },
-      // Explicit, self-contained root — this scaffold config is never meant
-      // to combine with any sibling scaffold package's config (each ships
-      // standalone), and leaving it unset makes typescript-eslint's
-      // candidate-root disambiguation ambiguous the moment more than one
-      // scaffold package's config resolves in the same ESLint process (e.g.
-      // this monorepo's own `templates/` build, where all four exist
-      // side by side; a real customer scaffold never has that problem,
-      // since it only ever ships and lints ONE of these four at a time).
-      parserOptions: {
-        tsconfigRootDir: import.meta.dirname,
-      },
-    },
-    rules: {
-      // Downgraded rather than off, so both stay visible without failing a
-      // fresh scaffold's lint:
-      //   - unused-vars: most of the source follows the underscore-prefix
-      //     convention for intentionally-unused bindings, which this rule's
-      //     default options don't recognize; a handful of test fixtures also
-      //     carry genuinely-unused locals this minimal config doesn't try to
-      //     triage file-by-file.
-      //   - require-imports: CommonJS require() is the correct form in Jest
-      //     config/mock files and in a few test-only dynamic re-require
-      //     patterns.
-      "@typescript-eslint/no-unused-vars": "warn",
-      "@typescript-eslint/no-require-imports": "warn",
-    },
-  },
-);

package/templates/database/flows/listing-diagnostic.ts

@@ -1,182 +0,0 @@
-/**
- * @file listing-diagnostic.ts
- * @description The ONE scoring RULE every project-listing diagnostic shares
- * (#5001, reworked by #5036 D4) — the template's Q3–Q6 resolved by option
- * VALUE, never by option position.
- *
- * The mechanism (#5036 D4, "scoring by value, not position"): the generated
- * flow emits each scored option under the FOUNDER'S OWN `option.value`, and
- * the register's `optionWeights` map is keyed on those same values. Q3/Q4 are
- * founder-authored, so their weights map is built PER LISTING from that
- * listing's own options — the WEIGHT still comes from the founder's declared
- * order via `listingOptionPoints(index, arity)`, but it is stored against the
- * value rather than an index. Q5/Q6 carry fixed values
- * (`projectListingQuestionsSchema`, #4998), so their weights are declared once
- * here, shared by every listing.
- *
- * What that buys, and why the old `q{n}:{i}of{k}` encoding had to go: meaning
- * now travels with the value. A register may reorder or insert options and an
- * already-stored answer keeps scoring what it always meant, so the subset a
- * surface renders no longer has to be a prefix of the register's list — which
- * is what unblocks the shared team-composition value set (#5036 D3). It also
- * dissolves the "shared register needs a shared value universe" problem
- * (docs/lessons/2026-09-07-…): the generated experiment's `questionSet` now
- * declares the listing's OWN options, so
- * `waitlistExperimentConfigSchema`'s "every weights key must be a declared
- * option" cross-validation is satisfied by construction rather than by
- * declaring a finite universe of positional tokens.
- *
- * What is shared is therefore the RULE and the shape — same point names, same
- * `total` sum, same tier floors, same 0–12 range — not a single frozen
- * constant. Two listings' registers differ only in the Q3/Q4 KEYS, which are
- * the founders' own option values.
- *
- * Q5 runs STRONGEST-FIRST, deliberately. `projectListingQuestionsSchema` pins
- * Q5's values as `urgent | planning | exploring`, which is urgency descending,
- * while the positional rule scores index 0 lowest — so the old positional
- * encoding scored `urgent` 0 and `exploring` 3, backwards, a standing defect
- * recorded in docs/lessons/2026-09-07-q5-fixed-order-is-strongest-first.md.
- * Scoring by value is exactly the mechanism that resolves it: the weights
- * below name `urgent` 3 and `exploring` 0 explicitly, with no reordering of
- * the founder's rendered options and no per-question special case hidden
- * inside a positional formula. That lesson's open question is closed here.
- * Q6 (`low → critical`) is genuinely weakest-first and keeps 0 → 3.
- *
- * Q1 (contact), Q2 (segment), Q7 (free text) and the extras carry no points —
- * they are absent from `points` entirely, so they contribute 0 by
- * construction rather than by a zero weight that could drift.
- *
- * This module is data + the pure functions that generate it — it imports only
- * TYPES from `@working-theory/validation` and introduces no dependency from
- * `database/` toward `apps/*` (architecture.yaml's import boundary), exactly
- * like `presets.ts` beside it. The rule lives here and only here; the
- * projection (`apps/api/src/services/project-listing-flow.ts`) calls
- * `buildListingDiagnosticScoring` rather than re-deriving weights, so the
- * register and the flow can never disagree about what an answer is worth.
- */
-
-import type {
-  ProjectListingQuestions,
-  WaitlistScoring,
-} from "@working-theory/validation";
-
-/** The four scored template questions, in template order. */
-export const LISTING_DIAGNOSTIC_SCORED_QUESTIONS = ["q3", "q4", "q5", "q6"] as const;
-export type ListingDiagnosticScoredQuestion =
-  (typeof LISTING_DIAGNOSTIC_SCORED_QUESTIONS)[number];
-
-/** The highest score any one question can contribute. */
-export const LISTING_DIAGNOSTIC_MAX_QUESTION_POINTS = 3;
-
-/**
- * The weight of option `index` (zero-based) of `arity` options —
- * `round(3·i/(k−1))`, so the founder's first option always scores 0 and their
- * last always scores 3, whatever the arity. This is still how a
- * founder-authored question's weights are DERIVED (the founder orders their
- * options weakest→strongest); what changed in #5036 D4 is where the result is
- * STORED — against the option's value, not its index.
- *
- * A single-option question (`arity <= 1`) has no spread to score and yields 0;
- * the template never produces one, and this guard exists so the expression can
- * never divide by zero.
- */
-export function listingOptionPoints(index: number, arity: number): number {
-  if (arity <= 1) return 0;
-  return Math.round((LISTING_DIAGNOSTIC_MAX_QUESTION_POINTS * index) / (arity - 1));
-}
-
-/**
- * `optionWeights` for one founder-authored question (Q3/Q4), keyed by the
- * founder's own option values and weighted by their declared order.
- */
-export function listingDiagnosticOptionWeights(
-  options: readonly { value: string }[],
-): Record<string, number> {
-  const weights: Record<string, number> = {};
-  options.forEach((option, index) => {
-    weights[option.value] = listingOptionPoints(index, options.length);
-  });
-  return weights;
-}
-
-/**
- * Q5's fixed urgency weights — STRONGEST FIRST, against the positional rule
- * and deliberately so (see the file header). `urgent` is the strongest buying
- * signal the question can carry and scores 3; `exploring` is the weakest and
- * scores 0. The three weights are the same multiset a 3-option positional
- * question produces (`{0, 2, 3}`), so the 0–12 total range is unchanged.
- */
-export const LISTING_DIAGNOSTIC_Q5_WEIGHTS: Readonly<Record<string, number>> = {
-  urgent: 3,
-  planning: 2,
-  exploring: 0,
-};
-
-/**
- * Q6's fixed band weights — weakest first, matching the schema's own
- * `low → critical` low→high ordering, so these are exactly what the positional
- * rule produced for a 4-option question.
- */
-export const LISTING_DIAGNOSTIC_Q6_WEIGHTS: Readonly<Record<string, number>> = {
-  low: 0,
-  medium: 1,
-  high: 2,
-  critical: 3,
-};
-
-/** The four tier keys, strongest first — the order `tiers` is evaluated in. */
-export const LISTING_DIAGNOSTIC_TIERS = ["now", "soon", "later", "curious"] as const;
-
-/**
- * The inclusive lower bound of each tier over the 0–12 total (4 questions ×
- * 3 points): `now` 10–12, `soon` 7–9, `later` 4–6, `curious` 0–3. Ordered
- * strongest-first because `evaluateWaitlistScoring` takes the FIRST matching
- * tier, so a `gte` ladder read top-down is total and unambiguous.
- */
-const TIER_FLOORS: Readonly<Record<(typeof LISTING_DIAGNOSTIC_TIERS)[number], number>> = {
-  now: 10,
-  soon: 7,
-  later: 4,
-  curious: 0,
-};
-
-/**
- * Build one listing's register from its own `questions` block. Embedded
- * verbatim into that listing's generated `WaitlistExperiment.config` —
- * `waitlistExperimentConfigSchema` carries the scoring block by value and
- * offers no by-reference slot.
- *
- * Every listing gets the same point names, the same `total` sum, the same
- * tier ladder and the same 0–12 range; only the Q3/Q4 weight KEYS differ,
- * because those keys are the founder's own option values (#5036 D4).
- */
-export function buildListingDiagnosticScoring(
-  questions: ProjectListingQuestions,
-): WaitlistScoring {
-  const weights: Record<ListingDiagnosticScoredQuestion, Record<string, number>> = {
-    q3: listingDiagnosticOptionWeights(questions.q3.options),
-    q4: listingDiagnosticOptionWeights(questions.q4.options),
-    q5: { ...LISTING_DIAGNOSTIC_Q5_WEIGHTS },
-    q6: { ...LISTING_DIAGNOSTIC_Q6_WEIGHTS },
-  };
-
-  return {
-    version: 1,
-    points: LISTING_DIAGNOSTIC_SCORED_QUESTIONS.map((question) => ({
-      name: `${question}_points`,
-      question,
-      kind: "optionWeights" as const,
-      weights: weights[question],
-    })),
-    scores: {
-      total: {
-        sum: LISTING_DIAGNOSTIC_SCORED_QUESTIONS.map((q) => `${q}_points`),
-      },
-    },
-    tiers: LISTING_DIAGNOSTIC_TIERS.map((key) => ({
-      key,
-      when: { score: "total", gte: TIER_FLOORS[key] },
-    })),
-    default: "curious",
-  };
-}