What's wrong with this entry?
The task-notification origin kind now carries an optional subkind field. When subkind is "scheduled-trigger", the turn is the automatic firing of a stored scheduled prompt.
- Lets SDK integrations distinguish scheduled task deliveries from other background notifications
- The harness frames scheduled triggers using a
[SCHEDULED TASK - AUTOMATED FIRING OF A CONFIGURED PROMPT]prefix instead of the generic background-notification frame
Schema addition (search for "Present when the delivery is the fired stored prompt of a scheduled task/routine", "[SCHEDULED TASK - AUTOMATED FIRING OF A CONFIGURED PROMPT]")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.