AI report example: `explore` nested under `context:`

[dfliess]

I've noticed that the AI report example in the reports reference
nests the explore under context::

data:
  ai:
    prompt: "Analyze key metrics and identify significant changes"
    context:
      explore: my_explore

But the AI resolver doesn't seem to have that property, aiProps
declares explore as a top-level field, and anything else lands in UnusedFields. When I deployed the documented example it reconciled clean and ran fine, so at first I assumed it worked. It doesn't: the explore is dropped, and unknown resolver properties are downgraded to a warning unless StrictResolverProps is set
(resolver.go), so nothing surfaces it.

I’m not sure this is purely cosmetic, though. It seems the explore is what ties the time range to the data.
With it, latest resolves against the metrics view
(ai.go#L311-L315).
Without it, latest falls back to the report's execution time
(ai.go#L318-L336).
So 1M as of latest/M quietly stops meaning "the last complete month of data" and starts
meaning "the last complete month by the clock".

Am I reading this right?

[pjain1]

@dfliess Thanks for the report. You are correct about context is not supported, the example is wrong, it was decided to have explore directly on top level. I will fix this. Regarding use of latest data - irrespective of explore is set or not, relative time range is always resolved against report execution time. We have watermark: inherit property for non-AI reports to override it, let me see if it makes sense for AI reports as well.