unable to create task and update task' status, probably to earlier experimenting

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I'm unable to update the Status-property for a node tagged as Task.

I'm a long time user of the app. For one of the graphs, I have been using the Markdown files for a long time. In this time, I have been experimenting quite a bit. I may have set things to the Task- and Status-property. When the database-version became available as a beta, I have switched, eager to test this new version out. Since then I am unable to change the Status-property.

Here's the issue:
- I can create a new task by type on a new node, then add `` #Task`` to it. I cannot create a new task by using "control-enter".
- I can not update the Status (from the existing white circle). Using "control-enter" doesn't do anything. Mouse click on the circle does reveal a pull down menu with the various status's, but selecting any of the options, doesn't do anything. Using "escape" and then "p" then "s" yields a text "Status" but doesn't do anything

### Reproduce the Bug

1. Go to a new bullet.
2. Type ``test #Task``
3. Press control-enter to change status

or

1. Go to a new bullet.
2. Type ``test``
3. Press control-enter to create task

### Expected Behavior

In the first case I expect to toggle the node's Status between the different options.
In the second case I expect a #Task tag to be added, and the prepending of the task status circle.

### Screenshots

### Files

[logseq.com-1785356907284.log](https://github.com/user-attachments/files/30545028/logseq.com-1785356907284.log)

### Browser, Desktop or Mobile Platform Information

MacOS 26.6 (25G72). Logseq Version 2.0.1 (2.0.1).

Problem exists since migrating from Markdown to Database-version

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Reproduce the two failure cases in Logseq 2.0.1 on macOS: creating a task with Control-Enter and changing an existing task's status. Review the attached log file for relevant errors, then trace the task and status handling used by the database version. Done means both reproduction paths create or update the task status as described in Expected Behavior.

Written by the indexing model from the issue text.