@critical-path/svelte 0.19.3 → 0.19.4

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @critical-path/svelte
 
+## 0.19.4
+
+### Patch Changes
+
+- Updated dependencies [5dbf25b]
+  - @critical-path/core@0.55.0
+  - @critical-path/client@0.26.0
+  - @critical-path/mcp@0.22.0
+
 ## 0.19.3
 
 ### Patch Changes

package/dist/index.js

@@ -4590,6 +4590,7 @@ var xn = (e, t) => {
 	levelingDelayHours: X(I()).describe("With levelling: hours spent waiting for the assignee"),
 	waitingOn: X(F()).describe("With levelling: the task this one waited for"),
 	isMilestone: X(L()).describe("True for a milestone"),
+	isSummary: X(L()).describe("True for a task with subtasks: its dates and slack are roll-ups of them"),
 	deadlineDate: X(F()).describe("The task's deadline as an instant"),
 	deadlineVarianceHours: X(I()).describe("Working hours from forecast finish to deadline; negative means it will be missed")
 }), Pn = Y({
@@ -4599,6 +4600,8 @@ var xn = (e, t) => {
 	totalDurationHours: I(),
 	criticalTaskIds: z(F()).describe("Tasks with zero or negative slack, in schedule order"),
 	missedDeadlineTaskIds: X(z(F())).describe("Tasks forecast to finish after their deadline"),
+	unestimatedTaskIds: X(z(F())).describe("Unfinished tasks with no estimate, scheduled for defaultEstimateHours"),
+	cyclicTaskIds: X(z(F())).describe("Tasks on a dependency cycle; their dates are not reliable"),
 	tasks: z(Nn),
 	leveled: X(L()),
 	unleveledProjectEndDate: X(F()).describe("With levelling: the end date before levelling"),
@@ -4698,7 +4701,7 @@ var xn = (e, t) => {
 	{
 		name: "analyze-schedule",
 		description: "Find what drives a project's end date, how much each task can slip and where people are double-booked, then recommend fixes. Use for \"when will we finish?\", \"what is critical?\" or deadline-risk questions.",
-		content: "---\nname: analyze-schedule\ndescription: Find what drives a project's end date, how much each task can slip and where people are double-booked, then recommend fixes. Use for \"when will we finish?\", \"what is critical?\" or deadline-risk questions.\n---\n\n# Analyze the schedule\n\n## 1. Run the schedule\n\n1. Get the `projectId` (`list_projects`).\n2. Call `calculate_critical_path` with `calendars: \"assignee\"` and `levelResources: true`, so each person works on one task at a time on their own calendar. If the user wants the ideal schedule with unlimited people, call it with no options instead.\n3. If the question spans projects that share people, call `calculate_portfolio_critical_path` with their `projectIds` (and `projectOrder` if the user ranked them) instead.\n4. For in-flight projects, pass `effort: \"remaining\"` so finished hours are not scheduled again.\n\n## 2. Read the result\n\n- `projectEndDate` is the forecast finish. With levelling, compare it with `unleveledProjectEndDate`: the gap is time lost waiting for busy people.\n- `criticalTaskIds` are the tasks with zero or negative slack. Any delay to one of them moves the end date or misses a deadline.\n- `missedDeadlineTaskIds` lists tasks forecast to finish after their `deadline`. Their `deadlineVarianceHours` says by how much (negative working hours), and the negative `totalSlack` on the tasks before them shows which work drives the miss. Entries with `isMilestone: true` are checkpoints such as releases or sign-offs.\n- Each entry in `tasks` has `slackWorkingHours`: how many working hours the task can slip without moving the end. Under about 8 hours is near-critical.\n- `levelingDelayHours` and `waitingOn` show a task that waited for its assignee to finish another task.\n- `overallocations` lists periods where a person (`assigneeId`) or team (`teamId`) is booked above `capacity`; `allocation` 1.5 means 150%.\n\nLook up titles for the task ids you mention with `get_task` or `list_tasks`; report titles, not ids. To see why a critical task cannot start earlier, call `get_task` with `includeDependencies: true`: `dependencies.dependsOn` lists what it waits for and `dependencies.dependents` what waits for it.\n\n## 3. Recommend\n\nRank fixes by how much they pull the end date in:\n\n1. **Unblock critical tasks.** A critical task with `isBlocked: true` delays everything; say what it waits for.\n2. **Move work off the bottleneck person.** If critical tasks wait on one assignee (`waitingOn`), suggest reassigning a non-critical task of theirs.\n3. **Remove false dependencies.** A critical task waiting on work it does not really need (`dependencies.dependsOn`) can start earlier once the link is removed.\n4. **Split long critical tasks** so parts can run in parallel.\n5. **Cut or defer** tasks feeding late deliverables, if dates are fixed.\n\nShow the recommendation to the user. Change tasks (`update_task`) or dependencies (`add_dependency`, `remove_dependency`) only when they ask, then run the schedule again to show the effect.\n\n## Report format\n\n- Forecast finish date, and against any deadline the user gave. If the user gives a date that is not yet on a task, offer to record it as a `deadline` (on a milestone task with `isMilestone: true` if it is a checkpoint) so later runs track it.\n- Each milestone: forecast date against its deadline.\n- Critical path: task titles in order, with assignee.\n- Top risks: near-critical tasks, blocked critical tasks, over-allocations.\n- Recommended actions, each with its expected effect.\n"
+		content: "---\nname: analyze-schedule\ndescription: Find what drives a project's end date, how much each task can slip and where people are double-booked, then recommend fixes. Use for \"when will we finish?\", \"what is critical?\" or deadline-risk questions.\n---\n\n# Analyze the schedule\n\n## 1. Run the schedule\n\n1. Get the `projectId` (`list_projects`).\n2. Call `calculate_critical_path` with `calendars: \"assignee\"` and `levelResources: true`, so each person works on one task at a time on their own calendar. If the user wants the ideal schedule with unlimited people, call it with no options instead.\n3. If the question spans projects that share people, call `calculate_portfolio_critical_path` with their `projectIds` (and `projectOrder` if the user ranked them) instead.\n4. For in-flight projects, pass `effort: \"remaining\"` so finished hours are not scheduled again.\n\n## 2. Read the result\n\n- `projectEndDate` is the forecast finish. With levelling, compare it with `unleveledProjectEndDate`: the gap is time lost waiting for busy people.\n- `criticalTaskIds` are the tasks with zero or negative slack. Any delay to one of them moves the end date or misses a deadline.\n- `unestimatedTaskIds` lists unfinished tasks with no estimate; each was assumed to take `defaultEstimateHours` (1 by default), so say the forecast is uncertain and suggest estimating them. Entries with `isSummary: true` are parent tasks shown as the span of their subtasks.\n- `missedDeadlineTaskIds` lists tasks forecast to finish after their `deadline`. Their `deadlineVarianceHours` says by how much (negative working hours), and the negative `totalSlack` on the tasks before them shows which work drives the miss. Entries with `isMilestone: true` are checkpoints such as releases or sign-offs.\n- Each entry in `tasks` has `slackWorkingHours`: how many working hours the task can slip without moving the end. Under about 8 hours is near-critical.\n- `levelingDelayHours` and `waitingOn` show a task that waited for its assignee to finish another task.\n- `overallocations` lists periods where a person (`assigneeId`) or team (`teamId`) is booked above `capacity`; `allocation` 1.5 means 150%.\n\nLook up titles for the task ids you mention with `get_task` or `list_tasks`; report titles, not ids. To see why a critical task cannot start earlier, call `get_task` with `includeDependencies: true`: `dependencies.dependsOn` lists what it waits for and `dependencies.dependents` what waits for it.\n\n## 3. Recommend\n\nRank fixes by how much they pull the end date in:\n\n1. **Unblock critical tasks.** A critical task with `isBlocked: true` delays everything; say what it waits for.\n2. **Move work off the bottleneck person.** If critical tasks wait on one assignee (`waitingOn`), suggest reassigning a non-critical task of theirs.\n3. **Remove false dependencies.** A critical task waiting on work it does not really need (`dependencies.dependsOn`) can start earlier once the link is removed.\n4. **Split long critical tasks** so parts can run in parallel.\n5. **Cut or defer** tasks feeding late deliverables, if dates are fixed.\n\nShow the recommendation to the user. Change tasks (`update_task`) or dependencies (`add_dependency`, `remove_dependency`) only when they ask, then run the schedule again to show the effect.\n\n## Report format\n\n- Forecast finish date, and against any deadline the user gave. If the user gives a date that is not yet on a task, offer to record it as a `deadline` (on a milestone task with `isMilestone: true` if it is a checkpoint) so later runs track it.\n- Each milestone: forecast date against its deadline.\n- Critical path: task titles in order, with assignee.\n- Top risks: near-critical tasks, blocked critical tasks, over-allocations.\n- Recommended actions, each with its expected effect.\n"
 	},
 	{
 		name: "investigate-task",
@@ -5146,7 +5149,8 @@ var rr = $({
 			"dueDate",
 			"order"
 		]).optional().describe("Which ready task gets an assignee first when levelling (default: least slack, then task priority)"),
-		effort: H(["estimate", "remaining"]).optional().describe("'remaining' schedules only estimate minus logged hours for in-progress tasks (default: full estimates)")
+		effort: H(["estimate", "remaining"]).optional().describe("'remaining' schedules only estimate minus logged hours for in-progress tasks (default: full estimates)"),
+		defaultEstimateHours: I().nonnegative().optional().describe("Hours to assume for tasks with no estimate (default 1). They are listed in unestimatedTaskIds")
 	}),
 	annotations: { readOnlyHint: !0 },
 	execute: async (e, t) => t.calculatePortfolioCriticalPath(e)
@@ -5182,18 +5186,20 @@ var rr = $({
 				"dueDate",
 				"order"
 			]).optional().describe("Which ready task gets an assignee first when levelling (default: least slack, then task priority)"),
-			effort: H(["estimate", "remaining"]).optional().describe("'remaining' schedules only estimate minus logged hours for in-progress tasks (default: full estimates)")
+			effort: H(["estimate", "remaining"]).optional().describe("'remaining' schedules only estimate minus logged hours for in-progress tasks (default: full estimates)"),
+			defaultEstimateHours: I().nonnegative().optional().describe("Hours to assume for tasks with no estimate (default 1). They are listed in unestimatedTaskIds")
 		}),
 		annotations: { readOnlyHint: !0 },
 		execute: async (e, t, n) => {
 			let r = e.projectId || n?.projectId;
 			if (!r) throw Error("projectId is required to calculate the critical path. Find one with `list_projects`.");
-			let { calendars: i, levelResources: a, levelingPriority: o, effort: s } = e;
+			let { calendars: i, levelResources: a, levelingPriority: o, effort: s, defaultEstimateHours: c } = e;
 			return t.calculateCriticalPath(r, {
 				calendars: i,
 				levelResources: a,
 				levelingPriority: o,
-				effort: s
+				effort: s,
+				defaultEstimateHours: c
 			});
 		}
 	}),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@critical-path/svelte",
-  "version": "0.19.3",
+  "version": "0.19.4",
   "description": "Svelte 5 Runes state and reactive integrations for Critical Path headless project management framework",
   "author": "Jack James",
   "license": "MIT",
@@ -18,9 +18,9 @@
     }
   },
   "dependencies": {
-    "@critical-path/client": "0.25.4",
-    "@critical-path/core": "0.54.0",
-    "@critical-path/mcp": "0.21.0"
+    "@critical-path/client": "0.26.0",
+    "@critical-path/core": "0.55.0",
+    "@critical-path/mcp": "0.22.0"
   },
   "peerDependencies": {
     "svelte": "^5.57.2"