taskcheck 1.2.0__tar.gz → 1.3.0__tar.gz

taskcheck-1.3.0/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.4
+Name: taskcheck
+Version: 1.3.0
+Summary: Automatic scheduler for taskwarrior
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: appdirs>=1.4.4
+Requires-Dist: google-api-python-client>=2.198.0
+Requires-Dist: google-auth>=2.56.2
+Requires-Dist: google-auth-oauthlib>=1.2.2
+Requires-Dist: icalendar>=6.0.1
+Requires-Dist: random-unicode-emoji>=2.8
+Requires-Dist: requests>=2.32.3
+Requires-Dist: rich>=13.9.4
+
+![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
+
+A Taskwarrior scheduler for people who want a realistic plan, not a manual to-do list.
+It turns tasks, working hours, and calendar blocks into an actionable schedule — then keeps due dates visible.
+
+Use it if you want to:
+- stop guessing what to do next
+- fit tasks into real availability
+- be sure your long-time plan won't go overdue
+- keep Taskwarrior as the source of truth
+
+> [!IMPORTANT]
+> This repo is actively maintained again
+
+## Features
+
+- ✨ Auto-schedule tasks from working hours + calendar blocks
+- 🧭 Support complex working-hour maps
+- ⏱️ Consider urgency, due dates, and dependencies
+- 🧪 Dry-run mode to preview changes
+- 🧠 Auto-adjust urgency when deadlines cannot be met
+- 🔄 Force-refresh iCal calendars
+- 📊 Custom reports for planned and unplanned tasks
+- 🎨 Report styling with emoji and extra attributes
+- 🗓️ Block time with iCal or Google Calendar, including all-day events
+
+## Quick start
+
+1. `pipx install taskcheck`
+2. `taskcheck --install` ← setup only
+3. add `estimated` + `time_map` UDAs
+4. edit `~/.config/task/taskcheck.toml` (see [Reference](#Reference))
+5. `taskcheck --schedule`
+
+## How it works
+
+Taskcheck reads your pending and waiting tasks, estimates when each one can be worked on, and writes back a schedule.
+It respects:
+- your working hours
+- task duration estimates
+- calendar events and vacations from iCal / Google Calendar
+- task urgency and due dates
+
+It updates Taskwarrior with:
+- `scheduled` → when work should start
+- `completion_date` → when work is expected to finish
+- a warning when a task will miss its due date
+
+### Required UDAs
+
+- `estimated`: expected duration in hours
+- `time_map`: which working-hour profile applies to the task, for example `work` or `weekend`
+
+Example:
+
+```toml
+[time_maps.work]
+monday = [[9, 12.30], [14, 17]]
+tuesday = [[9, 12.30], [14, 17]]
+```
+
+### Reports
+
+- `taskcheck -r today` → tasks planned for today
+- `taskcheck -r 1w` → tasks planned for the next week
+
+## Reference
+
+📚 Full reference: [REFERENCE.md](REFERENCE.md)
+
+In short:
+- `taskcheck --install` is interactive
+- it installs required Taskwarrior settings if you confirm the first prompt
+- it installs optional urgency/report tuning if you confirm the second prompt
+- it can also create the default config file if you confirm the third prompt
+- it does **not** schedule tasks or fetch calendars
+- scheduling happens with `taskcheck --schedule`
+- all flags/config keys/settings are documented in `REFERENCE.md`
+
+## Algorithm
+
+The algorithm simulates a workday one chunk at a time.
+
+For each day starting from today, it sorts tasks by urgency and picks the most urgent task that fits the available time.
+It assigns a small block of work, then recomputes urgency exactly as Taskwarrior would on that day.
+If urgency changes, the next task choice can change too.
+
+For `today`, taskcheck skips past hours.
+
+The default work chunk is 2 hours (or less if the task is shorter); you can tune it with the Taskwarrior UDA `min_block`.
+
+If a task would finish after its `due_date`, taskcheck retries. It keeps that task's current non-due urgency weight, then lowers the weight by 0.1 only for tasks that have not missed a deadline. Due urgency is never reduced. Retries stop when deadlines are respected or unflagged tasks reach a weight of 0.
+
+## Tips and Tricks
+
+- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
+- You can see tasks that you can execute now with the `task ready` report.
+
+See the reference section above for flags, config keys, and installed Taskwarrior settings.

taskcheck-1.3.0/README.md

@@ -0,0 +1,99 @@
+![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
+
+A Taskwarrior scheduler for people who want a realistic plan, not a manual to-do list.
+It turns tasks, working hours, and calendar blocks into an actionable schedule — then keeps due dates visible.
+
+Use it if you want to:
+- stop guessing what to do next
+- fit tasks into real availability
+- be sure your long-time plan won't go overdue
+- keep Taskwarrior as the source of truth
+
+> [!IMPORTANT]
+> This repo is actively maintained again
+
+## Features
+
+- ✨ Auto-schedule tasks from working hours + calendar blocks
+- 🧭 Support complex working-hour maps
+- ⏱️ Consider urgency, due dates, and dependencies
+- 🧪 Dry-run mode to preview changes
+- 🧠 Auto-adjust urgency when deadlines cannot be met
+- 🔄 Force-refresh iCal calendars
+- 📊 Custom reports for planned and unplanned tasks
+- 🎨 Report styling with emoji and extra attributes
+- 🗓️ Block time with iCal or Google Calendar, including all-day events
+
+## Quick start
+
+1. `pipx install taskcheck`
+2. `taskcheck --install` ← setup only
+3. add `estimated` + `time_map` UDAs
+4. edit `~/.config/task/taskcheck.toml` (see [Reference](#Reference))
+5. `taskcheck --schedule`
+
+## How it works
+
+Taskcheck reads your pending and waiting tasks, estimates when each one can be worked on, and writes back a schedule.
+It respects:
+- your working hours
+- task duration estimates
+- calendar events and vacations from iCal / Google Calendar
+- task urgency and due dates
+
+It updates Taskwarrior with:
+- `scheduled` → when work should start
+- `completion_date` → when work is expected to finish
+- a warning when a task will miss its due date
+
+### Required UDAs
+
+- `estimated`: expected duration in hours
+- `time_map`: which working-hour profile applies to the task, for example `work` or `weekend`
+
+Example:
+
+```toml
+[time_maps.work]
+monday = [[9, 12.30], [14, 17]]
+tuesday = [[9, 12.30], [14, 17]]
+```
+
+### Reports
+
+- `taskcheck -r today` → tasks planned for today
+- `taskcheck -r 1w` → tasks planned for the next week
+
+## Reference
+
+📚 Full reference: [REFERENCE.md](REFERENCE.md)
+
+In short:
+- `taskcheck --install` is interactive
+- it installs required Taskwarrior settings if you confirm the first prompt
+- it installs optional urgency/report tuning if you confirm the second prompt
+- it can also create the default config file if you confirm the third prompt
+- it does **not** schedule tasks or fetch calendars
+- scheduling happens with `taskcheck --schedule`
+- all flags/config keys/settings are documented in `REFERENCE.md`
+
+## Algorithm
+
+The algorithm simulates a workday one chunk at a time.
+
+For each day starting from today, it sorts tasks by urgency and picks the most urgent task that fits the available time.
+It assigns a small block of work, then recomputes urgency exactly as Taskwarrior would on that day.
+If urgency changes, the next task choice can change too.
+
+For `today`, taskcheck skips past hours.
+
+The default work chunk is 2 hours (or less if the task is shorter); you can tune it with the Taskwarrior UDA `min_block`.
+
+If a task would finish after its `due_date`, taskcheck retries. It keeps that task's current non-due urgency weight, then lowers the weight by 0.1 only for tasks that have not missed a deadline. Due urgency is never reduced. Retries stop when deadlines are respected or unflagged tasks reach a weight of 0.
+
+## Tips and Tricks
+
+- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
+- You can see tasks that you can execute now with the `task ready` report.
+
+See the reference section above for flags, config keys, and installed Taskwarrior settings.

{taskcheck-1.2.0 → taskcheck-1.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "taskcheck"
-version = "1.2.0"
+version = "1.3.0"
 description = "Automatic scheduler for taskwarrior"
 readme = "README.md"
 requires-python = ">=3.11"

{taskcheck-1.2.0 → taskcheck-1.3.0}/taskcheck/__main__.py

@@ -52,7 +52,7 @@ arg_parser.add_argument(
     dest="auto_adjust_urgency",
     action="store_false",
     default=True,
-    help="Disable automatic reduction of urgency weight when tasks cannot be completed on time. (Enabled by default, meaning automatic reduction will occur.)",
+    help="Disable automatic per-task urgency adjustment when tasks cannot be completed on time.",
 )
 arg_parser.add_argument(
     "--add-google-calendar",

{taskcheck-1.2.0 → taskcheck-1.3.0}/taskcheck/parallel.py

@@ -111,6 +111,7 @@ def check_tasks_parallel(
     urgency_coefficients = get_urgency_coefficients(taskrc=taskrc)
 
     current_weight = initial_weight_urgency
+    frozen_weights = {}
 
     # Always re-initialize task_info inside the loop to avoid mutated state
     task_info_original = initialize_task_info(
@@ -132,6 +133,7 @@ def check_tasks_parallel(
                 urgency_coefficients,
                 verbose,
                 current_weight,
+                frozen_weights,
             )
 
         # Check if any tasks cannot be completed on time
@@ -159,7 +161,9 @@ def check_tasks_parallel(
         if not tasks_overdue or not auto_adjust_urgency:
             break
 
-        # If we have overdue tasks and auto-adjust is enabled, reduce weight and try again
+        for task in tasks_overdue:
+            frozen_weights.setdefault(task["uuid"], current_weight)
+
         if verbose:
             console.print(
                 f"[red]{len(tasks_overdue)} task(s) cannot be completed on time[/red]"
@@ -175,12 +179,12 @@ def check_tasks_parallel(
         if tasks_overdue:
             # We tried to adjust but still have overdue tasks
             console.print(
-                "[red]Warning: cannot find a solution even with urgency weight 0.0[/red]"
+                "[red]Warning: cannot find a solution after per-task urgency adjustment[/red]"
             )
         else:
             # We successfully resolved overdue tasks by adjusting weight
             console.print(
-                f"[green]Final urgency weight: {max(current_weight, 0.0):.1f}[/green]"
+                f"[green]Resolved deadlines with per-task urgency adjustment[/green]"
             )
 
     if dry_run:
@@ -275,6 +279,7 @@ def allocate_time_for_day(
     urgency_coefficients,
     verbose,
     weight_urgency,
+    frozen_weights=None,
 ):
     date = datetime.today().date() + timedelta(days=day_offset)
     total_available_hours = compute_total_available_hours(task_info, day_offset)
@@ -287,7 +292,13 @@ def allocate_time_for_day(
     tasks_remaining = prepare_tasks_remaining(task_info, day_offset)
 
     while day_remaining_hours > 0 and tasks_remaining:
-        recompute_urgencies(tasks_remaining, urgency_coefficients, date, weight_urgency)
+        recompute_urgencies(
+            tasks_remaining,
+            urgency_coefficients,
+            date,
+            weight_urgency,
+            frozen_weights,
+        )
         sorted_task_ids = sorted(
             tasks_remaining.keys(),
             key=lambda x: tasks_remaining[x]["urgency"],
@@ -423,8 +434,11 @@ def update_urgency(info, urgency_key, urgency_compute_fn, urgency_coefficients,
     info["urgency"] = info["urgency"] - old_urgency + urgency_value
 
 
-def recompute_urgencies(tasks_remaining, urgency_coefficients, date, weight_urgency):
-    """Recompute urgency simulating that today is `date`"""
+def recompute_urgencies(
+    tasks_remaining, urgency_coefficients, date, weight_urgency, frozen_weights=None
+):
+    """Recompute urgency simulating that today is `date`."""
+    frozen_weights = frozen_weights or {}
     # Recompute estimated urgencies as before
     for info in tasks_remaining.values():
         # Update estimated urgency
@@ -438,7 +452,8 @@ def recompute_urgencies(tasks_remaining, urgency_coefficients, date, weight_urge
 
         # Apply weights to create a combined score
         base_urgency = info["urgency"] - info["due_urgency"]
-        base_urgency *= weight_urgency
+        task_weight = frozen_weights.get(info["task"]["uuid"], weight_urgency)
+        base_urgency *= task_weight
         # Always add due_urgency, only weight estimated and age
         weighted_urgency = base_urgency + info["due_urgency"]
         info["urgency"] = weighted_urgency

taskcheck-1.3.0/taskcheck.egg-info/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.4
+Name: taskcheck
+Version: 1.3.0
+Summary: Automatic scheduler for taskwarrior
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: appdirs>=1.4.4
+Requires-Dist: google-api-python-client>=2.198.0
+Requires-Dist: google-auth>=2.56.2
+Requires-Dist: google-auth-oauthlib>=1.2.2
+Requires-Dist: icalendar>=6.0.1
+Requires-Dist: random-unicode-emoji>=2.8
+Requires-Dist: requests>=2.32.3
+Requires-Dist: rich>=13.9.4
+
+![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
+
+A Taskwarrior scheduler for people who want a realistic plan, not a manual to-do list.
+It turns tasks, working hours, and calendar blocks into an actionable schedule — then keeps due dates visible.
+
+Use it if you want to:
+- stop guessing what to do next
+- fit tasks into real availability
+- be sure your long-time plan won't go overdue
+- keep Taskwarrior as the source of truth
+
+> [!IMPORTANT]
+> This repo is actively maintained again
+
+## Features
+
+- ✨ Auto-schedule tasks from working hours + calendar blocks
+- 🧭 Support complex working-hour maps
+- ⏱️ Consider urgency, due dates, and dependencies
+- 🧪 Dry-run mode to preview changes
+- 🧠 Auto-adjust urgency when deadlines cannot be met
+- 🔄 Force-refresh iCal calendars
+- 📊 Custom reports for planned and unplanned tasks
+- 🎨 Report styling with emoji and extra attributes
+- 🗓️ Block time with iCal or Google Calendar, including all-day events
+
+## Quick start
+
+1. `pipx install taskcheck`
+2. `taskcheck --install` ← setup only
+3. add `estimated` + `time_map` UDAs
+4. edit `~/.config/task/taskcheck.toml` (see [Reference](#Reference))
+5. `taskcheck --schedule`
+
+## How it works
+
+Taskcheck reads your pending and waiting tasks, estimates when each one can be worked on, and writes back a schedule.
+It respects:
+- your working hours
+- task duration estimates
+- calendar events and vacations from iCal / Google Calendar
+- task urgency and due dates
+
+It updates Taskwarrior with:
+- `scheduled` → when work should start
+- `completion_date` → when work is expected to finish
+- a warning when a task will miss its due date
+
+### Required UDAs
+
+- `estimated`: expected duration in hours
+- `time_map`: which working-hour profile applies to the task, for example `work` or `weekend`
+
+Example:
+
+```toml
+[time_maps.work]
+monday = [[9, 12.30], [14, 17]]
+tuesday = [[9, 12.30], [14, 17]]
+```
+
+### Reports
+
+- `taskcheck -r today` → tasks planned for today
+- `taskcheck -r 1w` → tasks planned for the next week
+
+## Reference
+
+📚 Full reference: [REFERENCE.md](REFERENCE.md)
+
+In short:
+- `taskcheck --install` is interactive
+- it installs required Taskwarrior settings if you confirm the first prompt
+- it installs optional urgency/report tuning if you confirm the second prompt
+- it can also create the default config file if you confirm the third prompt
+- it does **not** schedule tasks or fetch calendars
+- scheduling happens with `taskcheck --schedule`
+- all flags/config keys/settings are documented in `REFERENCE.md`
+
+## Algorithm
+
+The algorithm simulates a workday one chunk at a time.
+
+For each day starting from today, it sorts tasks by urgency and picks the most urgent task that fits the available time.
+It assigns a small block of work, then recomputes urgency exactly as Taskwarrior would on that day.
+If urgency changes, the next task choice can change too.
+
+For `today`, taskcheck skips past hours.
+
+The default work chunk is 2 hours (or less if the task is shorter); you can tune it with the Taskwarrior UDA `min_block`.
+
+If a task would finish after its `due_date`, taskcheck retries. It keeps that task's current non-due urgency weight, then lowers the weight by 0.1 only for tasks that have not missed a deadline. Due urgency is never reduced. Retries stop when deadlines are respected or unflagged tasks reach a weight of 0.
+
+## Tips and Tricks
+
+- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
+- You can see tasks that you can execute now with the `task ready` report.
+
+See the reference section above for flags, config keys, and installed Taskwarrior settings.

{taskcheck-1.2.0 → taskcheck-1.3.0}/tests/test_parallel.py

@@ -287,6 +287,32 @@ class TestWeightConfiguration:
         recompute_urgencies(tasks_remaining, coeffs, date, 0.7)
         assert tasks_remaining["task-1"]["urgency"] >= tasks_remaining["task-1"]["due_urgency"]
 
+    def test_recompute_urgencies_uses_frozen_weight_per_task(self):
+        tasks_remaining = {
+            uuid: {
+                "task": {"uuid": uuid, "id": index, "entry": "20240101T000000Z"},
+                "urgency": 10.0,
+                "estimated_urgency": 5.0,
+                "due_urgency": 0.0,
+                "age_urgency": 0.0,
+                "remaining_hours": 2.0,
+                "started": False,
+            }
+            for index, uuid in enumerate(("frozen", "unfrozen"), start=1)
+        }
+        coeffs = UrgencyCoefficients({"P2H": 5.0}, False, 0, 365, 0, 0)
+
+        recompute_urgencies(
+            tasks_remaining,
+            coeffs,
+            datetime(2024, 1, 1).date(),
+            0.2,
+            frozen_weights={"frozen": 0.7},
+        )
+
+        assert tasks_remaining["frozen"]["urgency"] == 7.0
+        assert tasks_remaining["unfrozen"]["urgency"] == 2.0
+
     def test_recompute_urgencies_inherit_and_cycle(self):
         tasks_remaining = {
             "a": {"task": {"uuid": "a", "depends": ["b"]}, "urgency": 1.0, "estimated_urgency": 0.0, "due_urgency": 0.0, "age_urgency": 0.0, "remaining_hours": 1.0, "started": False},
@@ -503,7 +529,7 @@ class TestAutoAdjustUrgency:
         with patch("taskcheck.parallel.console.print") as mock_console_print:
             check_tasks_parallel(sample_config, verbose=True, taskrc=test_taskrc, auto_adjust_urgency=True)
             messages = [" ".join(str(arg).lower() for arg in call.args) for call in mock_console_print.call_args_list]
-            assert any("final urgency weight" in msg or "cannot find a solution" in msg for msg in messages)
+            assert any("per-task urgency adjustment" in msg for msg in messages)
 
     @patch("taskcheck.parallel.get_calendars")
     @patch("taskcheck.parallel.get_tasks")

taskcheck-1.2.0/PKG-INFO

@@ -1,232 +0,0 @@
-Metadata-Version: 2.4
-Name: taskcheck
-Version: 1.2.0
-Summary: Automatic scheduler for taskwarrior
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-Requires-Dist: appdirs>=1.4.4
-Requires-Dist: google-api-python-client>=2.198.0
-Requires-Dist: google-auth>=2.56.2
-Requires-Dist: google-auth-oauthlib>=1.2.2
-Requires-Dist: icalendar>=6.0.1
-Requires-Dist: random-unicode-emoji>=2.8
-Requires-Dist: requests>=2.32.3
-Requires-Dist: rich>=13.9.4
-
-<div align="center">
-  
-```
-########    ###     ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-   ##      ## ##   ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##     ##   ##  ##       ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ##  ######  #####    ##       ######### ######   ##       #####    
-   ##    #########       ## ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ## ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##    ##     ##  ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-```
-
-> _A non-AI automatic scheduler for taskwarrior (i.e. alternative to skedpal / timehero / flowsavvy / reclaim / trevor / motion)_
-
-  ![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
-
-</div>
-
-This is a taskwarrior extension that automatically schedules your tasks based on your working hours,
-estimated time, and calendar events, finding an optimal time to work on each task and match all your
-deadlines.
-
-> [!IMPORTANT]
-> This repo is actively maintained again
-
-## Features
-
-- [x] **Use arbitrarily complex time maps for working hours**
-- [x] Block scheduling time using iCal calendars (meetings, vacations, holidays, etc.)
-- [x] **Parallel scheduling algorithm for multiple tasks, considering urgency and dependencies**
-- [x] Dry-run mode: preview scheduling without modifying your Taskwarrior database
-- [x] Custom urgency weighting for scheduling (via CLI or config)
-- [x] **Auto-fix scheduling to match due dates**
-- [x] Force update of iCal calendars, bypassing cache
-- [x] Simple, customizable reports for planned and unplanned tasks
-- [x] Emoji and attribute customization in reports
-- [ ] Use Google API to access calendars
-
-## Install
-
-1. `pipx install taskcheck`
-2. `taskcheck --install`
-
-## How does it work
-
-This extension parses your pending and waiting tasks sorted decreasingly by urgency and tries to schedule them in the future.
-It considers their estimated time to schedule all tasks starting from the most urgent one.
-
-#### UDAs
-
-Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
-the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
-that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
-The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
-file of taskcheck. For instance:
-
-```toml
-[time_maps]
-# get an error)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-# ...
-```
-
-#### They say it's an "AI"
-
-Taskcheck will also parse online iCal calendars (Google, Apple, etc.) and will match them with your time maps.
-It will then modify the Taskwarrior tasks by adding the `completion_date` attribute with the expected
-date of completion and the `scheduled` attribute with the date in which the task is expected to
-start.
-
-It will also print a red line for every task whose `completion_date` is after its `due_date`.
-
-In general, it is recommended to run taskcheck rather frequently and at least once at the beginning
-of your working day.
-
-#### Reports
-
-You can also print simple reports that exploit the `scheduling` UDA filled by Taskcheck to grasp
-how much time you have to work on which task in which day. For
-instance:
-
-- `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week
-
-## Configuration
-
-`taskcheck --install` allows you to create required and recommended configurations for
-Taskwarrior. It will also generate a default configuration file for taskcheck.
-
-Below is an example of a taskcheck configuration file, with all relevant options:
-
-```toml
-[time_maps]
-# Define your working hours for each named time map (in 24h format, e.g. 9.5 = 9:30)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-wednesday = [[9, 12.30], [14, 17]]
-thursday = [[9, 12.30], [14, 17]]
-friday = [[9, 12.30], [14, 17]]
-
-[time_maps.weekend]
-saturday = [[9, 12.30]]
-sunday = [[9, 12.30]]
-
-[scheduler]
-days_ahead = 1000         # How far to go with the schedule (lower values = faster computation)
-weight_urgency = 1.0      # Default weight for urgency in scheduling (overridable via CLI)
-# if weight_urgency is set to 0, only due urgency is considered
-# by default, this factor is automatically reduced if some task cannot be scheduled in time,
-# leading to tasks with due dates being prioritized (see --no-auto-adjust-urgency)
-
-[calendars]
-# iCal calendars can be used to block your time and make the scheduling more precise
-[calendars.1]
-url = "https://your/url/to/calendar.ics"
-expiration = 0.08         # In hours (0.08 hours ≈ 5 minutes)
-timezone = "Europe/Rome"  # If set, force timezone for this calendar (see TZ database)
-
-[calendars.holidays]
-url = "https://www.officeholidays.com/ics-clean/italy/milan"
-event_all_day_is_blocking = true
-expiration = 720          # In hours (720 hours = 30 days)
-
-[report]
-include_unplanned = true
-additional_attributes = ["estimated", "due", "urgency"]           # Extra attributes to show in the report
-additional_attributes_unplanned = ["due", "urgency"]               # Extra attributes for unplanned tasks
-unplanned_max_due = "30d"       # Only show unplanned tasks due within this Taskwarrior-relative horizon; tasks without a due date are always shown
-emoji_keywords = {"meet"=":busts_in_silhouette:", "review"=":mag_right:"} # Map keywords to emoji
-```
-
-### Configuration Options
-
-- **[scheduler]**
-  - `days_ahead`: How many days ahead to schedule tasks.
-  - `weight_urgency`: Default weight for urgency in scheduling (0.0 to 1.0). Can be overridden with `--urgency-weight`.
-- **[calendars]**
-  - `url`: iCal URL to block time.
-  - `expiration`: Cache expiration in hours.
-  - `timezone`: (Optional) Force a timezone for this calendar.
-  - `event_all_day_is_blocking`: (Optional, bool) Treat all-day events as blocking.
-- **[report]**
-  - `include_unplanned`: Show unplanned tasks in a separate section.
-  - `additional_attributes`: Extra columns to show in the report.
-  - `additional_attributes_unplanned`: Extra columns for unplanned tasks.
-  - `unplanned_max_due`: Optional Taskwarrior-relative horizon (for example `30d`) for dated unplanned tasks. Tasks without a due date are always shown; omitting this setting applies no limit.
-  - `emoji_keywords`: Map keywords in task descriptions to emoji.
-
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency.
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
-skip all the available slots until 12 pm.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
-
-After the scheduling is done, if any task has a `completion_date` after its `due_date`, the
-`weight_urgency` factor is reduced by 0.1 and the scheduling is repeated, until all tasks
-are scheduled before their due dates or the `weight_urgency` factor reaches 0.
-
-## Tips and Tricks
-
-- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
-- You can see tasks that you can execute now with the `task ready` report.
-
-## CLI Options
-
-```
-usage: __main__.py [-h] [-v] [-i] [-r REPORT] [-s] [-f] [--taskrc TASKRC] [--urgency-weight URGENCY_WEIGHT] [--dry-run] [--no-auto-adjust-urgency]
-
-options:
-  -h, --help            show this help message and exit
-  -v, --verbose         Increase output verbosity.
-  -i, --install         Install the UDAs, required settings, and default config file.
-  -r REPORT, --report REPORT
-                        Generate a report of the tasks based on the scheduling; can be any Taskwarrior datetime specification (e.g. today, tomorrow, eom, som, 1st, 2nd, etc.). It is considered as `by`, meaning that the report will be
-                        generated for all the days until the specified date and including it.
-  -s, --schedule        Perform the scheduling algorithm, giving a schedule and a scheduling UDA and alerting for not completable tasks
-  -f, --force-update    Force update of all ical calendars by ignoring cache expiration
-  --taskrc TASKRC       Set custom TASKRC directory for debugging purposes
-  --urgency-weight URGENCY_WEIGHT
-                        Weight for urgency in scheduling (0.0 to 1.0), overrides config value. When 1.0, the whole Taskwarrior urgency is used for scheduling. When 0.0, the Taskwarrior urgency is reduced to only due urgency.
-  --dry-run             Perform scheduling without modifying the Taskwarrior database, useful for testing
-  --no-auto-adjust-urgency
-                        Disable automatic reduction of urgency weight … (default: enabled)
-```
-
-### Examples
-
-- `taskcheck --schedule`  
-  Run the scheduler and update your Taskwarrior tasks.
-- `taskcheck --schedule --dry-run`  
-  Preview the schedule without modifying your database.
-- `taskcheck --schedule --urgency-weight 0.5`  
-  Use a custom urgency weighting for this run.
-- `taskcheck --schedule --no-auto-adjust-urgency`  
-  Avoid the automatically reduction of urgency weight if tasks can't be scheduled before their due dates.
-- `taskcheck --report today`  
-  Show the schedule for today.
-- `taskcheck --report 1w`  
-  Show the schedule for the next week.
-- `taskcheck --force-update`  
-  Force refresh of all iCal calendars, ignoring cache.

taskcheck-1.2.0/README.md

@@ -1,217 +0,0 @@
-<div align="center">
-  
-```
-########    ###     ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-   ##      ## ##   ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##     ##   ##  ##       ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ##  ######  #####    ##       ######### ######   ##       #####    
-   ##    #########       ## ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ## ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##    ##     ##  ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-```
-
-> _A non-AI automatic scheduler for taskwarrior (i.e. alternative to skedpal / timehero / flowsavvy / reclaim / trevor / motion)_
-
-  ![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
-
-</div>
-
-This is a taskwarrior extension that automatically schedules your tasks based on your working hours,
-estimated time, and calendar events, finding an optimal time to work on each task and match all your
-deadlines.
-
-> [!IMPORTANT]
-> This repo is actively maintained again
-
-## Features
-
-- [x] **Use arbitrarily complex time maps for working hours**
-- [x] Block scheduling time using iCal calendars (meetings, vacations, holidays, etc.)
-- [x] **Parallel scheduling algorithm for multiple tasks, considering urgency and dependencies**
-- [x] Dry-run mode: preview scheduling without modifying your Taskwarrior database
-- [x] Custom urgency weighting for scheduling (via CLI or config)
-- [x] **Auto-fix scheduling to match due dates**
-- [x] Force update of iCal calendars, bypassing cache
-- [x] Simple, customizable reports for planned and unplanned tasks
-- [x] Emoji and attribute customization in reports
-- [ ] Use Google API to access calendars
-
-## Install
-
-1. `pipx install taskcheck`
-2. `taskcheck --install`
-
-## How does it work
-
-This extension parses your pending and waiting tasks sorted decreasingly by urgency and tries to schedule them in the future.
-It considers their estimated time to schedule all tasks starting from the most urgent one.
-
-#### UDAs
-
-Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
-the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
-that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
-The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
-file of taskcheck. For instance:
-
-```toml
-[time_maps]
-# get an error)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-# ...
-```
-
-#### They say it's an "AI"
-
-Taskcheck will also parse online iCal calendars (Google, Apple, etc.) and will match them with your time maps.
-It will then modify the Taskwarrior tasks by adding the `completion_date` attribute with the expected
-date of completion and the `scheduled` attribute with the date in which the task is expected to
-start.
-
-It will also print a red line for every task whose `completion_date` is after its `due_date`.
-
-In general, it is recommended to run taskcheck rather frequently and at least once at the beginning
-of your working day.
-
-#### Reports
-
-You can also print simple reports that exploit the `scheduling` UDA filled by Taskcheck to grasp
-how much time you have to work on which task in which day. For
-instance:
-
-- `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week
-
-## Configuration
-
-`taskcheck --install` allows you to create required and recommended configurations for
-Taskwarrior. It will also generate a default configuration file for taskcheck.
-
-Below is an example of a taskcheck configuration file, with all relevant options:
-
-```toml
-[time_maps]
-# Define your working hours for each named time map (in 24h format, e.g. 9.5 = 9:30)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-wednesday = [[9, 12.30], [14, 17]]
-thursday = [[9, 12.30], [14, 17]]
-friday = [[9, 12.30], [14, 17]]
-
-[time_maps.weekend]
-saturday = [[9, 12.30]]
-sunday = [[9, 12.30]]
-
-[scheduler]
-days_ahead = 1000         # How far to go with the schedule (lower values = faster computation)
-weight_urgency = 1.0      # Default weight for urgency in scheduling (overridable via CLI)
-# if weight_urgency is set to 0, only due urgency is considered
-# by default, this factor is automatically reduced if some task cannot be scheduled in time,
-# leading to tasks with due dates being prioritized (see --no-auto-adjust-urgency)
-
-[calendars]
-# iCal calendars can be used to block your time and make the scheduling more precise
-[calendars.1]
-url = "https://your/url/to/calendar.ics"
-expiration = 0.08         # In hours (0.08 hours ≈ 5 minutes)
-timezone = "Europe/Rome"  # If set, force timezone for this calendar (see TZ database)
-
-[calendars.holidays]
-url = "https://www.officeholidays.com/ics-clean/italy/milan"
-event_all_day_is_blocking = true
-expiration = 720          # In hours (720 hours = 30 days)
-
-[report]
-include_unplanned = true
-additional_attributes = ["estimated", "due", "urgency"]           # Extra attributes to show in the report
-additional_attributes_unplanned = ["due", "urgency"]               # Extra attributes for unplanned tasks
-unplanned_max_due = "30d"       # Only show unplanned tasks due within this Taskwarrior-relative horizon; tasks without a due date are always shown
-emoji_keywords = {"meet"=":busts_in_silhouette:", "review"=":mag_right:"} # Map keywords to emoji
-```
-
-### Configuration Options
-
-- **[scheduler]**
-  - `days_ahead`: How many days ahead to schedule tasks.
-  - `weight_urgency`: Default weight for urgency in scheduling (0.0 to 1.0). Can be overridden with `--urgency-weight`.
-- **[calendars]**
-  - `url`: iCal URL to block time.
-  - `expiration`: Cache expiration in hours.
-  - `timezone`: (Optional) Force a timezone for this calendar.
-  - `event_all_day_is_blocking`: (Optional, bool) Treat all-day events as blocking.
-- **[report]**
-  - `include_unplanned`: Show unplanned tasks in a separate section.
-  - `additional_attributes`: Extra columns to show in the report.
-  - `additional_attributes_unplanned`: Extra columns for unplanned tasks.
-  - `unplanned_max_due`: Optional Taskwarrior-relative horizon (for example `30d`) for dated unplanned tasks. Tasks without a due date are always shown; omitting this setting applies no limit.
-  - `emoji_keywords`: Map keywords in task descriptions to emoji.
-
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency.
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
-skip all the available slots until 12 pm.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
-
-After the scheduling is done, if any task has a `completion_date` after its `due_date`, the
-`weight_urgency` factor is reduced by 0.1 and the scheduling is repeated, until all tasks
-are scheduled before their due dates or the `weight_urgency` factor reaches 0.
-
-## Tips and Tricks
-
-- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
-- You can see tasks that you can execute now with the `task ready` report.
-
-## CLI Options
-
-```
-usage: __main__.py [-h] [-v] [-i] [-r REPORT] [-s] [-f] [--taskrc TASKRC] [--urgency-weight URGENCY_WEIGHT] [--dry-run] [--no-auto-adjust-urgency]
-
-options:
-  -h, --help            show this help message and exit
-  -v, --verbose         Increase output verbosity.
-  -i, --install         Install the UDAs, required settings, and default config file.
-  -r REPORT, --report REPORT
-                        Generate a report of the tasks based on the scheduling; can be any Taskwarrior datetime specification (e.g. today, tomorrow, eom, som, 1st, 2nd, etc.). It is considered as `by`, meaning that the report will be
-                        generated for all the days until the specified date and including it.
-  -s, --schedule        Perform the scheduling algorithm, giving a schedule and a scheduling UDA and alerting for not completable tasks
-  -f, --force-update    Force update of all ical calendars by ignoring cache expiration
-  --taskrc TASKRC       Set custom TASKRC directory for debugging purposes
-  --urgency-weight URGENCY_WEIGHT
-                        Weight for urgency in scheduling (0.0 to 1.0), overrides config value. When 1.0, the whole Taskwarrior urgency is used for scheduling. When 0.0, the Taskwarrior urgency is reduced to only due urgency.
-  --dry-run             Perform scheduling without modifying the Taskwarrior database, useful for testing
-  --no-auto-adjust-urgency
-                        Disable automatic reduction of urgency weight … (default: enabled)
-```
-
-### Examples
-
-- `taskcheck --schedule`  
-  Run the scheduler and update your Taskwarrior tasks.
-- `taskcheck --schedule --dry-run`  
-  Preview the schedule without modifying your database.
-- `taskcheck --schedule --urgency-weight 0.5`  
-  Use a custom urgency weighting for this run.
-- `taskcheck --schedule --no-auto-adjust-urgency`  
-  Avoid the automatically reduction of urgency weight if tasks can't be scheduled before their due dates.
-- `taskcheck --report today`  
-  Show the schedule for today.
-- `taskcheck --report 1w`  
-  Show the schedule for the next week.
-- `taskcheck --force-update`  
-  Force refresh of all iCal calendars, ignoring cache.

taskcheck-1.2.0/taskcheck.egg-info/PKG-INFO

@@ -1,232 +0,0 @@
-Metadata-Version: 2.4
-Name: taskcheck
-Version: 1.2.0
-Summary: Automatic scheduler for taskwarrior
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-Requires-Dist: appdirs>=1.4.4
-Requires-Dist: google-api-python-client>=2.198.0
-Requires-Dist: google-auth>=2.56.2
-Requires-Dist: google-auth-oauthlib>=1.2.2
-Requires-Dist: icalendar>=6.0.1
-Requires-Dist: random-unicode-emoji>=2.8
-Requires-Dist: requests>=2.32.3
-Requires-Dist: rich>=13.9.4
-
-<div align="center">
-  
-```
-########    ###     ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-   ##      ## ##   ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##     ##   ##  ##       ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ##  ######  #####    ##       ######### ######   ##       #####    
-   ##    #########       ## ##  ##   ##       ##     ## ##       ##       ##  ##   
-   ##    ##     ## ##    ## ##   ##  ##    ## ##     ## ##       ##    ## ##   ##  
-   ##    ##     ##  ######  ##    ##  ######  ##     ## ########  ######  ##    ## 
-```
-
-> _A non-AI automatic scheduler for taskwarrior (i.e. alternative to skedpal / timehero / flowsavvy / reclaim / trevor / motion)_
-
-  ![immagine](https://github.com/user-attachments/assets/27b83bb1-7a50-4923-a453-0a958fbe11ed)
-
-</div>
-
-This is a taskwarrior extension that automatically schedules your tasks based on your working hours,
-estimated time, and calendar events, finding an optimal time to work on each task and match all your
-deadlines.
-
-> [!IMPORTANT]
-> This repo is actively maintained again
-
-## Features
-
-- [x] **Use arbitrarily complex time maps for working hours**
-- [x] Block scheduling time using iCal calendars (meetings, vacations, holidays, etc.)
-- [x] **Parallel scheduling algorithm for multiple tasks, considering urgency and dependencies**
-- [x] Dry-run mode: preview scheduling without modifying your Taskwarrior database
-- [x] Custom urgency weighting for scheduling (via CLI or config)
-- [x] **Auto-fix scheduling to match due dates**
-- [x] Force update of iCal calendars, bypassing cache
-- [x] Simple, customizable reports for planned and unplanned tasks
-- [x] Emoji and attribute customization in reports
-- [ ] Use Google API to access calendars
-
-## Install
-
-1. `pipx install taskcheck`
-2. `taskcheck --install`
-
-## How does it work
-
-This extension parses your pending and waiting tasks sorted decreasingly by urgency and tries to schedule them in the future.
-It considers their estimated time to schedule all tasks starting from the most urgent one.
-
-#### UDAs
-
-Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
-the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
-that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
-The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
-file of taskcheck. For instance:
-
-```toml
-[time_maps]
-# get an error)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-# ...
-```
-
-#### They say it's an "AI"
-
-Taskcheck will also parse online iCal calendars (Google, Apple, etc.) and will match them with your time maps.
-It will then modify the Taskwarrior tasks by adding the `completion_date` attribute with the expected
-date of completion and the `scheduled` attribute with the date in which the task is expected to
-start.
-
-It will also print a red line for every task whose `completion_date` is after its `due_date`.
-
-In general, it is recommended to run taskcheck rather frequently and at least once at the beginning
-of your working day.
-
-#### Reports
-
-You can also print simple reports that exploit the `scheduling` UDA filled by Taskcheck to grasp
-how much time you have to work on which task in which day. For
-instance:
-
-- `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week
-
-## Configuration
-
-`taskcheck --install` allows you to create required and recommended configurations for
-Taskwarrior. It will also generate a default configuration file for taskcheck.
-
-Below is an example of a taskcheck configuration file, with all relevant options:
-
-```toml
-[time_maps]
-# Define your working hours for each named time map (in 24h format, e.g. 9.5 = 9:30)
-[time_maps.work]
-monday = [[9, 12.30], [14, 17]]
-tuesday = [[9, 12.30], [14, 17]]
-wednesday = [[9, 12.30], [14, 17]]
-thursday = [[9, 12.30], [14, 17]]
-friday = [[9, 12.30], [14, 17]]
-
-[time_maps.weekend]
-saturday = [[9, 12.30]]
-sunday = [[9, 12.30]]
-
-[scheduler]
-days_ahead = 1000         # How far to go with the schedule (lower values = faster computation)
-weight_urgency = 1.0      # Default weight for urgency in scheduling (overridable via CLI)
-# if weight_urgency is set to 0, only due urgency is considered
-# by default, this factor is automatically reduced if some task cannot be scheduled in time,
-# leading to tasks with due dates being prioritized (see --no-auto-adjust-urgency)
-
-[calendars]
-# iCal calendars can be used to block your time and make the scheduling more precise
-[calendars.1]
-url = "https://your/url/to/calendar.ics"
-expiration = 0.08         # In hours (0.08 hours ≈ 5 minutes)
-timezone = "Europe/Rome"  # If set, force timezone for this calendar (see TZ database)
-
-[calendars.holidays]
-url = "https://www.officeholidays.com/ics-clean/italy/milan"
-event_all_day_is_blocking = true
-expiration = 720          # In hours (720 hours = 30 days)
-
-[report]
-include_unplanned = true
-additional_attributes = ["estimated", "due", "urgency"]           # Extra attributes to show in the report
-additional_attributes_unplanned = ["due", "urgency"]               # Extra attributes for unplanned tasks
-unplanned_max_due = "30d"       # Only show unplanned tasks due within this Taskwarrior-relative horizon; tasks without a due date are always shown
-emoji_keywords = {"meet"=":busts_in_silhouette:", "review"=":mag_right:"} # Map keywords to emoji
-```
-
-### Configuration Options
-
-- **[scheduler]**
-  - `days_ahead`: How many days ahead to schedule tasks.
-  - `weight_urgency`: Default weight for urgency in scheduling (0.0 to 1.0). Can be overridden with `--urgency-weight`.
-- **[calendars]**
-  - `url`: iCal URL to block time.
-  - `expiration`: Cache expiration in hours.
-  - `timezone`: (Optional) Force a timezone for this calendar.
-  - `event_all_day_is_blocking`: (Optional, bool) Treat all-day events as blocking.
-- **[report]**
-  - `include_unplanned`: Show unplanned tasks in a separate section.
-  - `additional_attributes`: Extra columns to show in the report.
-  - `additional_attributes_unplanned`: Extra columns for unplanned tasks.
-  - `unplanned_max_due`: Optional Taskwarrior-relative horizon (for example `30d`) for dated unplanned tasks. Tasks without a due date are always shown; omitting this setting applies no limit.
-  - `emoji_keywords`: Map keywords in task descriptions to emoji.
-
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency.
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
-skip all the available slots until 12 pm.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
-
-After the scheduling is done, if any task has a `completion_date` after its `due_date`, the
-`weight_urgency` factor is reduced by 0.1 and the scheduling is repeated, until all tasks
-are scheduled before their due dates or the `weight_urgency` factor reaches 0.
-
-## Tips and Tricks
-
-- You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.
-- You can see tasks that you can execute now with the `task ready` report.
-
-## CLI Options
-
-```
-usage: __main__.py [-h] [-v] [-i] [-r REPORT] [-s] [-f] [--taskrc TASKRC] [--urgency-weight URGENCY_WEIGHT] [--dry-run] [--no-auto-adjust-urgency]
-
-options:
-  -h, --help            show this help message and exit
-  -v, --verbose         Increase output verbosity.
-  -i, --install         Install the UDAs, required settings, and default config file.
-  -r REPORT, --report REPORT
-                        Generate a report of the tasks based on the scheduling; can be any Taskwarrior datetime specification (e.g. today, tomorrow, eom, som, 1st, 2nd, etc.). It is considered as `by`, meaning that the report will be
-                        generated for all the days until the specified date and including it.
-  -s, --schedule        Perform the scheduling algorithm, giving a schedule and a scheduling UDA and alerting for not completable tasks
-  -f, --force-update    Force update of all ical calendars by ignoring cache expiration
-  --taskrc TASKRC       Set custom TASKRC directory for debugging purposes
-  --urgency-weight URGENCY_WEIGHT
-                        Weight for urgency in scheduling (0.0 to 1.0), overrides config value. When 1.0, the whole Taskwarrior urgency is used for scheduling. When 0.0, the Taskwarrior urgency is reduced to only due urgency.
-  --dry-run             Perform scheduling without modifying the Taskwarrior database, useful for testing
-  --no-auto-adjust-urgency
-                        Disable automatic reduction of urgency weight … (default: enabled)
-```
-
-### Examples
-
-- `taskcheck --schedule`  
-  Run the scheduler and update your Taskwarrior tasks.
-- `taskcheck --schedule --dry-run`  
-  Preview the schedule without modifying your database.
-- `taskcheck --schedule --urgency-weight 0.5`  
-  Use a custom urgency weighting for this run.
-- `taskcheck --schedule --no-auto-adjust-urgency`  
-  Avoid the automatically reduction of urgency weight if tasks can't be scheduled before their due dates.
-- `taskcheck --report today`  
-  Show the schedule for today.
-- `taskcheck --report 1w`  
-  Show the schedule for the next week.
-- `taskcheck --force-update`  
-  Force refresh of all iCal calendars, ignoring cache.