Task 36761905 (Feature 802a8515): a newly created quest definition must materialize its future instances so it reaches the board immediately.
One-line core change in create_quest_definition: await regenerate_for_definition(database, snapshot.definition.id) after the DAO write. 1986 passed. Several existing tests encoded the bug (create writes no instances) as expected behaviour and were updated to end-date their seed rules / clear the table before the gated walk; details in the developer report.
Task 36761905 (Feature 802a8515): a newly created quest definition must materialize its future instances so it reaches the board immediately.
One-line core change in create_quest_definition: await regenerate_for_definition(database, snapshot.definition.id) after the DAO write. 1986 passed. Several existing tests encoded the bug (create writes no instances) as expected behaviour and were updated to end-date their seed rules / clear the table before the gated walk; details in the developer report.
create_quest_definition persisted the rule, definition, assignees and
windows but never called regenerate_for_definition, unlike edit, assign,
unassign and activate. A new task therefore had no quest_instances rows
and stayed off the panel board until an unrelated write regenerated it.
Call regenerate_for_definition after the DAO write, using the host
clock and the default horizon, and add a test that a created weekly
definition has only today-or-later instances.
Update test fixtures that relied on create writing no instances: close
the seeded one-day rules with end_date, clear the table before the gated
materialize walk, and adjust the admin regenerate tests to the new
create behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Task 36761905 (Feature 802a8515): a newly created quest definition must materialize its future instances so it reaches the board immediately.
One-line core change in create_quest_definition: await regenerate_for_definition(database, snapshot.definition.id) after the DAO write. 1986 passed. Several existing tests encoded the bug (create writes no instances) as expected behaviour and were updated to end-date their seed rules / clear the table before the gated walk; details in the developer report.
Independent Codex gpt-5.6-terra review completed for this exact commit.