@reblu/site-next 1.7.1 → 1.9.0

package/CHANGELOG.md

@@ -1,5 +1,54 @@
 # @reblu/site-next
 
+## 1.9.0
+
+### Minor Changes
+
+- 16dfaea: Add `createSiteManifestRoute` (REB-777), a new `./site-manifest` subpath.
+
+  A Route Handler factory for a SITE's capability manifest, same isolation
+  pattern as `./route-handlers` (REB-510): its own tsup entry, zero
+  dependencies (not even `next/server`), no `'use client'`, so importing it
+  from `app/.well-known/reblu-site.json/route.ts` never drags in any
+  client-component graph.
+
+  ```ts
+  export const GET = createSiteManifestRoute({
+    surfaces: { 'academy.enrollment': { path: '/academia/inscripcion' } },
+  })
+  ```
+
+  Serves `{ manifestVersion: 1, sdkVersion?, surfaces }` as JSON with a short
+  public `Cache-Control` (this payload holds no tenant secrets). `surfaces`
+  keys are typed against `@reblu/site-contracts`'s new
+  `SiteCapabilitySurfaceKey` — a typo in a surface key is a compile error, not
+  a silent no-op.
+
+  Purely additive — a new export, nothing existing changed.
+
+### Patch Changes
+
+- d4dd66d: Fix `deriveValidationFields` throwing when called from a Server Component.
+  `@reblu/site-next/academy` carries a leading `'use client'` directive so
+  `AcademyEnrollmentForm` survives the build, which made the whole entry —
+  including the pure, dependency-free `deriveValidationFields` helper — look
+  client-only to Next's RSC boundary. Add `@reblu/site-next/academy-server`, a
+  new server-safe subpath exporting only `deriveValidationFields` and its
+  types, for Server Components to import from. `@reblu/site-next/academy`
+  still re-exports `deriveValidationFields` unchanged for existing consumers
+  and client-side call sites.
+- Updated dependencies [16dfaea]
+  - @reblu/site-contracts@1.1.0
+
+## 1.8.0
+
+### Minor Changes
+
+- 984f8b5: Add `@reblu/site-next/academy`, exporting `AcademyEnrollmentForm` — a
+  copy-injectable, per-tenant customizable enrollment-request form — and
+  `deriveValidationFields`, a pure helper that derives its validation fields
+  from the course/config data a SITE's academy API already returns.
+
 ## 1.7.1
 
 ### Patch Changes

package/README.md

@@ -18,6 +18,10 @@ intentionally Next-coupled so the lower SDK layers —
 5. **reCAPTCHA v3** (`./recaptcha`) — the SITE's half of the contact-form
    captcha contract: the canonical action, the render gate, and the
    interaction-mount key. See "reCAPTCHA v3" below.
+6. **Academy** (`./academy`, `./academy-server`) — `AcademyEnrollmentForm`,
+   the anonymous enrollment-request form, plus `deriveValidationFields` to
+   build its per-tenant validation fields from course/config data. See
+   "Academy" below.
 
 ## Install
 
@@ -149,6 +153,93 @@ export const POST = createProxyRoute('/api/site/auth/login')
 `REBLU_API_BASE_URL`/`REBLU_API_KEY` env vars — read lazily per request, not at
 module load.
 
+## Academy
+
+`@reblu/site-next/academy` exports the anonymous academy enrollment-request
+form (`AcademyEnrollmentForm`) and re-exports the pure helper that derives its
+validation fields from tenant data (`deriveValidationFields`).
+`@reblu/site-next/academy-server` exports ONLY that pure helper.
+
+**Which subpath to import from matters.** `./academy` carries a leading
+`'use client'` directive — required so `AcademyEnrollmentForm` survives the
+build — and the whole entry (helper included) is one directive-covered chunk.
+Calling `deriveValidationFields` imported from `./academy` inside a Server
+Component throws at runtime ("Attempted to call deriveValidationFields() from
+the server but deriveValidationFields is on the client"), because Next's RSC
+boundary sees the whole entry as client-only. A course detail page is
+typically an async Server Component computing `validationFields` to pass down
+as a prop — exactly the case that needs the server-safe subpath:
+
+```tsx
+// app/academy/[slug]/page.tsx — an async Server Component
+import { AcademyEnrollmentForm } from '@reblu/site-next/academy'
+import { deriveValidationFields } from '@reblu/site-next/academy-server'
+
+// `course` is whatever `GET /api/site/academy/courses/[slug]` (via
+// `@reblu/site-client`'s `academy.bySlug`) already returned — this form never
+// re-derives `salesEnabled` or requests anything extra.
+const validationFields = deriveValidationFields(course)
+
+{course.salesEnabled && (
+  <AcademyEnrollmentForm
+    enrollmentRequestUrl="/api/academy/enrollment-requests"
+    courseSlug={course.slug}
+    validationFields={validationFields}
+  />
+)}
+```
+
+Import `deriveValidationFields` from `./academy` instead only when the call
+site is already inside a `'use client'` boundary (e.g. computing it alongside
+other client-side state) — `./academy` still re-exports it for that case and
+for call sites that prefer one import statement for both.
+
+`enrollmentRequestUrl` is a SITE-owned Route Handler path — `/api/academy/
+enrollment-requests` above is illustrative; the SITE chooses its own local
+route. The browser can never call base-api directly (`X-Reblu-Api-Key` is a
+server secret), so that local route proxies to the platform endpoint,
+`POST /api/site/academy/enrollment-requests`. Wire it with `createProxyRoute`
+from `./route-handlers`:
+
+```ts
+// app/api/academy/enrollment-requests/route.ts
+import { createProxyRoute } from '@reblu/site-next/route-handlers'
+
+export const POST = createProxyRoute('/api/site/academy/enrollment-requests')
+```
+
+**PER-TENANT, DATA-DRIVEN — not code-driven.** Whether a course asks for extra
+verification, and which fields it asks for, is entirely tenant configuration:
+
+- Today, `AcademyCourseDetail` exposes only `requiresValidation` +
+  `validationFieldLabel` (a single generic field). `deriveValidationFields`
+  falls back to that one field when no richer list is present.
+- A future tenant-configurable list (e.g. `AcademyConfig.validationFields: [{
+  key, label, required, maxLength? }]`) is accepted by the SAME helper —
+  `AcademyValidationSource` is defined structurally, so a wider real contract
+  type is already assignable without an SDK release. Arbitrary keys (a
+  colegiado number, a professional college, anything a tenant configures) work
+  the moment the data carries them; `AcademyEnrollmentForm` never hardcodes a
+  field name — it only ever iterates the `validationFields` array it was given.
+- A tenant with no validation requirement passes `validationFields={[]}` (or
+  omits the prop, `[]` is the default) — the form renders only the email
+  field.
+
+**Never a purchase confirmation.** The upstream route
+(`POST /api/site/academy/enrollment-requests`) replies UNIFORMLY whether the
+email was brand-new (a request row was created) or already known (a sign-in
+link was sent, nothing created) — anti-enumeration by design. The form's
+always-visible copy says the request goes to human review and that no
+automatic charge happens; `onSubmitted` fires on any 2xx and must never be
+read as "a request was recorded".
+
+**Field-level errors.** A non-2xx JSON body shaped like `{ error, details:
+{ fieldErrors } }` (`ApiErrorBody`/`ApiErrorDetails` from `@reblu/site-client`)
+maps each `fieldErrors` key onto the matching input (`email`, or a
+`validationFields[].key`) and focuses the first one; anything else — no
+`details`, or a `429` — renders as a single form-level error instead. No
+reCAPTCHA: the route is IP rate-limited server-side.
+
 ## Structured data (JSON-LD)
 
 `@reblu/site-next/json-ld` (REB-622, server-only, dependency-free) renders one

package/dist/academy-server.cjs

@@ -0,0 +1,52 @@
+"use strict";
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __export = (target, all) => {
+  for (var name in all)
+    __defProp(target, name, { get: all[name], enumerable: true });
+};
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+
+// src/academy/server.ts
+var server_exports = {};
+__export(server_exports, {
+  deriveValidationFields: () => deriveValidationFields
+});
+module.exports = __toCommonJS(server_exports);
+
+// src/academy/derive-validation-fields.ts
+var DEFAULT_GENERIC_VALIDATION_KEY = "validationField";
+var DEFAULT_GENERIC_VALIDATION_LABEL = "Dato de verificaci\xF3n";
+function deriveValidationFields(source, options = {}) {
+  if (!source.requiresValidation) return [];
+  if (source.validationFields && source.validationFields.length > 0) {
+    return source.validationFields.map((field) => ({
+      key: field.key,
+      label: field.label,
+      required: field.required ?? true,
+      ...field.maxLength !== void 0 ? { maxLength: field.maxLength } : {}
+    }));
+  }
+  return [
+    {
+      key: options.genericKey ?? DEFAULT_GENERIC_VALIDATION_KEY,
+      label: source.validationFieldLabel || options.genericLabel || DEFAULT_GENERIC_VALIDATION_LABEL,
+      required: source.validationFieldRequired ?? true
+    }
+  ];
+}
+// Annotate the CommonJS export names for ESM import in node:
+0 && (module.exports = {
+  deriveValidationFields
+});
+//# sourceMappingURL=academy-server.cjs.map

package/dist/academy-server.cjs.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/academy/server.ts","../src/academy/derive-validation-fields.ts"],"sourcesContent":["/**\n * `@reblu/site-next/academy-server` — the server-safe half of the academy SDK\n * surface (defect fix, follow-up to REB-584/#1095).\n *\n * `deriveValidationFields` is a pure, dependency-free helper (no React, no\n * `@reblu/site-ui`) — exactly the kind of thing a Server Component should be\n * able to call directly, and the README/demo-site usage pattern always called\n * it inline in an async Server Component. But `./academy` (`src/academy/index.ts`)\n * carries its OWN leading `'use client'` directive so `AcademyEnrollmentForm`\n * survives the build (R4 — see `tsup.config.ts`), and with `splitting: false`\n * the whole entry is ONE self-contained chunk sharing that single directive\n * prologue. That made every import from `./academy`, including this pure\n * helper, look like a client-only export to Next's RSC boundary — calling\n * `deriveValidationFields` from a Server Component threw \"Attempted to call\n * deriveValidationFields() from the server but deriveValidationFields is on\n * the client\".\n *\n * This module is its OWN tsup entry (subpath `./academy-server`) with NO\n * React import of any kind, so it must NEVER carry `'use client'` — same\n * direction as `./route-handlers` and `./recaptcha`. Server Components MUST\n * import `deriveValidationFields` from here, not from `./academy`; Client\n * Components (or anywhere already inside a `'use client'` boundary) may keep\n * using either subpath — `./academy` still re-exports it for callers that\n * import it alongside `AcademyEnrollmentForm` in one statement.\n */\nexport {\n  deriveValidationFields,\n  type AcademyValidationField,\n  type AcademyValidationFieldConfig,\n  type AcademyValidationSource,\n  type DeriveValidationFieldsOptions,\n} from './derive-validation-fields'\n","/**\n * `@reblu/site-next/academy` (also re-exported from the server-safe\n * `@reblu/site-next/academy-server` subpath — see `./server.ts`) — validation-\n * field derivation (REB-584 follow-up).\n *\n * PER-TENANT, DATA-DRIVEN (not code-driven): whether an enrollment request asks\n * for extra verification, and which fields it asks for, comes entirely from the\n * tenant's academy config / course data. This module never hardcodes a\n * sector-specific field name or label — the SDK does not know what a\n * \"colegiado\" is, and never will.\n *\n * Today the public course-detail contract (`AcademyCourseDetail`) exposes only\n * `requiresValidation` + `validationFieldLabel` — a single generic field, no\n * per-field `required` flag of its own (that flag lives on `AcademyConfig`,\n * server-side only, and isn't in the DTO yet). REB-83 is expected to add a\n * genuinely tenant-configurable list (`AcademyConfig.validationFields: [{ key,\n * label, required, maxLength? }]`) to that contract, which is how the upcoming\n * `collegiateNumber` / `professionalCollege` keys arrive — as DATA, not a code\n * change here.\n *\n * `AcademyValidationSource` is therefore defined STRUCTURALLY, not imported from\n * `@reblu/site-contracts`: it accepts whatever subset of fields the caller's\n * data actually has today, and remains satisfied once REB-83 lands a wider\n * real type — a course/config object with a `validationFields` array is already\n * assignable to this interface without a SITE-side type change.\n */\n\n/** A single tenant-defined (or derived) validation field the form should render. */\nexport interface AcademyValidationField {\n  key: string\n  label: string\n  required: boolean\n  maxLength?: number\n}\n\n/**\n * The shape a tenant-configured validation field list entry may take\n * (REB-83). `required` and `maxLength` are optional on the INPUT — the output\n * `AcademyValidationField` always carries a resolved `required`.\n */\nexport interface AcademyValidationFieldConfig {\n  key: string\n  label: string\n  required?: boolean\n  maxLength?: number\n}\n\n/**\n * Structural input — a subset of `AcademyCourseDetail` (today) plus the\n * optional REB-83 fields once the config/course exposes them. Any real DTO\n * that is at least this wide is assignable here without an import.\n */\nexport interface AcademyValidationSource {\n  requiresValidation: boolean\n  /** Present on `AcademyCourseDetail` today. */\n  validationFieldLabel?: string | null\n  /**\n   * NOT yet in `AcademyCourseDetail` (server-only, on `AcademyConfig`) —\n   * accepted here so a SITE that already has it (e.g. from a wider tenant\n   * config read) can pass it through; defaults to `true` (erring strict) when\n   * absent, matching the existing demo-site precedent.\n   */\n  validationFieldRequired?: boolean | null\n  /** REB-83 — tenant-defined list. When present and non-empty, takes priority\n   * over the single-field fallback below. */\n  validationFields?: AcademyValidationFieldConfig[] | null\n}\n\nexport interface DeriveValidationFieldsOptions {\n  /** @default 'validationField' */\n  genericKey?: string\n  /** @default 'Dato de verificación' */\n  genericLabel?: string\n}\n\nexport const DEFAULT_GENERIC_VALIDATION_KEY = 'validationField'\nexport const DEFAULT_GENERIC_VALIDATION_LABEL = 'Dato de verificación'\n\n/**\n * Derives the list of validation fields an enrollment form should render for\n * a course, from data alone.\n *\n * - `requiresValidation` is false → no fields (the form renders none).\n * - A non-empty `validationFields` list (REB-83) → used verbatim, arbitrary\n *   keys included, each entry's `required` defaulting to `true` when absent.\n * - Otherwise → falls back to the single generic field the SITE already knows\n *   today, labeled from `validationFieldLabel` (or the generic fallback\n *   label when the tenant configured no label).\n */\nexport function deriveValidationFields(\n  source: AcademyValidationSource,\n  options: DeriveValidationFieldsOptions = {},\n): AcademyValidationField[] {\n  if (!source.requiresValidation) return []\n\n  if (source.validationFields && source.validationFields.length > 0) {\n    return source.validationFields.map((field) => ({\n      key: field.key,\n      label: field.label,\n      required: field.required ?? true,\n      ...(field.maxLength !== undefined ? { maxLength: field.maxLength } : {}),\n    }))\n  }\n\n  return [\n    {\n      key: options.genericKey ?? DEFAULT_GENERIC_VALIDATION_KEY,\n      label:\n        source.validationFieldLabel || options.genericLabel || DEFAULT_GENERIC_VALIDATION_LABEL,\n      required: source.validationFieldRequired ?? true,\n    },\n  ]\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;;;AC2EO,IAAM,iCAAiC;AACvC,IAAM,mCAAmC;AAazC,SAAS,uBACd,QACA,UAAyC,CAAC,GAChB;AAC1B,MAAI,CAAC,OAAO,mBAAoB,QAAO,CAAC;AAExC,MAAI,OAAO,oBAAoB,OAAO,iBAAiB,SAAS,GAAG;AACjE,WAAO,OAAO,iBAAiB,IAAI,CAAC,WAAW;AAAA,MAC7C,KAAK,MAAM;AAAA,MACX,OAAO,MAAM;AAAA,MACb,UAAU,MAAM,YAAY;AAAA,MAC5B,GAAI,MAAM,cAAc,SAAY,EAAE,WAAW,MAAM,UAAU,IAAI,CAAC;AAAA,IACxE,EAAE;AAAA,EACJ;AAEA,SAAO;AAAA,IACL;AAAA,MACE,KAAK,QAAQ,cAAc;AAAA,MAC3B,OACE,OAAO,wBAAwB,QAAQ,gBAAgB;AAAA,MACzD,UAAU,OAAO,2BAA2B;AAAA,IAC9C;AAAA,EACF;AACF;","names":[]}

package/dist/academy-server.d.cts

@@ -0,0 +1,84 @@
+/**
+ * `@reblu/site-next/academy` (also re-exported from the server-safe
+ * `@reblu/site-next/academy-server` subpath — see `./server.ts`) — validation-
+ * field derivation (REB-584 follow-up).
+ *
+ * PER-TENANT, DATA-DRIVEN (not code-driven): whether an enrollment request asks
+ * for extra verification, and which fields it asks for, comes entirely from the
+ * tenant's academy config / course data. This module never hardcodes a
+ * sector-specific field name or label — the SDK does not know what a
+ * "colegiado" is, and never will.
+ *
+ * Today the public course-detail contract (`AcademyCourseDetail`) exposes only
+ * `requiresValidation` + `validationFieldLabel` — a single generic field, no
+ * per-field `required` flag of its own (that flag lives on `AcademyConfig`,
+ * server-side only, and isn't in the DTO yet). REB-83 is expected to add a
+ * genuinely tenant-configurable list (`AcademyConfig.validationFields: [{ key,
+ * label, required, maxLength? }]`) to that contract, which is how the upcoming
+ * `collegiateNumber` / `professionalCollege` keys arrive — as DATA, not a code
+ * change here.
+ *
+ * `AcademyValidationSource` is therefore defined STRUCTURALLY, not imported from
+ * `@reblu/site-contracts`: it accepts whatever subset of fields the caller's
+ * data actually has today, and remains satisfied once REB-83 lands a wider
+ * real type — a course/config object with a `validationFields` array is already
+ * assignable to this interface without a SITE-side type change.
+ */
+/** A single tenant-defined (or derived) validation field the form should render. */
+interface AcademyValidationField {
+    key: string;
+    label: string;
+    required: boolean;
+    maxLength?: number;
+}
+/**
+ * The shape a tenant-configured validation field list entry may take
+ * (REB-83). `required` and `maxLength` are optional on the INPUT — the output
+ * `AcademyValidationField` always carries a resolved `required`.
+ */
+interface AcademyValidationFieldConfig {
+    key: string;
+    label: string;
+    required?: boolean;
+    maxLength?: number;
+}
+/**
+ * Structural input — a subset of `AcademyCourseDetail` (today) plus the
+ * optional REB-83 fields once the config/course exposes them. Any real DTO
+ * that is at least this wide is assignable here without an import.
+ */
+interface AcademyValidationSource {
+    requiresValidation: boolean;
+    /** Present on `AcademyCourseDetail` today. */
+    validationFieldLabel?: string | null;
+    /**
+     * NOT yet in `AcademyCourseDetail` (server-only, on `AcademyConfig`) —
+     * accepted here so a SITE that already has it (e.g. from a wider tenant
+     * config read) can pass it through; defaults to `true` (erring strict) when
+     * absent, matching the existing demo-site precedent.
+     */
+    validationFieldRequired?: boolean | null;
+    /** REB-83 — tenant-defined list. When present and non-empty, takes priority
+     * over the single-field fallback below. */
+    validationFields?: AcademyValidationFieldConfig[] | null;
+}
+interface DeriveValidationFieldsOptions {
+    /** @default 'validationField' */
+    genericKey?: string;
+    /** @default 'Dato de verificación' */
+    genericLabel?: string;
+}
+/**
+ * Derives the list of validation fields an enrollment form should render for
+ * a course, from data alone.
+ *
+ * - `requiresValidation` is false → no fields (the form renders none).
+ * - A non-empty `validationFields` list (REB-83) → used verbatim, arbitrary
+ *   keys included, each entry's `required` defaulting to `true` when absent.
+ * - Otherwise → falls back to the single generic field the SITE already knows
+ *   today, labeled from `validationFieldLabel` (or the generic fallback
+ *   label when the tenant configured no label).
+ */
+declare function deriveValidationFields(source: AcademyValidationSource, options?: DeriveValidationFieldsOptions): AcademyValidationField[];
+
+export { type AcademyValidationField, type AcademyValidationFieldConfig, type AcademyValidationSource, type DeriveValidationFieldsOptions, deriveValidationFields };

package/dist/academy-server.d.ts

@@ -0,0 +1,84 @@
+/**
+ * `@reblu/site-next/academy` (also re-exported from the server-safe
+ * `@reblu/site-next/academy-server` subpath — see `./server.ts`) — validation-
+ * field derivation (REB-584 follow-up).
+ *
+ * PER-TENANT, DATA-DRIVEN (not code-driven): whether an enrollment request asks
+ * for extra verification, and which fields it asks for, comes entirely from the
+ * tenant's academy config / course data. This module never hardcodes a
+ * sector-specific field name or label — the SDK does not know what a
+ * "colegiado" is, and never will.
+ *
+ * Today the public course-detail contract (`AcademyCourseDetail`) exposes only
+ * `requiresValidation` + `validationFieldLabel` — a single generic field, no
+ * per-field `required` flag of its own (that flag lives on `AcademyConfig`,
+ * server-side only, and isn't in the DTO yet). REB-83 is expected to add a
+ * genuinely tenant-configurable list (`AcademyConfig.validationFields: [{ key,
+ * label, required, maxLength? }]`) to that contract, which is how the upcoming
+ * `collegiateNumber` / `professionalCollege` keys arrive — as DATA, not a code
+ * change here.
+ *
+ * `AcademyValidationSource` is therefore defined STRUCTURALLY, not imported from
+ * `@reblu/site-contracts`: it accepts whatever subset of fields the caller's
+ * data actually has today, and remains satisfied once REB-83 lands a wider
+ * real type — a course/config object with a `validationFields` array is already
+ * assignable to this interface without a SITE-side type change.
+ */
+/** A single tenant-defined (or derived) validation field the form should render. */
+interface AcademyValidationField {
+    key: string;
+    label: string;
+    required: boolean;
+    maxLength?: number;
+}
+/**
+ * The shape a tenant-configured validation field list entry may take
+ * (REB-83). `required` and `maxLength` are optional on the INPUT — the output
+ * `AcademyValidationField` always carries a resolved `required`.
+ */
+interface AcademyValidationFieldConfig {
+    key: string;
+    label: string;
+    required?: boolean;
+    maxLength?: number;
+}
+/**
+ * Structural input — a subset of `AcademyCourseDetail` (today) plus the
+ * optional REB-83 fields once the config/course exposes them. Any real DTO
+ * that is at least this wide is assignable here without an import.
+ */
+interface AcademyValidationSource {
+    requiresValidation: boolean;
+    /** Present on `AcademyCourseDetail` today. */
+    validationFieldLabel?: string | null;
+    /**
+     * NOT yet in `AcademyCourseDetail` (server-only, on `AcademyConfig`) —
+     * accepted here so a SITE that already has it (e.g. from a wider tenant
+     * config read) can pass it through; defaults to `true` (erring strict) when
+     * absent, matching the existing demo-site precedent.
+     */
+    validationFieldRequired?: boolean | null;
+    /** REB-83 — tenant-defined list. When present and non-empty, takes priority
+     * over the single-field fallback below. */
+    validationFields?: AcademyValidationFieldConfig[] | null;
+}
+interface DeriveValidationFieldsOptions {
+    /** @default 'validationField' */
+    genericKey?: string;
+    /** @default 'Dato de verificación' */
+    genericLabel?: string;
+}
+/**
+ * Derives the list of validation fields an enrollment form should render for
+ * a course, from data alone.
+ *
+ * - `requiresValidation` is false → no fields (the form renders none).
+ * - A non-empty `validationFields` list (REB-83) → used verbatim, arbitrary
+ *   keys included, each entry's `required` defaulting to `true` when absent.
+ * - Otherwise → falls back to the single generic field the SITE already knows
+ *   today, labeled from `validationFieldLabel` (or the generic fallback
+ *   label when the tenant configured no label).
+ */
+declare function deriveValidationFields(source: AcademyValidationSource, options?: DeriveValidationFieldsOptions): AcademyValidationField[];
+
+export { type AcademyValidationField, type AcademyValidationFieldConfig, type AcademyValidationSource, type DeriveValidationFieldsOptions, deriveValidationFields };

package/dist/academy-server.js

@@ -0,0 +1,25 @@
+// src/academy/derive-validation-fields.ts
+var DEFAULT_GENERIC_VALIDATION_KEY = "validationField";
+var DEFAULT_GENERIC_VALIDATION_LABEL = "Dato de verificaci\xF3n";
+function deriveValidationFields(source, options = {}) {
+  if (!source.requiresValidation) return [];
+  if (source.validationFields && source.validationFields.length > 0) {
+    return source.validationFields.map((field) => ({
+      key: field.key,
+      label: field.label,
+      required: field.required ?? true,
+      ...field.maxLength !== void 0 ? { maxLength: field.maxLength } : {}
+    }));
+  }
+  return [
+    {
+      key: options.genericKey ?? DEFAULT_GENERIC_VALIDATION_KEY,
+      label: source.validationFieldLabel || options.genericLabel || DEFAULT_GENERIC_VALIDATION_LABEL,
+      required: source.validationFieldRequired ?? true
+    }
+  ];
+}
+export {
+  deriveValidationFields
+};
+//# sourceMappingURL=academy-server.js.map

package/dist/academy-server.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/academy/derive-validation-fields.ts"],"sourcesContent":["/**\n * `@reblu/site-next/academy` (also re-exported from the server-safe\n * `@reblu/site-next/academy-server` subpath — see `./server.ts`) — validation-\n * field derivation (REB-584 follow-up).\n *\n * PER-TENANT, DATA-DRIVEN (not code-driven): whether an enrollment request asks\n * for extra verification, and which fields it asks for, comes entirely from the\n * tenant's academy config / course data. This module never hardcodes a\n * sector-specific field name or label — the SDK does not know what a\n * \"colegiado\" is, and never will.\n *\n * Today the public course-detail contract (`AcademyCourseDetail`) exposes only\n * `requiresValidation` + `validationFieldLabel` — a single generic field, no\n * per-field `required` flag of its own (that flag lives on `AcademyConfig`,\n * server-side only, and isn't in the DTO yet). REB-83 is expected to add a\n * genuinely tenant-configurable list (`AcademyConfig.validationFields: [{ key,\n * label, required, maxLength? }]`) to that contract, which is how the upcoming\n * `collegiateNumber` / `professionalCollege` keys arrive — as DATA, not a code\n * change here.\n *\n * `AcademyValidationSource` is therefore defined STRUCTURALLY, not imported from\n * `@reblu/site-contracts`: it accepts whatever subset of fields the caller's\n * data actually has today, and remains satisfied once REB-83 lands a wider\n * real type — a course/config object with a `validationFields` array is already\n * assignable to this interface without a SITE-side type change.\n */\n\n/** A single tenant-defined (or derived) validation field the form should render. */\nexport interface AcademyValidationField {\n  key: string\n  label: string\n  required: boolean\n  maxLength?: number\n}\n\n/**\n * The shape a tenant-configured validation field list entry may take\n * (REB-83). `required` and `maxLength` are optional on the INPUT — the output\n * `AcademyValidationField` always carries a resolved `required`.\n */\nexport interface AcademyValidationFieldConfig {\n  key: string\n  label: string\n  required?: boolean\n  maxLength?: number\n}\n\n/**\n * Structural input — a subset of `AcademyCourseDetail` (today) plus the\n * optional REB-83 fields once the config/course exposes them. Any real DTO\n * that is at least this wide is assignable here without an import.\n */\nexport interface AcademyValidationSource {\n  requiresValidation: boolean\n  /** Present on `AcademyCourseDetail` today. */\n  validationFieldLabel?: string | null\n  /**\n   * NOT yet in `AcademyCourseDetail` (server-only, on `AcademyConfig`) —\n   * accepted here so a SITE that already has it (e.g. from a wider tenant\n   * config read) can pass it through; defaults to `true` (erring strict) when\n   * absent, matching the existing demo-site precedent.\n   */\n  validationFieldRequired?: boolean | null\n  /** REB-83 — tenant-defined list. When present and non-empty, takes priority\n   * over the single-field fallback below. */\n  validationFields?: AcademyValidationFieldConfig[] | null\n}\n\nexport interface DeriveValidationFieldsOptions {\n  /** @default 'validationField' */\n  genericKey?: string\n  /** @default 'Dato de verificación' */\n  genericLabel?: string\n}\n\nexport const DEFAULT_GENERIC_VALIDATION_KEY = 'validationField'\nexport const DEFAULT_GENERIC_VALIDATION_LABEL = 'Dato de verificación'\n\n/**\n * Derives the list of validation fields an enrollment form should render for\n * a course, from data alone.\n *\n * - `requiresValidation` is false → no fields (the form renders none).\n * - A non-empty `validationFields` list (REB-83) → used verbatim, arbitrary\n *   keys included, each entry's `required` defaulting to `true` when absent.\n * - Otherwise → falls back to the single generic field the SITE already knows\n *   today, labeled from `validationFieldLabel` (or the generic fallback\n *   label when the tenant configured no label).\n */\nexport function deriveValidationFields(\n  source: AcademyValidationSource,\n  options: DeriveValidationFieldsOptions = {},\n): AcademyValidationField[] {\n  if (!source.requiresValidation) return []\n\n  if (source.validationFields && source.validationFields.length > 0) {\n    return source.validationFields.map((field) => ({\n      key: field.key,\n      label: field.label,\n      required: field.required ?? true,\n      ...(field.maxLength !== undefined ? { maxLength: field.maxLength } : {}),\n    }))\n  }\n\n  return [\n    {\n      key: options.genericKey ?? DEFAULT_GENERIC_VALIDATION_KEY,\n      label:\n        source.validationFieldLabel || options.genericLabel || DEFAULT_GENERIC_VALIDATION_LABEL,\n      required: source.validationFieldRequired ?? true,\n    },\n  ]\n}\n"],"mappings":";AA2EO,IAAM,iCAAiC;AACvC,IAAM,mCAAmC;AAazC,SAAS,uBACd,QACA,UAAyC,CAAC,GAChB;AAC1B,MAAI,CAAC,OAAO,mBAAoB,QAAO,CAAC;AAExC,MAAI,OAAO,oBAAoB,OAAO,iBAAiB,SAAS,GAAG;AACjE,WAAO,OAAO,iBAAiB,IAAI,CAAC,WAAW;AAAA,MAC7C,KAAK,MAAM;AAAA,MACX,OAAO,MAAM;AAAA,MACb,UAAU,MAAM,YAAY;AAAA,MAC5B,GAAI,MAAM,cAAc,SAAY,EAAE,WAAW,MAAM,UAAU,IAAI,CAAC;AAAA,IACxE,EAAE;AAAA,EACJ;AAEA,SAAO;AAAA,IACL;AAAA,MACE,KAAK,QAAQ,cAAc;AAAA,MAC3B,OACE,OAAO,wBAAwB,QAAQ,gBAAgB;AAAA,MACzD,UAAU,OAAO,2BAA2B;AAAA,IAC9C;AAAA,EACF;AACF;","names":[]}