perf(forms): stop duplicating form schema in collector context

[dmourot]

The form collector context was embedding the full form schema as JSON, duplicating field names, types, descriptions and allowed values that already reach the agent through the update_<name> tool params. The context now sends only the requiredness information the tool omits: the base required list (the tool sends [] for incremental filling) and the per-field requiredWhen conditions (stripped from the tool schema to stay JSON-Schema-legal). For large forms the embedded schema was the single biggest chunk of the request, so this roughly halves the prompt in those cases. Tests cover the new requiredness rules and guard against the full schema being re-embedded.

🤖 Generated with Claude Code

[dmourot]

Code review

Found 1 issue (fixed in 3202951 per the fix >= 50 request):

1. Four JSDoc comments still claimed the full form schema reaches the agent via the dynamic context, but this PR changed the context to send only the requiredness rules (required list + requiredWhen conditions). The comments on FormFieldCondition, FormFieldSchema.requiredWhen, FormCollectorSchema, and toWireParameters were left stale and now describe behavior the PR removed (bug due to the JSON.stringify(schema) → JSON.stringify(requirementRules) change in contextProvider).

ago-sdk/src/forms/createFormCollector.ts

Lines 40 to 42 in 455870c

	* Stripped from the LLM tool's `parameters` (see {@link toWireParameters}), but the
	* full schema, `requiredWhen` included, still reaches the agent via the dynamic
	* context so it knows when each field becomes required.

Two other candidates were checked and dismissed as pre-existing (not introduced by this PR): a field listed in both required and requiredWhen reads as always-required, and the "Some fields are conditionally required" sentence is emitted unconditionally. Both behaviors existed before this change.

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}