@starascendin/lifeos-mcp 0.7.74 → 0.7.75

package/README.md

@@ -95,8 +95,8 @@ Add to your `.mcp.json` (project root or `~/.claude/mcp.json`):
 - **get_tasks** - Get tasks with filters (project, status, priority)
 - **get_todays_tasks** - Get today's tasks and top priorities
 - **get_overdue_tasks** - Get open tasks that are already overdue
-- **create_issue** - Create a new task/issue, optionally with a calendar start/end time
-- **update_issue** - Update an existing task, including estimate/story points and scheduled calendar time
+- **create_issue** - Create a new task/issue, optionally with an initial issue calendar block
+- **update_issue** - Update an existing task, including estimate/story points and due date
 - **mark_issue_complete** - Mark a task as done
 - **create_calendar_block** - Create protected calendar-only time without creating a PM issue or Google event
 

package/dist/build-info.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.7.74";
-export declare const BUILD_TIME = "2026-05-18T17:40:32.368Z";
+export declare const VERSION = "0.7.75";
+export declare const BUILD_TIME = "2026-05-19T19:39:48.444Z";

package/dist/build-info.js

@@ -1,3 +1,3 @@
 // AUTO-GENERATED — do not edit. Regenerated on every build.
-export const VERSION = "0.7.74";
-export const BUILD_TIME = "2026-05-18T17:40:32.368Z";
+export const VERSION = "0.7.75";
+export const BUILD_TIME = "2026-05-19T19:39:48.444Z";

package/dist/index.js

@@ -326,15 +326,15 @@ const TOOLS = [
                 },
                 scheduledStartAt: {
                     type: "string",
-                    description: "Calendar start datetime in ISO format like '2026-05-18T09:00:00-07:00' (optional)",
+                    description: "First issue calendar block start datetime in ISO format like '2026-05-18T09:00:00-07:00' (optional, separate from dueDate)",
                 },
                 scheduledEndAt: {
                     type: "string",
-                    description: "Calendar end datetime in ISO format like '2026-05-18T10:30:00-07:00' (optional, required when scheduledStartAt is provided)",
+                    description: "First issue calendar block end datetime in ISO format like '2026-05-18T10:30:00-07:00' (optional, required when scheduledStartAt is provided)",
                 },
                 scheduledTimezone: {
                     type: "string",
-                    description: "IANA timezone for the scheduled block, e.g. 'America/Los_Angeles' (optional)",
+                    description: "IANA timezone for the issue calendar block, e.g. 'America/Los_Angeles' (optional)",
                 },
                 cycleId: {
                     type: "string",
@@ -437,11 +437,11 @@ const TOOLS = [
                 },
                 scheduledStartAt: {
                     type: "string",
-                    description: "Calendar start datetime in ISO format like '2026-05-18T09:00:00-07:00' (optional)",
+                    description: "Legacy calendar start datetime. Prefer apply_planning_patch schedule_issue to add issue calendar blocks.",
                 },
                 scheduledEndAt: {
                     type: "string",
-                    description: "Calendar end datetime in ISO format like '2026-05-18T10:30:00-07:00' (optional)",
+                    description: "Legacy calendar end datetime. Prefer apply_planning_patch schedule_issue to add issue calendar blocks.",
                 },
                 scheduledTimezone: {
                     type: "string",
@@ -1008,7 +1008,7 @@ const TOOLS = [
     },
     {
         name: "apply_planning_patch",
-        description: "Apply an agent-generated day/week/cycle planning patch. Mutates tasks, due dates, scheduled start/end times, protected non-ticket calendar blocks, top priorities, current cycle goals/assignments, daily fields, issue comments, Daily AI Comments, Weekly AI Comments, and daily/weekly notes.",
+        description: "Apply an agent-generated day/week/cycle planning patch. Mutates tasks, due dates, issue calendar blocks, protected non-ticket calendar blocks, top priorities, current cycle goals/assignments, daily fields, issue comments, Daily AI Comments, Weekly AI Comments, and daily/weekly notes.",
         inputSchema: {
             type: "object",
             properties: {
@@ -1035,7 +1035,7 @@ const TOOLS = [
                 },
                 operations: {
                     type: "array",
-                    description: "Operations to apply. Supported types: create_issue, create_calendar_block, update_issue, schedule_issue, assign_issue_to_current_cycle, set_top_priority, mark_issue_status, save_daily_note, save_weekly_note, set_daily_field, update_cycle_goals, add_issue_comment, add_daily_ai_comment, add_weekly_ai_comment.",
+                    description: "Operations to apply. Supported types: create_issue, create_calendar_block, update_issue, schedule_issue, assign_issue_to_current_cycle, set_top_priority, mark_issue_status, save_daily_note, save_weekly_note, set_daily_field, update_cycle_goals, add_issue_comment, add_daily_ai_comment, add_weekly_ai_comment. dueDate is the issue deadline/day assignment. schedule_issue adds one issue calendar block and can be repeated for multiple blocks.",
                     items: {
                         type: "object",
                         properties: {
@@ -1060,7 +1060,7 @@ const TOOLS = [
                             },
                             payload: {
                                 type: "object",
-                                description: "Operation-specific payload. Use issueIdOrIdentifier for existing tasks, dueDate for day assignment/deadlines, scheduledStartAt/scheduledEndAt for PM issue time blocks. Use create_calendar_block with title, timezone, and either startAt/endAt ISO datetimes or date plus startTime/endTime for protected calendar-only blocks that must not create an issue.",
+                                description: "Operation-specific payload. Use issueIdOrIdentifier for existing tasks, dueDate for day assignment/deadlines, and schedule_issue with scheduledStartAt/scheduledEndAt or date plus startTime/endTime to add an issue calendar block. Use create_calendar_block with title, timezone, and either startAt/endAt ISO datetimes or date plus startTime/endTime for protected calendar-only blocks that must not create an issue.",
                             },
                         },
                         required: ["type", "payload"],
@@ -5492,11 +5492,12 @@ ${notesClause}
 
 Workflow:
 1. Call get_planning_context with daily=true, weekly=true, currentCycle=true, backlog=true, habits=true, dailyFields=true, calendar=true, voiceMemos=true.
-2. Decide today's top 3, tasks to assign to the day via dueDate, tasks to time-block via scheduledStartAt/scheduledEndAt, protected non-ticket calendar blocks to create with create_calendar_block, backlog items to pull into the current cycle, and any cycle goal updates.
+2. Decide today's top 3, tasks to assign to the day or deadline via dueDate, issue calendar blocks to add with schedule_issue, protected non-ticket calendar blocks to create with create_calendar_block, backlog items to pull into the current cycle, and any cycle goal updates.
 3. Call apply_planning_patch with mode "day" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
    - create_calendar_block for protected non-ticket time like errands, meals, dog walking, appointments, or holds; this must not create a PM issue
-   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
+   - update_issue for dueDate, status, priority, and estimate changes
+   - schedule_issue for each issue calendar block using issueIdOrIdentifier plus scheduledStartAt/scheduledEndAt, or date plus startTime/endTime; repeat for multiple blocks
    - assign_issue_to_current_cycle for current cycle work
    - set_top_priority for today's top 3
    - update_cycle_goals when the current cycle goal should change
@@ -5621,11 +5622,12 @@ ${notesClause}
 
 Workflow:
 1. Call get_planning_context with daily=true, weekly=true, currentCycle=true, backlog=true, habits=true, dailyFields=true, calendar=true, voiceMemos=true.
-2. Shape the week around the current cycle: update cycle goals, pull/assign tasks, assign tasks to days with dueDate, time-block tasks with scheduledStartAt/scheduledEndAt, create protected non-ticket calendar blocks with create_calendar_block, and set near-term priorities.
+2. Shape the week around the current cycle: update cycle goals, pull/assign tasks, assign tasks to days or deadlines with dueDate, add issue calendar blocks with schedule_issue, create protected non-ticket calendar blocks with create_calendar_block, and set near-term priorities.
 3. Call apply_planning_patch with mode "week" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
    - create_calendar_block for protected non-ticket time like errands, meals, dog walking, appointments, or holds
-   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
+   - update_issue for dueDate, status, priority, and estimate changes
+   - schedule_issue for each issue calendar block using issueIdOrIdentifier plus scheduledStartAt/scheduledEndAt, or date plus startTime/endTime; repeat for multiple blocks
    - assign_issue_to_current_cycle for current cycle work
    - set_top_priority for immediate focus
    - update_cycle_goals for the active cycle
@@ -5649,12 +5651,13 @@ Do not ask for confirmation; the user intends this planning workflow to mutate L
                     text: `Help me plan my current cycle/sprint in LifeOS and apply the resulting mutations.
 
 1. Call get_planning_context with currentCycle=true, backlog=true, weekly=true, daily=true.
-2. Shape the current cycle: update cycle goals, pull/assign tasks, assign near-term tasks with dueDate, time-block tasks with scheduledStartAt/scheduledEndAt, create protected non-ticket calendar blocks with create_calendar_block, and set near-term priorities.
+2. Shape the current cycle: update cycle goals, pull/assign tasks, assign near-term tasks to days or deadlines with dueDate, add issue calendar blocks with schedule_issue, create protected non-ticket calendar blocks with create_calendar_block, and set near-term priorities.
 3. Call apply_planning_patch with mode "cycle" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
    - create_calendar_block for protected non-ticket time that should appear on the calendar without creating a PM issue
    - assign_issue_to_current_cycle for current cycle work
-   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
+   - update_issue for dueDate, status, priority, and estimate changes
+   - schedule_issue for each issue calendar block using issueIdOrIdentifier plus scheduledStartAt/scheduledEndAt, or date plus startTime/endTime; repeat for multiple blocks
    - update_cycle_goals for active cycle goals
    - save_daily_note or save_weekly_note when useful as the readable plan artifact
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@starascendin/lifeos-mcp",
-  "version": "0.7.74",
+  "version": "0.7.75",
   "description": "MCP server for LifeOS Project Management - manage projects, tasks, notes, and contacts via AI assistants",
   "type": "module",
   "main": "dist/index.js",