feat: add respondent attributes to SignInFieldAttributes

[bheddens]

What

Adds two attributes to SignInFieldAttributes:

'allow-visitor-respondents'?: boolean;
'allow-employee-respondents'?: boolean;

These back the Field options → Respondents controls in the dashboard. Both are writable on the v3 sign-in-fields resource (app/resources/api/v3/sign_in_field_resource.rb declares them, and only created_at/updated_at are readonly there), and both default to true in the database:

sign_in_fields.allow_visitor_respondents   boolean DEFAULT true NOT NULL
sign_in_fields.allow_employee_respondents  boolean DEFAULT true NOT NULL

Why

An integration that creates a sign-in field holding a value only an admin can supply, a badge or card number read off the credential, has no way to say so through this type. Because the columns default to true, the field is silently offered to visitors and to employees, neither of whom can know the number.

pacs-integration-service #327 fixes that for the Card ID field, but has to cast past this interface to do it:

export const CARD_ID_RESPONDENT_DEFAULTS = {
  'allow-visitor-respondents': false,
  'allow-employee-respondents': false,
} as Partial<EnvoySignInFieldConfig>;

With this merged and released, that cast comes out.

Optional, not required

Marked optional to match 'store-response'?: boolean, even though the columns are NOT NULL and a read always returns them. Required would be a breaking change for anyone building an attributes literal, and it buys nothing: the internal SDK's creation model already makes everything except name and kind partial, so optionality here does not weaken creation payloads.

Verification

tsc --noEmit, eslint, and prettier clean. Test suite green: 5 suites, 72 tests. Type-only change, so no new tests.

Version bumped to 2.5.3 in package.json and package-lock.json, matching how #115 handled a comparable additive change to the payload types (2.5.1 -> 2.5.2). Publishing itself still happens on release creation, so this only stages the version.

[Copilot]

Pull request overview

Adds respondent-scoping attributes to the Node SDK’s SignInFieldAttributes type so integrations can control whether visitors and/or employees are allowed to answer a sign-in field, matching the v3 API and database defaults.

Changes:

• Extend SignInFieldAttributes with 'allow-visitor-respondents'?: boolean and 'allow-employee-respondents'?: boolean.
• Add inline JSDoc explaining semantics and server-side default behavior for these new attributes.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ryanflynndev]

Please update the version