Fix #155: record-props is THE output form — nameable props type for every component

[jagguji]

Closes #155. Amended per review discussion: no flag — record-props is now the only output form.

Problem

Whether a component binds as type props = {…} + external make: React.component<props> or as classic labeled args was decided solely by "extends *HTMLAttributes / shares a base" (recordProps in emit.mjs). A component with a plain, self-contained props object — blend's AccordionItem — always fell to labeled args and never got a nameable props type, which blocks the wrapper/override pattern:

module Item = {
  type props = JuspayRescriptBlend.AccordionItem.props   // ← needs a nameable type
  @react.componentWithProps
  let make = (props: props) => <JuspayRescriptBlend.AccordionItem {...props} onClick=mine />
}

Fix — one output form, no flag

Every component with ≥1 prop emits the record form. Deliberately not a flag (the first cut was --record-props opt-in; review pushback was right): two output modes double the test surface forever and force every consumer regen script to carry an option — for zero benefit, since the forms are behaviorally identical for JSX (v4 lowers to make/props either way). --record-props remains accepted as a no-op so any script that adopted it during the preview keeps working.

// AccordionItem.res (was labeled-args, no nameable type)
type props = {
  value: string,                                  // required stays required
  subtext?: string,
  @as("type") type_?: RecordPropsTypes.recordPropsType,   // reserved words unchanged
  weird?: string,  // ⚪ loose — was `string | { a: 1; } | { b: 2; }`   ← flags survive
}
@module("demo") external make: React.component<props> = "AccordionItem"

Correctness

• Flags carry over — propLine renders both forms; flag markers byte-equal on the benchmark corpus (blend: 910 = 910).
• Generics parameterize — a type-var prop becomes type props<'a> + React.component<props<'a>>; this also makes the Catalog of minor fidelity widenings (TS type vs generated ReScript) for triage — blend 0.0.37-beta.6 #65 variant-fallback path compile-safe (tyvar declared, not free).
• No empty record possible — extraction already skips props-less components (no-props).
• The motivating wrapper pattern is compile-proven in the sandbox ({...props, subtext: ?mine} spread-with-override).

Verification

• All 105 goldens regenerated (form-only flip: labeled → record) and all compile on ReScript — the compile run is the safety net for record-form edges.
• Benchmark: all 9 packages compile with identical usable/review/broken metrics — pure form churn, accepted. Consumers' generated files churn once.
• Fixture record-props (renamed from record-props-flag, no flag in args); smoke checks updated to assert the record form as the default.
• Docs: TYPE_MAPPING (record-props is the form; the HtmlAttrs fall-through cases now emit inline-field records) + CHANGELOG flagged as an output-form change.

🤖 Generated with Claude Code

[github-actions]

Benchmark: ✅ PASS

Package	Compile	Diff vs baseline	usable	review	broken	Verdict
@juspay/blend-design-system@0.0.36	✅	identical	102	5	0	✅ PASS
@juspay/blend-design-system@0.0.37-beta.8	✅	identical	215	7	0	✅ PASS
react-day-picker@10.0.1	✅	identical	19	7	0	✅ PASS
react-tooltip@6.0.7	✅	identical	1	0	0	✅ PASS
react-markdown@10.1.0	✅	identical	0	2	0	✅ PASS
@smastrom/react-rating@1.5.0	✅	identical	1	0	0	✅ PASS
clsx@2.1.1	✅	identical	0	0	0	✅ PASS
hono@4.12.25	✅	identical	0	0	0	✅ PASS
@base-ui-components/react@1.0.0-rc.0	✅	identical	174	21	0	✅ PASS

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@juspay/rescript-bindgen@156

commit: c4d1f95