Fix/ss log app metadata user metadata clarification

[nick-gagliardi]

Description

Clarifies when app_metadata and user_metadata appear in the ss (Successful Signup) tenant log schema.

The schema listed both fields without explaining that details.body reflects the raw signup request payload — not the final user
record. Customers using pre-registration Actions to set app_metadata or user_metadata expected to see those values in the log,
but they were absent because Action-applied metadata is written to the user record only, and never echoed back into the log body.

Added descriptions to both fields clarifying:

• Fields only populate when included directly in the signup request body by the calling client
• app_metadata set by pre-registration Actions is applied to the user record but does not appear in the log
• Neither field reflects the final user record state

References

https://auth0team.atlassian.net/browse/ESD-65342
https://auth0team.atlassian.net/jira/servicedesk/projects/DR/queues/custom/98/DR-2834

Testing

Checklist

• [ x] I've read and followed CONTRIBUTING.md.
• [ x] I've tested the site build for this change locally.
• [ x] I've made appropriate docs updates for any code or config changes.
• [ x] I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
auth0	🟢 Ready	View Preview	Aug 6, 2026, 3:14 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
auth0-docs-dev	🟢 Ready	View Preview	Aug 6, 2026, 3:14 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
auth0-docs-staging	🟢 Ready	View Preview	Aug 6, 2026, 3:15 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[hazel-nut]

content seems OK but isn't this file fetched automatically from somewhere? i think we'll need to update it at the source or it will get overwritten on next update.