Retrieve the recency information for data surfaced by standard capabilities.

This operation enables connectors to indicate how "fresh" the data is that they
surface through their standard capabilities. This is particularly important for
connectors that source data from scheduled dumps, snapshots, or other non-real-time
data sources.

Use Cases

• Data Freshness Assessment: Understand how current the data is from each capability
• Scheduled Data Sources: Handle connectors that read from CSV files, database
  snapshots, or other periodically updated data sources
• Data Quality Monitoring: Track data staleness for compliance and accuracy

Capability Recency Mapping

The response maps each standard capability to an optional datetime indicating when
the data for that capability was last updated:

• Non-null datetime: Indicates the data for this capability is current as of
  the specified timestamp
• null datetime: Indicates the connector cannot determine or does not track
  recency for this capability

Connector Implementation

Connectors should implement this capability when:

• They source data from scheduled dumps or snapshots
• They can provide meaningful recency information

Connectors that always provide "live" data may return null for all capabilities
or omit this capability entirely.

Data Reconciliation