@critical-path/svelte 0.19.5 → 0.19.6

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @critical-path/svelte
 
+## 0.19.6
+
+### Patch Changes
+
+- Updated dependencies [224ad51]
+  - @critical-path/core@0.57.0
+  - @critical-path/mcp@0.24.0
+  - @critical-path/client@0.27.1
+
 ## 0.19.5
 
 ### Patch Changes

package/dist/index.js

@@ -4532,6 +4532,7 @@ var Sn = (e, t) => {
 	assigneeId: X(I()),
 	dueDate: X(I()),
 	deadline: X(I()).describe("Latest acceptable finish, enforced by critical path analysis"),
+	earliestStart: X(I()).describe("Earliest the task may start, enforced by critical path analysis"),
 	isMilestone: X(R()).describe("A zero-duration checkpoint"),
 	estimatedHours: X(L()),
 	loggedHours: X(L()),
@@ -4549,7 +4550,8 @@ var Sn = (e, t) => {
 	id: I(),
 	taskId: I().describe("The task that waits"),
 	dependsOnTaskId: I().describe("The task it waits for"),
-	type: I().describe("blocking or relates_to")
+	type: I().describe("blocking or relates_to"),
+	lagHours: X(L()).describe("Working hours the waiting task waits after the other finishes")
 }).describe("A dependency between two tasks"), An = Y({
 	id: I(),
 	projectId: I(),
@@ -4712,7 +4714,7 @@ var Sn = (e, t) => {
 	{
 		name: "plan-project",
 		description: "Turn a goal, brief or feature list into a Critical Path project with deliverables, estimated and prioritized tasks, and the dependencies between them. Use when the user asks to plan, scope or break down work.",
-		content: "---\nname: plan-project\ndescription: Turn a goal, brief or feature list into a Critical Path project with deliverables, estimated and prioritized tasks, and the dependencies between them. Use when the user asks to plan, scope or break down work.\n---\n\n# Plan a project\n\nTurn a goal into deliverables (dated outcomes), tasks (estimated units of work) and dependencies (which task waits for which) the scheduler can use.\n\n## 1. Find or create the project\n\n1. Call `list_projects`. If a project already matches the goal, use it and read it with `get_project` to learn its workflow status keys and custom fields.\n2. Only if none fits, and the user wants a new one, call `create_project` with a `name` and a short `key`.\n3. Call `list_tasks` with the `projectId` and `list_deliverables` to see what already exists. Do not recreate it.\n\n## 2. Draft the plan before writing anything\n\nBreak the goal down in your reply first and show it to the user:\n\n- **Deliverables**: 2-6 outcomes someone could accept or reject, each with a due date if the user gave one.\n- **Milestones** for dated checkpoints (a release, a sign-off, a review): a task with `isMilestone: true`, a `deadline` if the date is fixed, and dependencies on the tasks that must finish first. The schedule then reports whether each date will be met.\n- **Tasks** under each deliverable. Each task:\n  - starts with a verb and is small enough for one person (about 2-24 hours);\n  - has `estimatedHours` (effort, not elapsed time);\n  - has a `priority`: `urgent` only for work that blocks others now, `high` for the critical outcome, `medium` by default, `low` for nice-to-haves;\n  - lists the tasks it must wait for (its dependencies). Only add a dependency when the work truly cannot start earlier; every extra one lengthens the schedule.\n- Note anything you assumed (team size, dates, scope) as a question.\n\nAsk the user to confirm or adjust before creating anything. A plan is cheap to change in chat and tedious to change once created.\n\n## 3. Create it\n\n1. Create tasks with `create_task` (`projectId`, `title`, `description` with acceptance criteria, `estimatedHours`, `priority`, `assigneeId` if known). Leave `status` out so tasks start in the workflow's default status.\n2. Create each deliverable with `create_deliverable`, passing the ids of its tasks in `taskIds`.\n3. Add each dependency from your plan with `add_dependency`: `taskId` is the task that waits, `dependsOnTaskId` the task that must finish first. Use the ids `create_task` returned. If one is refused as circular, your plan has a loop: fix the order with the user instead of retrying.\n4. If the project already had tasks, check what they wait for with `get_task` and `includeDependencies: true` before linking new work to them.\n\n## 4. Check the result\n\n1. Call `calculate_critical_path` for the project and report the forecast `projectEndDate` and the `criticalTaskIds` (by title). If every task is critical or the end date looks too early, a dependency is probably missing or reversed.\n2. If the end date misses a deliverable's due date, or `missedDeadlineTaskIds` is not empty, say so and suggest what to cut, split or reassign. The `analyze-schedule` skill covers this in depth.\n\n## Guardrails\n\n- Never invent user ids for `assigneeId`. Leave tasks unassigned unless the user named the person and you have their id.\n- Keep the plan to what the user asked for; propose extra work as suggestions, not tasks.\n"
+		content: "---\nname: plan-project\ndescription: Turn a goal, brief or feature list into a Critical Path project with deliverables, estimated and prioritized tasks, and the dependencies between them. Use when the user asks to plan, scope or break down work.\n---\n\n# Plan a project\n\nTurn a goal into deliverables (dated outcomes), tasks (estimated units of work) and dependencies (which task waits for which) the scheduler can use.\n\n## 1. Find or create the project\n\n1. Call `list_projects`. If a project already matches the goal, use it and read it with `get_project` to learn its workflow status keys and custom fields.\n2. Only if none fits, and the user wants a new one, call `create_project` with a `name` and a short `key`.\n3. Call `list_tasks` with the `projectId` and `list_deliverables` to see what already exists. Do not recreate it.\n\n## 2. Draft the plan before writing anything\n\nBreak the goal down in your reply first and show it to the user:\n\n- **Deliverables**: 2-6 outcomes someone could accept or reject, each with a due date if the user gave one.\n- **Waits and fixed start dates**: a dependency's `lagHours` for a wait between tasks (curing, review turnaround), and a task's `earliestStart` when it cannot begin before a date. Do not invent placeholder tasks for these.\n- **Milestones** for dated checkpoints (a release, a sign-off, a review): a task with `isMilestone: true`, a `deadline` if the date is fixed, and dependencies on the tasks that must finish first. The schedule then reports whether each date will be met.\n- **Tasks** under each deliverable. Each task:\n  - starts with a verb and is small enough for one person (about 2-24 hours);\n  - has `estimatedHours` (effort, not elapsed time);\n  - has a `priority`: `urgent` only for work that blocks others now, `high` for the critical outcome, `medium` by default, `low` for nice-to-haves;\n  - lists the tasks it must wait for (its dependencies). Only add a dependency when the work truly cannot start earlier; every extra one lengthens the schedule.\n- Note anything you assumed (team size, dates, scope) as a question.\n\nAsk the user to confirm or adjust before creating anything. A plan is cheap to change in chat and tedious to change once created.\n\n## 3. Create it\n\n1. Create tasks with `create_task` (`projectId`, `title`, `description` with acceptance criteria, `estimatedHours`, `priority`, `assigneeId` if known). Leave `status` out so tasks start in the workflow's default status.\n2. Create each deliverable with `create_deliverable`, passing the ids of its tasks in `taskIds`.\n3. Add each dependency from your plan with `add_dependency`: `taskId` is the task that waits, `dependsOnTaskId` the task that must finish first. Use the ids `create_task` returned. If one is refused as circular, your plan has a loop: fix the order with the user instead of retrying.\n4. If the project already had tasks, check what they wait for with `get_task` and `includeDependencies: true` before linking new work to them.\n\n## 4. Check the result\n\n1. Call `calculate_critical_path` for the project and report the forecast `projectEndDate` and the `criticalTaskIds` (by title). If every task is critical or the end date looks too early, a dependency is probably missing or reversed.\n2. If the end date misses a deliverable's due date, or `missedDeadlineTaskIds` is not empty, say so and suggest what to cut, split or reassign. The `analyze-schedule` skill covers this in depth.\n\n## Guardrails\n\n- Never invent user ids for `assigneeId`. Leave tasks unassigned unless the user named the person and you have their id.\n- Keep the plan to what the user asked for; propose extra work as suggestions, not tasks.\n"
 	},
 	{
 		name: "report-status",
@@ -4927,6 +4929,7 @@ var ir = $({
 		assigneeId: I().optional().describe("User ID to assign task to"),
 		dueDate: I().optional().describe("Due date (ISO string)"),
 		deadline: I().optional().describe("Latest acceptable finish (YYYY-MM-DD for the end of that working day, or an ISO date-time). Critical path analysis reports a miss as negative slack"),
+		earliestStart: I().optional().describe("Earliest the task may start (YYYY-MM-DD for the start of that day, or an ISO date-time), e.g. when something from outside the project arrives"),
 		isMilestone: R().optional().describe("Mark the task as a milestone: a zero-duration checkpoint (release, sign-off) fed by dependencies; its estimate is ignored"),
 		tags: z(I()).optional().describe("Tags for categorization"),
 		estimatedHours: L().optional().describe("Estimated hours to complete"),
@@ -4947,6 +4950,7 @@ var ir = $({
 			assigneeId: e.assigneeId,
 			dueDate: e.dueDate,
 			deadline: e.deadline,
+			earliestStart: e.earliestStart,
 			isMilestone: e.isMilestone,
 			tags: e.tags || [],
 			estimatedHours: e.estimatedHours,
@@ -4978,6 +4982,7 @@ var ir = $({
 		assigneeId: I().optional().describe("User ID to assign the task to"),
 		dueDate: I().optional().describe("Due date (ISO string)"),
 		deadline: I().optional().describe("Latest acceptable finish (YYYY-MM-DD for the end of that working day, or an ISO date-time). Critical path analysis reports a miss as negative slack"),
+		earliestStart: I().optional().describe("Earliest the task may start (YYYY-MM-DD for the start of that day, or an ISO date-time), e.g. when something from outside the project arrives"),
 		isMilestone: R().optional().describe("Mark the task as a milestone: a zero-duration checkpoint (release, sign-off) fed by dependencies; its estimate is ignored"),
 		tags: z(I()).optional().describe("Replaces all tags"),
 		estimatedHours: L().optional().describe("Estimated effort in hours"),
@@ -5056,18 +5061,21 @@ var ir = $({
 	zodSchema: B({
 		taskId: I().describe("The task that waits"),
 		dependsOnTaskId: I().describe("The task that must finish first"),
-		type: H(["blocking", "relates_to"]).optional().describe("'blocking' (default) affects the schedule; 'relates_to' only links the tasks for reference")
+		type: H(["blocking", "relates_to"]).optional().describe("'blocking' (default) affects the schedule; 'relates_to' only links the tasks for reference"),
+		lagHours: L().optional().describe("Working hours to wait after the other task finishes, e.g. 16 for two working days of curing; negative to start that much earlier")
 	}),
 	annotations: { idempotentHint: !0 },
 	execute: async (e, t) => {
-		let n = e.type ?? "blocking", { isEngine: r } = await Yn(t);
-		return r ? t.addDependency({
+		let n = e.type ?? "blocking", r = e.lagHours === void 0 ? {} : { lagHours: e.lagHours }, { isEngine: i } = await Yn(t);
+		return i ? t.addDependency({
 			taskId: e.taskId,
 			dependsOnTaskId: e.dependsOnTaskId,
-			type: n
+			type: n,
+			...r
 		}) : t.addDependency(e.taskId, {
 			dependsOnTaskId: e.dependsOnTaskId,
-			type: n
+			type: n,
+			...r
 		});
 	}
 }), dr = $({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@critical-path/svelte",
-  "version": "0.19.5",
+  "version": "0.19.6",
   "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.27.0",
-    "@critical-path/core": "0.56.0",
-    "@critical-path/mcp": "0.23.0"
+    "@critical-path/client": "0.27.1",
+    "@critical-path/core": "0.57.0",
+    "@critical-path/mcp": "0.24.0"
   },
   "peerDependencies": {
     "svelte": "^5.57.2"