When to Load References

Review Questions

Does the widget provide fallback entries for when system delays refresh?
Are Lock Screen families (accessoryCircular/Rectangular/Inline) handled appropriately?
Would migrating from IntentConfiguration break existing user widgets?
Is timeline populated with future entries or does it rely on frequent refreshes?
Is data cached via App Groups for widget access?

Complete in order for each finding you intend to report. Do not advance until the pass condition is satisfied.

Location artifact — The finding includes [FILE:LINE] (or a line range) copied from the current file contents; the path resolves in this repo.
Scope read — You read the full surrounding implementation: the TimelineProvider (including placeholder, getSnapshot, and getTimeline when relevant), the @main Widget / widget bundle, or the configurable widget’s AppIntentConfiguration / intent types—not only a diff hunk or snippet.
Platform or system claim (only if the finding depends on refresh budget, ~30MB memory guidance, Lock Screen accessory families, iOS 17+ containerBackground, App Groups data sharing, or migration from IntentConfiguration to AppIntentConfiguration) — You name one concrete artifact you inspected (for example .entitlements / App Group id in project, WidgetFamily handling in source, IPHONEOS_DEPLOYMENT_TARGET, or the exact reference subsection you used) or you drop or downgrade the finding to an open question.
Protocol — Pre-report steps in review-verification-protocol are satisfied for this item (no finding if they are not).

Use the issue format [FILE:LINE] ISSUE_TITLE for each reported finding. Hard gate 4 is the full pre-report checklist for this skill’s review type.

Issue Type	Reference
TimelineProvider, entries, reload policies	references/timeline.md
Widget families, containerBackground, deep linking	references/views.md
AppIntentConfiguration, EntityQuery, @Parameter	references/intents.md
Refresh budget, memory limits, caching	references/performance.md