scriptplan 0.10.2__tar.gz → 0.10.3__tar.gz

{scriptplan-0.10.2 → scriptplan-0.10.3}/CHANGELOG.md

@@ -1,5 +1,159 @@
 # Changelog
 
+## 0.10.3
+
+Fixes the defects Trace and Siambr reported against 0.10.2, and those found while fixing
+them. Two are regressions, one in 0.10.2 and one in 0.10.0. Three of the fixes can move
+the dates of a project that already scheduled, and they are listed first.
+
+### Fixes that can move an existing schedule
+
+- Tasks of equal priority were placed in declaration order. The README has always said
+  they are placed by criticalness, which no code computed until this release. A
+  resource's criticalness is the effort asked of it divided by the time it has. A task's
+  is its effort times the mean criticalness of the resources it may use, and its path
+  criticalness adds the heaviest chain of tasks that follow it. In practice the larger
+  effort is placed first. Tasks of 4 h, 1 h and 4 h on one desk used to run t0, t1, t2
+  and now run t0, t2, t1, which is the reference scheduler's order forwards, backwards
+  and under a daily cap. Give a task a `priority` to fix its place.
+- A task with a stated `start` and `end` and no effort booked none of the resources it
+  allocates. With `a` at priority 600 from 18:00 to 20:00 on a resource and `w` needing
+  an hour of the same resource from 18:00, 0.10.2 placed `w` at 18:00, inside `a`. `a`
+  now holds the resource and `w` runs 20:00-21:00. Where two such tasks overlap on one
+  resource, the one placed first holds the shared hours. The other keeps its dates and
+  books what is left, and neither is an error.
+- A project's `workinghours`, a global `leaves` and a shift's `leaves` now take effect
+  (next section). A project that sets any of them gets different dates, and they are
+  the dates it asked for.
+
+### Calendar
+
+Siambr reported the first three.
+
+- A project's `workinghours` was parsed and never applied. `length`, `gaplength` and a
+  resource with no hours of its own used Monday to Friday 09:00-17:00 whatever the
+  project said. With `workinghours mon - sat 09:00 - 17:00`, three days from Thursday
+  3 December ended on Monday the 7th. They now end on Saturday the 5th.
+- A global `leaves` did not close the calendar that `length` and `gaplength` count in,
+  although a global `vacation` did. `length 3d` from 24 December with
+  `leaves holiday "Christmas" 2026-12-25` ended on the 28th. It now ends on the 29th,
+  for any leave type and for a leave of part of a day.
+- A shift's `leaves` was dropped when the file was read, because the parser kept the
+  word `holiday` and lost the date. A resource on the shift now takes the shift's leave
+  with its hours.
+- A global `vacation` in the first week of a project in UTC was repeated every week for
+  a resource on the default hours. Ten days of effort from Monday 7 December with a
+  vacation on the 8th ended on the 23rd. They now end on the 21st.
+- Because each `leaves`, `vacation` or `booking` line on a resource stored the earlier
+  ones again, N lines kept 2^N - 1 entries and an availability check walked them all.
+  The dates were right, but the time doubled with each line, and Siambr measured 58
+  seconds for 20 leave days. Twenty lines now store twenty entries and schedule in
+  half a second.
+- A day that no `workinghours` line of a block names is not worked, for a project as
+  for a shift or a resource. This is unchanged and is now written down, because other
+  schedulers of this format keep the inherited hours on such a day.
+
+### Accepted and ignored
+
+`audit/evaluations/probe_directive_effect.py` now checks every directive the grammar
+accepts. It found these, beyond the calendar ones above.
+
+- Allocating a resource that has members failed with "could not be scheduled". It now
+  allocates every member, and 16 hours on a group of two takes one day.
+- `allocate r { limits { ... } }` was parsed and never applied. It is now refused, and
+  the error says to put the limits on the task.
+- `dailymin`, `weeklymin`, `monthlymin` and `minimum` were counted and never reported.
+  A period in which a resource or task was booked for less than its minimum now draws
+  a warning. The schedule and the exit code are unchanged.
+- `plan report` now prints warnings to stderr when the run succeeds. It used to discard
+  them, including the one that says a task asked to be scheduled as late as possible
+  and was scheduled as soon as possible because nothing fixed when it must end.
+- An attribute the reader could not turn into a name and a value was skipped. It is an
+  error now. The one case left on purpose is the value of a custom attribute declared
+  with `extend`, which ScriptPlan does not keep (README, known limits).
+
+### Regressions
+
+- A `!` reference whose scope is a task bound a task elsewhere in the project when that
+  scope had no such child. `g.b` with `depends !a` and no sibling `a` was scheduled after
+  `h.a`, an unrelated task in another branch. 0.10.1 refused the file, and 0.10.3
+  refuses it again. A reference with no `!`, or whose `!`s reach the top level of the
+  project, still binds the only task with that id, and one that could mean two tasks is
+  still refused. This was a regression in 0.10.2.
+- A task that depends on a container nested two or more levels deep never started. With
+  `p { m { w } }` and `s depends p`, 0.10.0 to 0.10.2 reported "Task 's' could not be
+  scheduled: no ready predecessor or successor". Containers were marked done in one
+  pass in declaration order, so p was checked before m and never marked. s now starts
+  09:30, when w ends, as 0.9.2 and the reference scheduler place it.
+
+### Fixed
+
+- A container that depends on another with a gap, `gaplength` or `onstart` never
+  scheduled its children. `q { depends p { gapduration 30min } }` reported "Task 'q.c'
+  could not be scheduled: no ready predecessor or successor" in 0.10.0 to 0.10.2, and
+  0.9.2 left q.c without dates and said nothing. Inheriting the dependency copied the
+  task `p` it names, and q.c waited for the copy, which is never scheduled. q.c now
+  runs 10:00-11:00, 30 minutes after p ends, which is the reference scheduler's answer.
+  An attribute that names a task, resource, account or shift keeps naming that same
+  one when a child inherits it.
+- A task scheduled as late as possible inside a container was not bounded by a
+  successor that depends on the container. With `q depends p` and q.c ending Monday
+  17:30, 0.9.2 to 0.10.1 placed p.p1 on Friday the 20th, after q.c, and said nothing.
+  0.10.2 refused the plan. p.p1 now ends when q.c starts, or 30 minutes earlier with
+  `gapduration 30min`. The same holds for a task nested deeper inside p.
+- `precedes` dropped its options. `a precedes b { gapduration 30min }` let b start the
+  moment a ended, and `gaplength` and `maxgapduration` were dropped the same way, with
+  nothing said. They now hold b back exactly as `b depends a` with the same option
+  does, in both directions; the backward cases match the reference scheduler.
+  `precedes b { onend }` is refused, because ScriptPlan cannot tie a task to another's
+  end, where 0.10.2 dropped it.
+- When a task broke a dependency on a container, the error was printed twice, and it
+  quoted the task's actual start as the start the file declares. It is printed once,
+  and names the declared start when that differs.
+- A milestone took a start inherited from its container as fixed. With the container
+  starting Monday 09:00 and the milestone depending on a task that ends at 17:00, 0.10.1
+  dated the milestone 09:00 and 0.10.2 refused the plan. The inherited start is now an
+  earliest start, as it already was for tasks with work, so the milestone sits at 17:00.
+  A start stated on the milestone itself is still fixed.
+- An unresolved `depends` or `precedes` was reported as "not a task in this project",
+  even when a task with that id existed elsewhere. The error now says the reference
+  names no task from where it is written.
+
+### Documentation
+
+- README now says that a task ranked higher takes a resource's daily or weekly
+  allowance first, so a lower-ranked task that started earlier can finish later. Trace
+  asked about a task that waited two days for 15 minutes on a capped resource. 0.10.2
+  and the hour-level reference scheduler give that schedule, and 0.10.1 gives it too at
+  15-minute slots. 0.10.1 differed only at 30-minute slots, because of the skipped-time
+  regression that 0.10.2 fixed.
+
+### Verification
+
+`tests/test_scope_and_inherited_start.py` runs six plans through the `plan` CLI. The
+three for the defects fail on 0.10.2, and the three that check what must not change pass
+on both versions. `tests/test_container_dependencies.py` runs 18 plans with container
+dependencies and `precedes`, checked against the reference scheduler where it accepts
+the plan and worked out by hand where it does not, and all 18 fail on 0.10.2.
+
+`tests/test_project_calendar.py` and `tests/test_contention_and_bookings.py` run 33
+plans for the calendar, booking and ordering fixes. Their expected dates are the
+reference scheduler's, apart from the one test of the unnamed-days rule. 28 of them
+fail on 0.10.2 and the 5 that check what must not change pass on both.
+`probe_directive_effect.py` holds a pair of projects for each of 52 directives and
+fails on 0.10.2 for nine of them. 150 random projects with contended resources give the
+reference scheduler's dates exactly. Before the ordering fix, 8 of 80 did not.
+
+No golden snapshot changes, but five example answers in `examples/edge_cases` do,
+because they assumed declaration order between tasks of equal priority:
+`shared_slot_forward_5min`, `shared_slot_forward_60min`, `shared_slot_backward`,
+`daily_cap_counts_worked_time` and `eight_efforts_fill_whole_days`. Four probes that
+assumed the same are updated. Trace's 16 project files give the same result as on
+0.10.2, apart from the two this release was meant to fix.
+
+Free-threaded Python builds were not exercised, nor Python 3.10 to 3.12 for the full
+suite.
+
 ## 0.10.2
 
 0.10.1 shipped two regressions. This release fixes them and the gaps 0.10.1 listed as

{scriptplan-0.10.2/scriptplan.egg-info → scriptplan-0.10.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: scriptplan
-Version: 0.10.2
+Version: 0.10.3
 Summary: A precise project scheduling engine with minute-level accuracy for resource allocation and dependency management.
 Author-email: Farshid Ashouri <farsheed.ashouri@gmail.com>
 Maintainer-email: Farshid Ashouri <farsheed.ashouri@gmail.com>
@@ -49,8 +49,8 @@ Dynamic: license-file
 
 # ScriptPlan
 
-![Tests](https://img.shields.io/badge/tests-496_passing-success?style=for-the-badge)
-![Probes](https://img.shields.io/badge/audit_probes-85_passing-success?style=for-the-badge)
+![Tests](https://img.shields.io/badge/tests-556_passing-success?style=for-the-badge)
+![Probes](https://img.shields.io/badge/audit_probes-139_passing-success?style=for-the-badge)
 ![Python](https://img.shields.io/badge/python-3.9%2B-blue?style=for-the-badge)
 ![Licence](https://img.shields.io/badge/licence-Apache--2.0-lightgrey?style=for-the-badge)
 
@@ -150,6 +150,12 @@ audit/evaluations/run_all.sh
 - Dates are read in the project's timezone and scheduled in UTC; reports convert back.
 - Resource shifts follow their own timezone across daylight-saving changes in both directions.
 - A working-hours interval that crosses midnight applies to the following day.
+- The project's `workinghours` is the calendar that `length`, `gaplength` and a
+  resource with no hours of its own use. Without one it is Monday to Friday,
+  09:00-17:00, in the project's timezone.
+- A global `leaves` or `vacation` closes that calendar for everyone, whatever the
+  leave is called, for whole days or part of one. A shift's `leaves` holds for
+  every resource on the shift.
 - Slot size is derived from the times a project uses, so `start 09:30` is honoured
   exactly and a shift of `08:13 - 11:59, 13:07 - 17:47` yields its true 8h26m a day.
   `timingresolution` overrides this.
@@ -165,9 +171,17 @@ audit/evaluations/run_all.sh
 - `effort` is person-time: two resources available in a slot contribute two
   slots of it. `mandatory` requires a resource for the task to progress at all;
   `persistent` keeps the one first chosen; `alternative` falls back.
-- `dailymax`, `weeklymax`, `monthlymax`, `maximum` and their `min` counterparts
-  block at the cap **and** release in the next period. Periods are counted in the
-  resource's own calendar, and a cap smaller than one slot is honoured exactly.
+- Allocating a resource that has members allocates every member.
+- A task with a `duration`, or with a stated `start` and `end`, books the
+  resources it allocates for the hours they are on shift and free. It keeps its
+  dates when they are not.
+- `dailymax`, `weeklymax`, `monthlymax` and `maximum` block at the cap **and**
+  release in the next period. Periods are counted in the resource's own calendar,
+  a week runs Monday to Sunday, and a cap smaller than one slot is honoured
+  exactly.
+- `dailymin`, `weeklymin`, `monthlymin` and `minimum` are targets, which placing
+  tasks cannot guarantee. A period in which the resource or task was booked for
+  less draws a warning once the schedule is complete.
 
 **Scheduling**
 
@@ -177,6 +191,12 @@ audit/evaluations/run_all.sh
   end. With none of these but a successor scheduled as soon as possible that
   states no start, it is scheduled as soon as possible instead, with a warning.
 - Contention is resolved by priority, then criticalness, then declaration order.
+  A task's criticalness is its effort times how much is asked of the resources it
+  may use, plus that of the heaviest chain of tasks that follow it, so at equal
+  priority the larger effort is placed first. Tasks are placed one at a time in
+  that order, so a task ranked higher takes a resource's daily or weekly allowance
+  first, and a lower-ranked task that started earlier can finish later. Raising
+  its priority keeps it going.
 - The declared project period is never rewritten. A task that does not fit is
   reported, with its name and the reason. A date stated outside the period is an
   error.
@@ -194,7 +214,10 @@ audit/evaluations/run_all.sh
 - A project that cannot be scheduled exits non-zero and says why. A dependency
   cycle is rejected before scheduling, naming the cycle.
 - An attribute or reference the parser cannot place is an error, never a silent
-  drop.
+  drop. Each directive the grammar accepts has a probe showing that it changes a
+  schedule, is refused or draws a warning, and the few that do none of these are
+  listed in `audit/evaluations/probe_directive_effect.py` with the reason.
+- Warnings are printed to stderr by `plan report` as well as by `scriptplan`.
 - `report_id` is a SHA-256 of the rendered result, so it differs when the
   schedule differs.
 
@@ -205,11 +228,27 @@ audit/evaluations/run_all.sh
   rejected at parse time rather than silently producing nothing.
 - Accounts are parsed but not yet modelled, so `chargeset` and `charge` record an
   amount without posting it anywhere.
-- A task reference is first looked up from the referring task's scope, one level
-  up for each `!`. When that finds nothing but exactly one task in the project has
-  that id, the reference binds to it, so `depends !!pack` inside `delivery` finds
-  `delivery.pack`. When two tasks could be meant, the file is refused and both are
-  named.
+- The value a task or resource gives to a custom attribute declared with `extend`
+  is read and not kept.
+- `limits` inside an `allocate` option block is refused. Put the limits on the
+  task, with `{ resources <id> }` to hold them to one resource.
+- The `workinghours` lines of one block (project, shift or resource) state its
+  whole week: a day no line names is not worked, and two lines naming the same
+  day add up. Other schedulers of this format keep the inherited hours on a day
+  a line does not name. Name every day you mean.
+- A `length` task with no start of its own is reported as starting at the first
+  working moment it can, where other schedulers report the moment it was
+  released, which may be midnight. The end is the same.
+- Each resource holds one entry per slot for the whole project, so memory grows
+  with resources times the project's length divided by the slot size. Times off
+  the hour make the slots smaller; `timingresolution` sets the size outright.
+- A task reference is looked up from the referring task's scope, one level up for
+  each `!`. When the `!`s stop at a task, the reference must name one of its
+  children: `!x` with no sibling `x` is refused. When there are no `!`s, or they
+  reach the top level of the project and no top-level task matches, the reference
+  binds to the only task in the project with that id, so `depends !!pack` inside
+  `delivery` finds `delivery.pack`. When two tasks could be meant, the file is
+  refused and both are named.
 - `onstart` on a dependency means start-to-start for a task scheduled as soon as
   possible: it may start once the predecessor starts. For a task scheduled as
   late as possible it means the task must finish before the predecessor starts,

{scriptplan-0.10.2 → scriptplan-0.10.3}/README.md

@@ -4,8 +4,8 @@
 
 # ScriptPlan
 
-![Tests](https://img.shields.io/badge/tests-496_passing-success?style=for-the-badge)
-![Probes](https://img.shields.io/badge/audit_probes-85_passing-success?style=for-the-badge)
+![Tests](https://img.shields.io/badge/tests-556_passing-success?style=for-the-badge)
+![Probes](https://img.shields.io/badge/audit_probes-139_passing-success?style=for-the-badge)
 ![Python](https://img.shields.io/badge/python-3.9%2B-blue?style=for-the-badge)
 ![Licence](https://img.shields.io/badge/licence-Apache--2.0-lightgrey?style=for-the-badge)
 
@@ -105,6 +105,12 @@ audit/evaluations/run_all.sh
 - Dates are read in the project's timezone and scheduled in UTC; reports convert back.
 - Resource shifts follow their own timezone across daylight-saving changes in both directions.
 - A working-hours interval that crosses midnight applies to the following day.
+- The project's `workinghours` is the calendar that `length`, `gaplength` and a
+  resource with no hours of its own use. Without one it is Monday to Friday,
+  09:00-17:00, in the project's timezone.
+- A global `leaves` or `vacation` closes that calendar for everyone, whatever the
+  leave is called, for whole days or part of one. A shift's `leaves` holds for
+  every resource on the shift.
 - Slot size is derived from the times a project uses, so `start 09:30` is honoured
   exactly and a shift of `08:13 - 11:59, 13:07 - 17:47` yields its true 8h26m a day.
   `timingresolution` overrides this.
@@ -120,9 +126,17 @@ audit/evaluations/run_all.sh
 - `effort` is person-time: two resources available in a slot contribute two
   slots of it. `mandatory` requires a resource for the task to progress at all;
   `persistent` keeps the one first chosen; `alternative` falls back.
-- `dailymax`, `weeklymax`, `monthlymax`, `maximum` and their `min` counterparts
-  block at the cap **and** release in the next period. Periods are counted in the
-  resource's own calendar, and a cap smaller than one slot is honoured exactly.
+- Allocating a resource that has members allocates every member.
+- A task with a `duration`, or with a stated `start` and `end`, books the
+  resources it allocates for the hours they are on shift and free. It keeps its
+  dates when they are not.
+- `dailymax`, `weeklymax`, `monthlymax` and `maximum` block at the cap **and**
+  release in the next period. Periods are counted in the resource's own calendar,
+  a week runs Monday to Sunday, and a cap smaller than one slot is honoured
+  exactly.
+- `dailymin`, `weeklymin`, `monthlymin` and `minimum` are targets, which placing
+  tasks cannot guarantee. A period in which the resource or task was booked for
+  less draws a warning once the schedule is complete.
 
 **Scheduling**
 
@@ -132,6 +146,12 @@ audit/evaluations/run_all.sh
   end. With none of these but a successor scheduled as soon as possible that
   states no start, it is scheduled as soon as possible instead, with a warning.
 - Contention is resolved by priority, then criticalness, then declaration order.
+  A task's criticalness is its effort times how much is asked of the resources it
+  may use, plus that of the heaviest chain of tasks that follow it, so at equal
+  priority the larger effort is placed first. Tasks are placed one at a time in
+  that order, so a task ranked higher takes a resource's daily or weekly allowance
+  first, and a lower-ranked task that started earlier can finish later. Raising
+  its priority keeps it going.
 - The declared project period is never rewritten. A task that does not fit is
   reported, with its name and the reason. A date stated outside the period is an
   error.
@@ -149,7 +169,10 @@ audit/evaluations/run_all.sh
 - A project that cannot be scheduled exits non-zero and says why. A dependency
   cycle is rejected before scheduling, naming the cycle.
 - An attribute or reference the parser cannot place is an error, never a silent
-  drop.
+  drop. Each directive the grammar accepts has a probe showing that it changes a
+  schedule, is refused or draws a warning, and the few that do none of these are
+  listed in `audit/evaluations/probe_directive_effect.py` with the reason.
+- Warnings are printed to stderr by `plan report` as well as by `scriptplan`.
 - `report_id` is a SHA-256 of the rendered result, so it differs when the
   schedule differs.
 
@@ -160,11 +183,27 @@ audit/evaluations/run_all.sh
   rejected at parse time rather than silently producing nothing.
 - Accounts are parsed but not yet modelled, so `chargeset` and `charge` record an
   amount without posting it anywhere.
-- A task reference is first looked up from the referring task's scope, one level
-  up for each `!`. When that finds nothing but exactly one task in the project has
-  that id, the reference binds to it, so `depends !!pack` inside `delivery` finds
-  `delivery.pack`. When two tasks could be meant, the file is refused and both are
-  named.
+- The value a task or resource gives to a custom attribute declared with `extend`
+  is read and not kept.
+- `limits` inside an `allocate` option block is refused. Put the limits on the
+  task, with `{ resources <id> }` to hold them to one resource.
+- The `workinghours` lines of one block (project, shift or resource) state its
+  whole week: a day no line names is not worked, and two lines naming the same
+  day add up. Other schedulers of this format keep the inherited hours on a day
+  a line does not name. Name every day you mean.
+- A `length` task with no start of its own is reported as starting at the first
+  working moment it can, where other schedulers report the moment it was
+  released, which may be midnight. The end is the same.
+- Each resource holds one entry per slot for the whole project, so memory grows
+  with resources times the project's length divided by the slot size. Times off
+  the hour make the slots smaller; `timingresolution` sets the size outright.
+- A task reference is looked up from the referring task's scope, one level up for
+  each `!`. When the `!`s stop at a task, the reference must name one of its
+  children: `!x` with no sibling `x` is refused. When there are no `!`s, or they
+  reach the top level of the project and no top-level task matches, the reference
+  binds to the only task in the project with that id, so `depends !!pack` inside
+  `delivery` finds `delivery.pack`. When two tasks could be meant, the file is
+  refused and both are named.
 - `onstart` on a dependency means start-to-start for a task scheduled as soon as
   possible: it may start once the predecessor starts. For a task scheduled as
   late as possible it means the task must finish before the predecessor starts,

scriptplan-0.10.3/examples/edge_cases/daily_cap_counts_worked_time.expected.csv

@@ -0,0 +1,4 @@
+id;start;end
+t0;2026-10-19-09:00:00;2026-10-19-09:40:00
+t1;2026-10-20-09:20:00;2026-10-20-09:33:00
+t2;2026-10-19-09:40:00;2026-10-20-09:20:00

scriptplan-0.10.3/examples/edge_cases/daily_cap_counts_worked_time.expected.md

@@ -0,0 +1,8 @@
+# daily_cap_counts_worked_time
+
+dailymax 60min on the desk, and three tasks of 40, 13 and 40 minutes at the same priority.
+Tasks of equal priority are placed larger effort first (path criticalness), and equal efforts in
+declaration order, so the order is t0, t2, t1. Monday: t0 works 09:00-09:40, leaving 20 minutes under the
+cap, so t2 works 09:40-10:00 on Monday and its other 20 minutes on Tuesday, 09:00-09:20. t1 follows on
+Tuesday, 09:20-09:33. The cap blocks at exactly 60 minutes and releases on the next day. 0.10.0 counted
+whole booked hours against the cap and spread the tasks over Monday, Tuesday and Wednesday.

scriptplan-0.10.3/examples/edge_cases/eight_efforts_fill_whole_days.expected.csv

@@ -0,0 +1,9 @@
+id;start;end
+t0;2026-10-21-16:16:00;2026-10-22-09:17:00
+t1;2026-10-21-12:54:00;2026-10-21-15:03:00
+t2;2026-10-22-09:17:00;2026-10-22-10:06:00
+t3;2026-10-21-15:03:00;2026-10-21-16:16:00
+t4;2026-10-20-10:39:00;2026-10-20-15:57:00
+t5;2026-10-20-15:57:00;2026-10-21-10:40:00
+t6;2026-10-19-09:00:00;2026-10-20-10:39:00
+t7;2026-10-21-10:40:00;2026-10-21-12:54:00

scriptplan-0.10.3/examples/edge_cases/eight_efforts_fill_whole_days.expected.md

@@ -0,0 +1,6 @@
+# eight_efforts_fill_whole_days
+
+Eight tasks of 61, 129, 49, 73, 318, 163, 579 and 134 minutes on one desk with 09:00-17:00 days, all at
+the same priority. They are placed larger effort first (path criticalness): t6, t4, t5, t7, t1, t3, t0,
+t2. Packed back to back they fill Monday, Tuesday and Wednesday with exactly 480 minutes each and end on
+Thursday after 66 more (1506 in all). 0.10.0 booked 490 minutes into the Monday.

scriptplan-0.10.3/examples/edge_cases/shared_slot_backward.expected.csv

@@ -0,0 +1,4 @@
+id;start;end
+t0;2026-10-19-16:20:00;2026-10-19-17:00:00
+t1;2026-10-19-15:27:00;2026-10-19-15:40:00
+t2;2026-10-19-15:40:00;2026-10-19-16:20:00

scriptplan-0.10.3/examples/edge_cases/shared_slot_backward.expected.md

@@ -0,0 +1,6 @@
+# shared_slot_backward
+
+The same three tasks, each alap with end 17:00. Tasks of equal priority are placed larger effort first (path criticalness), and equal efforts in
+declaration order, so the order is t0, t2, t1.
+Each is placed as late as the desk allows: t0 17:00 - 40 = 16:20; t2 ends where t0 begins,
+16:20 - 40 = 15:40; t1 15:40 - 13 = 15:27.

scriptplan-0.10.3/examples/edge_cases/shared_slot_forward_5min.expected.csv

@@ -0,0 +1,4 @@
+id;start;end
+t0;2026-10-19-09:00:00;2026-10-19-09:40:00
+t1;2026-10-19-10:20:00;2026-10-19-10:33:00
+t2;2026-10-19-09:40:00;2026-10-19-10:20:00

scriptplan-0.10.3/examples/edge_cases/shared_slot_forward_5min.expected.md

@@ -0,0 +1,8 @@
+# shared_slot_forward_5min
+
+Three tasks of 40, 13 and 40 minutes on one desk, same priority, 5-minute slots.
+Tasks of equal priority are placed larger effort first (path criticalness), and equal efforts in
+declaration order, so the order is t0, t2, t1. One person works one task at a time, so they run back to back
+from 09:00: t0 09:00 + 40 = 09:40; t2 09:40 + 40 = 10:20; t1 10:20 + 13 = 10:33. Total 93 minutes.
+0.10.0 started all three at 09:00 at 60-minute resolution (issuedb #11). Until 0.10.3 equal priorities
+were placed in declaration order (issuedb #37).

scriptplan-0.10.3/examples/edge_cases/shared_slot_forward_60min.expected.csv

@@ -0,0 +1,4 @@
+id;start;end
+t0;2026-10-19-09:00:00;2026-10-19-09:40:00
+t1;2026-10-19-10:20:00;2026-10-19-10:33:00
+t2;2026-10-19-09:40:00;2026-10-19-10:20:00

scriptplan-0.10.3/examples/edge_cases/shared_slot_forward_60min.expected.md

@@ -0,0 +1,8 @@
+# shared_slot_forward_60min
+
+Three tasks of 40, 13 and 40 minutes on one desk, same priority, 60-minute slots.
+Tasks of equal priority are placed larger effort first (path criticalness), and equal efforts in
+declaration order, so the order is t0, t2, t1. One person works one task at a time, so they run back to back
+from 09:00: t0 09:00 + 40 = 09:40; t2 09:40 + 40 = 10:20; t1 10:20 + 13 = 10:33. Total 93 minutes.
+0.10.0 started all three at 09:00 at 60-minute resolution (issuedb #11). Until 0.10.3 equal priorities
+were placed in declaration order (issuedb #37).

{scriptplan-0.10.2 → scriptplan-0.10.3}/scriptplan/__init__.py

@@ -7,7 +7,7 @@ for project files written in the .tjp project definition language.
 
 # The single source of truth for the version; pyproject reads it from here.
 # 0.10.2: every stated date and dependency is kept or refused, never overridden.
-__version__ = "0.10.2"
+__version__ = "0.10.3"
 __author__ = "ScriptPlan Team"
 
 from scriptplan.core.project import Project

{scriptplan-0.10.2 → scriptplan-0.10.3}/scriptplan/cli/main.py

@@ -25,6 +25,7 @@ from pathlib import Path
 from typing import Optional
 
 from scriptplan import __version__
+from scriptplan.cli.programmatic import run_scriptplan  # noqa: F401  (moved; still importable from here)
 
 
 def setup_logging(debug_level: int = 0, debug_modules: Optional[list[str]] = None) -> None:
@@ -472,52 +473,6 @@ class ScriptPlan:
             return False
 
 
-def run_scriptplan(tjp_file: str, output_dir: Optional[str] = None) -> tuple[bool, Optional[str]]:
-    """
-    Run ScriptPlan report generation on a .tjp file.
-
-    This is a simplified interface for programmatic use.
-
-    Args:
-        tjp_file: Path to the .tjp file
-        output_dir: Optional output directory for reports (default: current directory)
-
-    Returns:
-        Tuple of (success, error_message)
-    """
-    import contextlib
-    import io
-
-    # Capture stderr to get error messages
-    stderr_capture = io.StringIO()
-
-    try:
-        with contextlib.redirect_stderr(stderr_capture):
-            # Create minimal args
-            parser = create_parser()
-            args_list = [tjp_file]
-            if output_dir:
-                args_list.extend(["--output-dir", output_dir])
-            args = parser.parse_args(args_list)
-
-            # Suppress logging for programmatic use
-            logging.getLogger().setLevel(logging.ERROR)
-
-            # Run the application
-            app = ScriptPlan(args)
-            exit_code = app.run()
-
-            if exit_code == 0:
-                return (True, None)
-            else:
-                error_output = stderr_capture.getvalue()
-                return (False, error_output or "Report generation failed")
-
-    except Exception as e:
-        error_output = stderr_capture.getvalue()
-        return (False, error_output or str(e))
-
-
 def main(argv: Optional[list[str]] = None) -> int:
     """
     Main entry point for the CLI.

{scriptplan-0.10.2 → scriptplan-0.10.3}/scriptplan/cli/plan.py

@@ -19,7 +19,6 @@ from typing import Optional
 import click
 
 from scriptplan import __version__
-from scriptplan.cli.main import run_scriptplan
 from scriptplan.cli.plan_files import (
     InputFileError,
     create_auto_report_file,
@@ -28,6 +27,7 @@ from scriptplan.cli.plan_files import (
     validate_tjp_file,
 )
 from scriptplan.cli.plan_help import register as register_help_commands
+from scriptplan.cli.programmatic import run_scriptplan
 
 # Configure logging
 logger = logging.getLogger(__name__)

scriptplan-0.10.3/scriptplan/cli/programmatic.py

@@ -0,0 +1,61 @@
+"""Running the report generator from Python, as `plan report` does."""
+
+from __future__ import annotations
+
+import logging
+import sys
+
+__all__ = ["run_scriptplan"]
+
+
+def run_scriptplan(tjp_file: str, output_dir: str | None = None) -> tuple[bool, str | None]:
+    """
+    Run ScriptPlan report generation on a .tjp file.
+
+    This is a simplified interface for programmatic use.
+
+    Args:
+        tjp_file: Path to the .tjp file
+        output_dir: Optional output directory for reports (default: current directory)
+
+    Returns:
+        Tuple of (success, error_message)
+    """
+    import contextlib
+    import io
+
+    # Capture stderr to get error messages
+    stderr_capture = io.StringIO()
+
+    try:
+        with contextlib.redirect_stderr(stderr_capture):
+            from scriptplan.cli.main import ScriptPlan, create_parser
+
+            # Create minimal args
+            parser = create_parser()
+            args_list = [tjp_file]
+            if output_dir:
+                args_list.extend(["--output-dir", output_dir])
+            args = parser.parse_args(args_list)
+
+            # Suppress logging for programmatic use
+            logging.getLogger().setLevel(logging.ERROR)
+
+            # Run the application
+            app = ScriptPlan(args)
+            exit_code = app.run()
+
+            if exit_code != 0:
+                error_output = stderr_capture.getvalue()
+                return (False, error_output or "Report generation failed")
+
+    except Exception as e:
+        error_output = stderr_capture.getvalue()
+        return (False, error_output or str(e))
+
+    # A schedule that succeeded with warnings still has to show them: a
+    # warning nobody sees is a silent change to what the file asked for.
+    said = stderr_capture.getvalue()
+    if said:
+        sys.stderr.write(said if said.endswith("\n") else said + "\n")
+    return (True, None)