subscriber.argument_invalid: Subscriber passes something other than its event or a field of it

Subscriber passes something other than its event or a field of it.

Area 12, Background work; not declinable; the next step is usually the agent's.

A subscriber passes its event or the event's fields:

example

type Note = Text {    max_length: 200}entity Reminder {    id: Uuid    note: Note    sent: Bool    policy: {        create: [Access.authenticated]        read: [Access.system]        update: [Access.system]    }}type ReminderDue = Event {    reminder_id: Reminder.id}action send_reminder(reminder_id: Reminder.id) fails ReminderNotFound -> Unit {    attempt Reminder.update(reminder_id) {        set: {            sent: true        }    }}subscriber send_due {    on: ReminderDue    run: send_reminder(Reminder.id)}

jadpo checkcheck failed: 1 error, 1 file

error A subscriber passes its event, not Reminder

--> main.jadpo:31:24

   |31 |     run: send_reminder(Reminder.id)   |                        ^^^^^^^^ `Reminder`

reason: A subscriber's run: passes event or fields read through it, as written; the action works out anything else itself.
next: Pass event or a field of it, and move the rest into the action (agent)
rule: subscriber.argument_invalid
help: https://jadpo.dev/docs/errors/subscriber.argument_invalid