docs(forms): update stale statements in the signal forms docs

- overview: Signal Forms are stable, so drop the suggestion to use
  reactive forms for production stability, and require Angular v22 like
  the comparison guide does.
- validation: readonly fields also skip validation, like hidden and
  disabled fields.
- Restore links to the field state management guide that were commented
  out until the guide was published, and remove the leftover TODO
  comments above live pill rows.
- signal forms tutorial: drop the note that Signal Forms is experimental.
- PACKAGE.md: debouncing is supported through the `debounce()` rule.
- Use the `{when}` form of `disabled()` in JSDoc examples instead of the
  deprecated function overload.

Author: MeAkib

adev/src/content/guide/forms/signals/field-state-management.md

@@ -876,7 +876,6 @@ export class PasswordInput implements FormValueControl<string> {
 
 This guide covered validation and availability status handling, interaction tracking and field state propagation. Related guides explore other aspects of Signal Forms:
 
-<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
 <docs-pill-row>
   <docs-pill href="guide/forms/signals/models" title="Form models" />
   <docs-pill href="guide/forms/signals/validation" title="Validation" />

adev/src/content/guide/forms/signals/models.md

@@ -193,8 +193,7 @@ Field state provides reactive signals for each field's value, making it suitable
 
 TIP: Field state includes many more signals beyond `value()`, such as validation state (e.g., valid, invalid, errors), interaction tracking (e.g., touched, dirty), and visibility (e.g., hidden, disabled).
 
-<!-- TODO: UNCOMMENT BELOW WHEN GUIDE IS AVAILABLE -->
-<!-- See the [Field State Management guide](guide/forms/signals/field-state-management) for complete coverage. -->
+See the [Field State Management guide](guide/forms/signals/field-state-management) for complete coverage.
 
 ## Updating form models programmatically
 
@@ -425,7 +424,6 @@ Array items containing objects automatically receive tracking identities, which
 
 This guide covered creating models and updating values. Related guides explore other aspects of Signal Forms:
 
-<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
 <docs-pill-row>
   <docs-pill href="guide/forms/signals/field-state-management" title="Field state management" />
   <docs-pill href="guide/forms/signals/validation" title="Validation" />

adev/src/content/guide/forms/signals/overview.md

@@ -15,15 +15,15 @@ Signal Forms address these challenges by:
 - **Providing type safety** - Supports fully type safe schemas & bindings between your UI controls and data model
 - **Centralizing validation logic** - Define all validation rules in one place using a validation schema
 
-Signal Forms work best in new applications built with signals. If you're working with an existing application that uses reactive forms, or if you need production stability guarantees, reactive forms remain a solid choice.
+Signal Forms work best in new applications built with signals. If you're working with an existing application that uses reactive forms, reactive forms remain a solid choice.
 
 NOTE: If you're coming from template or reactive forms, you may be interested in the [comparison guide](guide/forms/signals/comparison).
 
 ## Prerequisites
 
 Signal Forms require:
 
-- Angular v21 or higher
+- Angular v22 or higher
 
 ## Setup
 

adev/src/content/guide/forms/signals/validation.md

@@ -38,7 +38,7 @@ Validation in Signal Forms follows this pattern:
 3. **Error propagation** - Validation errors are exposed through field state signals
 4. **Reactive updates** - UI automatically updates when validation state changes
 
-Validation runs on every value change for interactive fields. Hidden and disabled fields don't run validation - their validation rules are skipped until the field becomes interactive again.
+Validation runs on every value change for interactive fields. Hidden, disabled, and readonly fields don't run validation - their validation rules are skipped until the field becomes interactive again.
 
 ### Validation timing
 
@@ -360,9 +360,7 @@ export class OrderComponent {
 
 When validation rules fail, they produce error objects that describe what went wrong. Understanding error structure helps you provide clear feedback to users.
 
-<!-- TODO: Uncomment when field state management guide is published
-
-NOTE: This section covers the errors that validation rules produce. For displaying and using validation errors in your UI, see the [Field State Management guide](guide/forms/signals/field-state-management). -->
+NOTE: This section covers the errors that validation rules produce. For displaying and using validation errors in your UI, see the [Field State Management guide](guide/forms/signals/field-state-management).
 
 ### Error structure
 

adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.md

@@ -29,6 +29,6 @@ Ready to learn more? Here are recommended next steps:
 
 ## Keep learning
 
-IMPORTANT: Signal Forms is experimental, so check the [official documentation](guide/forms/signals/overview) for updates to the API.
+Check the [official documentation](guide/forms/signals/overview) for the full Signal Forms API and more in-depth guides.
 
 Happy coding!

packages/forms/signals/PACKAGE.md

@@ -6,6 +6,5 @@ forms that keeps signals at its core, and interoperates with the existing `@angu
 
 ## Not yet supported
 
-- Debouncing validation
 - Dynamic objects
 - Tuples

packages/forms/signals/src/api/types.ts

@@ -835,7 +835,7 @@ export type Schema<in TModel> = {
  * ```typescript
  * const userFormSchema: SchemaFn<User> = (p) => {
  *   required(p.name);
- *   disabled(p.email, ({valueOf}) => valueOf(p.name) === '');
+ *   disabled(p.email, {when: ({valueOf}) => valueOf(p.name) === ''});
  * };
  *
  * const f = form(userModel, userFormSchema, {injector});

packages/forms/signals/src/field/resolution.ts

@@ -26,7 +26,7 @@ export function getBoundPathDepth() {
  *
  * ```ts
  * const s = schema(p => {
- *   disabled(p.next, ({valueOf}) => valueOf(p.data));
+ *   disabled(p.next, {when: ({valueOf}) => valueOf(p.data)});
  *   apply(p.next, s);
  * });
  * ```