Add reference pages + availability note for new Windows.System age APIs (GetUserAgeRangeAsync / GetAgeVerificationStatusAsync)

[GrantMeStrength]

Summary

The Windows App SDK / Windows SDK release notes for build 10.0.26100.9169 list four new Windows.System age-signal APIs, but there are no reference pages for them in this repo (checked both docs and live branches):

• Windows.System.User.GetUserAgeRangeAsync → returns Windows.System.UserAgeRange
• Windows.System.User.GetAgeVerificationStatusAsync → returns Windows.System.UserAgeVerificationStatus
• Windows.System.UserAgeRange
• Windows.System.UserAgeVerificationStatus

A full recursive scan of the docs tree returns zero matches for these members/types. They appear to be gated behind an API contract (moniker) that hasn't published to the public reference yet, so the generated skeletons don't exist here.

Requests

1. Once the metadata publishes and the skeletons are generated, add a ## -remarks availability note to each page indicating the APIs are documented ahead of availability and aren't enabled at runtime until a planned future release, and that apps should fall back to default behavior / age-gate (returning an Unknown age range and an unavailable verification status) until then. This mirrors notes already added in MicrosoftDocs/windows-dev-docs-pr (release notes PR #7262, overview article PR #7264).

2. Naming reconciliation (please verify): the only age APIs currently present in this repo are a different, older family, staged on docs but not published to live, with commits dating to 2021 ("Cobalt"):

   • windows.system/user_checkuserageconsentgroupasync_43625918.md (User.CheckUserAgeConsentGroupAsync(UserAgeConsentGroup) → UserAgeConsentResult)
   • windows.system/userageconsentgroup.md (UserAgeConsentGroup { Child, Minor, Adult })
   • windows.system/userageconsentresult.md (UserAgeConsentResult { NotEnforced, Included, NotIncluded, Unknown, Ambiguous })
   • windows.system/knownuserproperties_ageenforcementregion.md (KnownUserProperties.AgeEnforcementRegion)

   Please confirm whether the new age-range / verification surface supersedes or coexists with this consent-group family, and whether the 2021 consent-group pages should be promoted to live, updated, or retired.

Related conceptual docs

• Age signals overview (windows-dev-docs-pr): hub/apps/develop/security/age-signals/index.md
• Windows SDK release notes entry (windows-dev-docs-pr): hub/apps/windows-sdk/release-notes.md, build 10.0.26100.9169, Windows.System section.

Filed from doc-quality investigation; API names cited from the SDK release notes build, not independently verified against shipping winmd metadata.

[GrantMeStrength]

Follow-up: also checked the Win32 reference repo (`MicrosoftDocs/sdk-api`), since the conceptual overview's Platform requirements table lists the API surface as Win32 COM (C/C++).

• Enumerated the complete set of 1,336 header directories under `sdk-api-src/content/` (via the git trees API, `truncated: false`). There is no `digitalsafety`, `agesignals`, `agesignal`, or any `signal` header, and no `GetUserAgeRange` / `AgeVerification` / `DigitalSafety` content on the `docs` branch.
• The only age-related Win32 API present is the legacy `wpcapi` (Windows Parental Controls: `IWindowsParentalControls`, `IWPCSettings`, etc.), which is unrelated.

So the new age-signal APIs are currently in neither reference repo (winrt-api nor sdk-api).

Two things for the owning team to reconcile:

1. Which surface is authoritative — the overview declares Win32 COM, but the documented API names (`GetUserAgeRangeAsync`, `GetAgeVerificationStatusAsync`) and shapes (`IAsyncOperation`, a `{AgeLower, AgeUpper}` struct) read as WinRT. That determines whether the reference lands in sdk-api or here (winrt-api).
2. Naming vs. the existing WinRT consent-group family (`CheckUserAgeConsentGroupAsync` / `UserAgeConsentGroup` / `UserAgeConsentResult`) already staged on this repo's `docs` branch (unpublished since 2021).

Conceptual source: `hub/apps/develop/security/age-signals/index.md` in `MicrosoftDocs/windows-dev-docs-pr`.