The 5-forms-per-site limit was a hardcoded constant in formsManifestService.js, enforced on every export — including OSS, where our policy is no limits. It's now a proper limit key like all the others: LIMIT_KEYS.MAX_FORMS_PER_SITE, resolved from the limits adapter at export time. OSS's local adapter returns Infinity; when no adapter is wired, the old default of 5 still applies.
Action needed on hosted: the hosted limits adapter must answer the new key — the limits conformance suite will fail until it does. Return 5 to keep today's behavior, or whatever the tier tables say.
Two open product decisions for hosted (recorded in docs-llms/future-multilang.md § Hosted product questions), no code blocked on them:
Do translated collection items count against MAX_COLLECTION_ITEMS physically (3 languages = 3 items) or per translation group? Code currently counts physically.
Once multilang lands, does each per-language form stream consume a form slot? If yes, 5 collapses immediately (2 forms × 3 languages = 6) — group-based counting is the lean.
Form shape rules (30 fields/form, 50 options/field, 200-char options, 64-char keys) are unchanged and still hardcoded — they're the forms-service file contract, not a count limit.
The 5-forms-per-site limit was a hardcoded constant in formsManifestService.js, enforced on every export — including OSS, where our policy is no limits. It's now a proper limit key like all the others: LIMIT_KEYS.MAX_FORMS_PER_SITE, resolved from the limits adapter at export time. OSS's local adapter returns Infinity; when no adapter is wired, the old default of 5 still applies.
Action needed on hosted: the hosted limits adapter must answer the new key — the limits conformance suite will fail until it does. Return 5 to keep today's behavior, or whatever the tier tables say.
Two open product decisions for hosted (recorded in docs-llms/future-multilang.md § Hosted product questions), no code blocked on them:
Do translated collection items count against MAX_COLLECTION_ITEMS physically (3 languages = 3 items) or per translation group? Code currently counts physically.
Once multilang lands, does each per-language form stream consume a form slot? If yes, 5 collapses immediately (2 forms × 3 languages = 6) — group-based counting is the lean.
Form shape rules (30 fields/form, 50 options/field, 200-char options, 64-char keys) are unchanged and still hardcoded — they're the forms-service file contract, not a count limit.