Plan, Confirm, Verify App Changes

Act as a careful operations assistant who edits business apps through their API, using only the access I give you.

Task: Make this change in Todoist: Move every task in the project 'Website Relaunch' that is labelled 'waiting' and overdue by more than 7 days into a new project called 'Stalled', and add the label 'review-friday' to each one. Leave completed tasks and all other projects untouched.. Use only these permissions: Read and write tasks and labels in Todoist only. No access to deleting tasks, changing projects' sharing settings, or account details..

Steps:
1. Restate the task in your own words and list the exact records or fields you expect to touch. Do not change anything yet.
2. Show a numbered plan of every change, with the current value and the new value side by side. Flag anything irreversible or outside Read and write tasks and labels in Todoist only. No access to deleting tasks, changing projects' sharing settings, or account details..
3. Wait for me to reply "approved". If I do not, stop.
4. After approval, make only the approved changes, one at a time, and report any error immediately.
5. Read each changed record back from Todoist and compare it with the plan to confirm it matches.

Output: A plan table before approval. After approval, a short results table with columns Record, Expected, Actual and Status (Match or Mismatch), then a one-line reminder to revoke the API key.

# Step 1: Task restatement (nothing changed yet) **My understanding:** In Todoist, find every active (not completed) task in the project **Website Relaunch** that has the label **waiting** and a due date more than 7 days in the past. Today is 2026-10-26, so the cutoff is a due date **before 2026-10-19**. Move those tasks into a project called **Stalled** and add the label **review-friday**, keeping any labels they already have. **Records and fields I expect to touch** (only on matching tasks): - `project_id`: Website Relaunch → Stalled - `labels`: existing labels (including `waiting`) plus `review-friday` - The label `review-friday` itself, if it doesn't exist yet - The project `Stalled`, if it doesn't exist yet **Not touched:** completed tasks, tasks in other projects, tasks without `waiting`, tasks due on or after 2026-10-19, tasks with no due date, project sharing, and account details. # Step 2: Plan **I have not read any Todoist data yet.** This session has no Todoist API token or connection, so I can't list the matching tasks or their current values. I won't guess at them. Once you give me read access, I'll fetch the tasks and fill in this table with real task IDs. | # | Record | Field | Current value | New value | |---|---|---|---|---| | 1 | Project "Stalled" | existence | Unknown, to be checked | Created if missing (see flag A) | | 2 | Label `review-friday` | existence | Unknown, to be checked | Created if missing | | 3…n | Each matching task (ID and title to come) | `project_id` | Website Relaunch | Stalled | | 3…n | Same task | `labels` | e.g. `[waiting, …existing]` | `[waiting, …existing, review-friday]` | **Filter:** `project = Website Relaunch`, label `waiting`, `is_completed = false`, `due.date < 2026-10-19`. **Flags:** - **A. Creating a project is probably outside your permissions.** You granted read and write on tasks and labels only. Creating "Stalled" is a project-level write. The safest option is for you to create an empty **Stalled** project yourself, and I'll then only move tasks into it. Otherwise, tell me explicitly that I may create it. - **B. Moving tasks is reversible.** I'll record each task's original project and labels so I can move it back. Nothing is deleted. Moving a task drops it from its section in Website Relaunch, and I can't restore the section automatically. - **C. Label updates replace the whole list.** I'll send the full existing labels plus `review-friday`, so `waiting` and the others stay. - **D. Subtasks.** Moving a parent task also moves its subtasks, even if they don't match the filter. I'll list any such subtasks in the final plan, and you can decide whether to include them. - **E. Recurring tasks.** If any matching tasks are recurring, I'll flag them, since their due dates may behave differently. - **F. Edge cases.** Tasks due exactly 2026-10-19 (7 days overdue) are excluded. Tasks with no due date are excluded. # What I need from you 1. A Todoist API token with the scoped access above, or confirmation of how I should connect, so I can do read-only lookups first. 2. Your answer on flag A: will you create "Stalled", or may I? I'll then return with the real task-by-task table and wait for your reply of **"approved"** before changing anything.