feat: meta-type presets and TodoList system database

[kooksee]

Summary

• Add built-in meta-type starter presets and migrate TodoList from a page meta type to a dedicated system records database (systemKind: todo_list).
• Ship TodoList workspace UI: sidebar quick add/recent tasks, List/Table/Board views, right-side detail panel, tags/assignees/collaborator fields, and per-record due date reminders via Scheduled Tasks.
• Polish list interaction: compact rows, single detail surface (no todo-list modal), keyboard navigation (Esc, ↑/↓), and editable due reminders.

Test plan

• Open TodoList from sidebar; verify list loads with Default / By status / By tags / Table / List views
• In List view: click row or Detail → right panel updates; ↑/↓ switches tasks; Esc closes panel
• Quick-add task from list footer and sidebar; verify recent tasks in sidebar
• Set Target date on a task → enable due reminder; edit schedule and delete reminder
• Create tasks from Table/Board views (no modal on todo-list page)
• Run npm run test in packages/client (todo-list-system tests)
• Package desktop with LOCAL_ONLY=true npm run package and smoke-test

Made with Cursor

[gemini-code-assist]

Code Review

This pull request introduces a built-in TodoList system database along with several starter meta-type presets (such as Bookmark, Project, and Issue) to enhance workspace initialization. It also integrates the TodoList into the UI sidebar, settings, and navigation, and adds a due date reminder feature. The review feedback highlights opportunities to improve performance by avoiding sequential awaits in a loop, prevent potential runtime errors by adding defensive checks for undefined fields, support both string and date types for target dates, and avoid unnecessary re-renders by defining a stable fallback object outside of the component.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Running sequential await database updates inside a for loop can be a significant performance bottleneck if there are many records. Consider batching these updates or processing them in parallel with a concurrency limit (e.g., using a batch update API or chunking with Promise.all).

[gemini-code-assist]

To prevent potential runtime errors, add a defensive check to ensure draft.fields is defined before attempting to delete properties from it.

      await workspace.nodes.updateNode(row.id, (draft) => {
        if (draft.type !== 'record') {
          return draft;
        }

        if (draft.fields) {
          delete draft.fields[TODO_LIST_FIELD_IDS.assignee];
        }
        return draft;
      });

[gemini-code-assist]

Add a defensive check to ensure draft.fields is initialized before setting or deleting properties on it.

    await workspace.nodes.updateNode(row.id, (draft) => {
      if (draft.type !== 'record') {
        return draft;
      }

      if (!draft.fields) {
        draft.fields = {};
      }

      if (matchedUserId) {
        draft.fields[TODO_LIST_FIELD_IDS.assignee] = {
          type: 'string_array',
          value: [matchedUserId],
        };
      } else {
        delete draft.fields[TODO_LIST_FIELD_IDS.assignee];
      }

      return draft;
    });

[gemini-code-assist]

The hasTargetDate check strictly requires value.type === 'string'. However, for a date field, the value type might be 'date' or 'string'. Relaxing this check to support both 'string' and 'date' types ensures the due date reminder can be enabled correctly.

Suggested change

	const hasTargetDate = (record: LocalRecordNode): boolean => {
	const value = record.fields[TODO_LIST_FIELD_IDS.targetDate];
	return Boolean(
	value &&
	value.type === 'string' &&
	typeof value.value === 'string' &&
	value.value.length > 0
	);
	};
	const hasTargetDate = (record: LocalRecordNode): boolean => {
	const value = record.fields[TODO_LIST_FIELD_IDS.targetDate];
	return Boolean(
	value &&
	(value.type === 'string' || value.type === 'date') &&
	typeof value.value === 'string' &&
	value.value.length > 0
	);
	};

[gemini-code-assist]

Passing an inline fallback object to useRecordField causes a new object reference to be created on every render. If useRecordField has field in its dependency array, this will trigger unnecessary effect re-runs and re-renders. Define the fallback object as a stable constant outside the component instead (e.g., const FALLBACK_REMINDERS_FIELD = { id: REMINDERS_RELATION_FIELD_ID, type: 'relation' as const, name: 'Reminders', index: 'z', databaseId: '' };).

  const { value, setValue } = useRecordField({
    field:
      remindersField?.type === 'relation'
        ? remindersField
        : FALLBACK_REMINDERS_FIELD,
  });