@scardis/omnifocus-mcp 0.1.0 → 0.1.2

package/openspec/specs/recurrence/spec.md

@@ -1,51 +0,0 @@
-# recurrence
-
-## Purpose
-
-Covers the construction, assignment, reading, and clearing of `Task.RepetitionRule` values on OmniFocus tasks.
-
-## Requirements
-
-### Requirement: Capability declared
-
-The `recurrence` capability covers the construction, assignment, reading, and clearing of `Task.RepetitionRule` values on OmniFocus tasks. The capability exposes a structured schema matching the OmniFocus UI surface: `frequency` (`daily` | `weekly` | `monthly` | `yearly`), `interval` (every N units, ≥1), `daysOfWeek` (weekly only, any subset of the 7 days), and `method` (`fixed` | `dueDate` | `start`). Repetition is set and cleared through `create_task` and `edit_task`; the current rule is returned by `get_task` as structured fields parsed from the underlying RRULE. Raw RRULE strings are not exposed as input — all recurrence is expressed through the structured schema.
-
-#### Scenario: Capability is named and scoped
-- **WHEN** a change proposes adding or modifying recurrence-related behavior
-- **THEN** it lands requirements under this capability
-
-### Requirement: Set repetition rule on task
-
-The system SHALL accept a `repetitionRule` field in `create_task` and `edit_task`. When provided, the snippet SHALL construct an ICS RRULE string from the structured fields and assign it via `new Task.RepetitionRule(rrule, method)`. The `daysOfWeek` field SHALL only be valid when `frequency` is `"weekly"`; providing it for any other frequency SHALL be a validation error. When `edit_task` receives `repetitionRule: null`, the snippet SHALL assign `task.repetitionRule = null` to clear the rule. When `edit_task` omits `repetitionRule` entirely, the existing rule SHALL be left unchanged.
-
-#### Scenario: Set daily repetition at creation
-- **WHEN** `create_task` is called with `{ name: "Stand-up", repetitionRule: { frequency: "daily", interval: 1, method: "fixed" } }`
-- **THEN** the created task has a repetition rule of every day (fixed interval) and the returned TaskDetail includes the parsed repetitionRule
-
-#### Scenario: Set weekly repetition on specific days
-- **WHEN** `create_task` is called with `{ repetitionRule: { frequency: "weekly", interval: 1, daysOfWeek: ["monday", "wednesday", "friday"], method: "start" } }`
-- **THEN** the task repeats every Mon/Wed/Fri from completion date
-
-#### Scenario: Edit task to add repetition
-- **WHEN** `edit_task` is called with `{ id: "t1", repetitionRule: { frequency: "monthly", interval: 1, method: "dueDate" } }`
-- **THEN** the task's repetition rule is set to monthly (due date) and all other fields are unchanged
-
-#### Scenario: Clear repetition via null
-- **WHEN** `edit_task` is called with `{ id: "t1", repetitionRule: null }`
-- **THEN** the task's repetition rule is cleared and `get_task` returns `repetitionRule: null` for that task
-
-#### Scenario: daysOfWeek on non-weekly frequency is a validation error
-- **WHEN** `create_task` or `edit_task` is called with `{ repetitionRule: { frequency: "daily", daysOfWeek: ["monday"], method: "fixed" } }`
-- **THEN** the tool returns a validation error before any snippet executes
-
-### Requirement: Return repetition rule from get_task
-
-The system SHALL include a `repetitionRule` field in the `TaskDetail` returned by `get_task`. When a task has no repetition rule, the field SHALL be `null`. When a task has a rule, the field SHALL be a structured object with `frequency`, `interval`, `daysOfWeek` (omitted when not applicable), and `method`, parsed from the underlying RRULE and RepetitionMethod.
-
-#### Scenario: get_task returns null when no repetition set
-- **WHEN** `get_task` is called for a task with no repetition rule
-- **THEN** the returned TaskDetail includes `repetitionRule: null`
-
-#### Scenario: get_task returns structured repetition fields
-- **WHEN** `get_task` is called for a task with a weekly repetition rule
-- **THEN** the returned TaskDetail includes `repetitionRule` with `frequency: "weekly"`, correct `interval`, `daysOfWeek` array, and `method`

package/openspec/specs/settings/spec.md

@@ -1,15 +0,0 @@
-# settings
-
-## Purpose
-
-Covers reading OmniFocus application settings and preferences via the OmniJS API. Individual tools and the enumeration of writable keys will be defined in the `settings` change.
-
-## Requirements
-
-### Requirement: Capability declared
-
-The `settings` capability SHALL cover reading OmniFocus application settings and preferences where the OmniJS API exposes them. Write access SHALL be limited to the subset of settings that OmniJS documents as writable; the specific writable keys SHALL be enumerated when the `settings` change is drafted. Requirements for individual tools SHALL be added by that change.
-
-#### Scenario: Capability is named and scoped
-- **WHEN** a future change proposes adding settings tools
-- **THEN** it lands requirements under this capability, with an explicit enumeration of writable keys vs read-only keys

package/openspec/specs/tag-management/spec.md

@@ -1,39 +0,0 @@
-# tag-management
-
-## Purpose
-
-Defines tools for reading and listing OmniFocus tags, including hierarchical tag listing and detail retrieval by ID.
-
-## Requirements
-
-### Requirement: List tags
-
-The system SHALL provide a `list_tags` tool that returns tags in the OmniFocus database as an array of summaries, each containing `{id, name, path, parentId, status}`. Tags form a tree in OmniFocus; the `path` field SHALL use the canonical ` ▸ ` separator and represent the full ancestor chain. The `parentId` field SHALL be `null` for top-level tags. The `status` field SHALL be one of `"active" | "onHold" | "dropped"`. The tool SHALL accept an optional `status` filter string and an optional `limit` integer (default 200). When `status` is omitted, all tags are returned regardless of status. When `limit` is omitted, at most 200 tags are returned.
-
-#### Scenario: All tags returned by default
-- **WHEN** `list_tags` is called with no arguments
-- **THEN** the tool returns all tags (active, onHold, and dropped) up to the limit
-
-#### Scenario: On-hold tag is reported with correct status
-- **WHEN** the database contains a tag that has been placed on hold
-- **THEN** that tag appears in the result with `status: "onHold"`
-
-#### Scenario: Filter by status returns only matching tags
-- **WHEN** `list_tags` is called with `{ filter: { status: "active" } }`
-- **THEN** only active tags are returned
-
-#### Scenario: Limit caps the number of returned tags
-- **WHEN** `list_tags` is called with `{ limit: 5 }`
-- **THEN** at most 5 tags are returned
-
-### Requirement: Get tag by ID
-
-The system SHALL provide a `get_tag` tool that accepts `{id: string}` and returns the full detail record of the named tag, including `{id, name, path, parentId, status, childTagIds}`. If no tag exists with that ID, the tool SHALL return a structured not-found error.
-
-#### Scenario: Existing tag returns full detail
-- **WHEN** `get_tag` is called with the ID of an existing tag
-- **THEN** the tool returns the tag's full detail including the IDs of its immediate child tags
-
-#### Scenario: Missing tag returns not-found error
-- **WHEN** `get_tag` is called with an ID that does not correspond to any tag
-- **THEN** the tool returns a structured error with a not-found code

package/openspec/specs/tag-write/spec.md

@@ -1,49 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Create tag
-
-The system SHALL provide a `create_tag` tool that creates a new OmniFocus tag and returns its full detail record. The tool SHALL accept `{name: string, parentTagId?: string}`. If `parentTagId` is provided the tag SHALL be created nested under that tag; otherwise it SHALL be created at the top level.
-
-#### Scenario: Create top-level tag
-- **WHEN** `create_tag` is called with `{name: "Waiting"}` and no `parentTagId`
-- **THEN** the tool creates the tag at the top level and returns its full detail record including a stable `id`
-
-#### Scenario: Create child tag
-- **WHEN** `create_tag` is called with `{name: "Email", parentTagId: "abc123"}`
-- **THEN** the tool creates the tag nested under the specified parent tag and returns its full detail record with `path` and `parentId` set correctly
-
-#### Scenario: Non-existent parent tag returns not-found error
-- **WHEN** `create_tag` is called with a `parentTagId` that does not correspond to any tag
-- **THEN** the tool returns a structured not-found error
-
-### Requirement: Edit tag
-
-The system SHALL provide an `edit_tag` tool that modifies an existing tag and returns its updated full detail record. The tool SHALL accept `{id: string}` plus any subset of `{name?: string, status?: "active" | "onHold" | "dropped"}`. Fields omitted SHALL be left unchanged.
-
-#### Scenario: Rename a tag
-- **WHEN** `edit_tag` is called with `{id: "abc123", name: "Delegated"}`
-- **THEN** the tag's name is updated and the tool returns the updated detail record
-
-#### Scenario: Put tag on hold
-- **WHEN** `edit_tag` is called with `{id: "abc123", status: "onHold"}`
-- **THEN** the tag's status becomes `"onHold"` and the tool returns the updated detail record
-
-#### Scenario: Non-existent tag returns not-found error
-- **WHEN** `edit_tag` is called with an ID that does not correspond to any tag
-- **THEN** the tool returns a structured not-found error
-
-### Requirement: Delete tag
-
-The system SHALL provide a `delete_tag` tool that permanently deletes a tag and all its child tags using OmniJS `deleteObject()`. Tasks and projects that held the tag have it removed automatically by OmniFocus. The tool description SHALL instruct the AI to confirm with the user before invoking, noting that child tags are also deleted.
-
-#### Scenario: Delete a tag
-- **WHEN** `delete_tag` is called with the ID of an existing tag
-- **THEN** the tag is permanently removed from OmniFocus, all tasks that held it have it removed, and the tool returns a confirmation envelope
-
-#### Scenario: Delete tag with children removes entire subtree
-- **WHEN** `delete_tag` is called with the ID of a tag that has child tags
-- **THEN** the tag and all its descendant tags are deleted
-
-#### Scenario: Non-existent tag returns not-found error
-- **WHEN** `delete_tag` is called with an ID that does not correspond to any tag
-- **THEN** the tool returns a structured not-found error

package/openspec/specs/task-filtering/spec.md

@@ -1,63 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Filter list_tasks results
-
-The system SHALL allow `list_tasks` to accept an optional `filter` object that restricts which tasks are returned. All filter fields are optional and combine as AND conditions. When `filter.status` is omitted, the tool SHALL exclude tasks with status `complete` or `dropped` by default.
-
-Filter fields:
-- `flagged` (boolean): when `true`, return only flagged tasks
-- `status` (array of TaskStatus): return only tasks whose status is in the array; overrides the default exclusion of complete/dropped
-- `tagId` (string): return only tasks that have this tag assigned
-- `dueBeforeDate` (ISO datetime string): return only tasks where `dueDate` is non-null and on or before this date
-
-#### Scenario: Filter by flagged
-- **WHEN** `list_tasks` is called with `{ scope: { all: true }, filter: { flagged: true } }`
-- **THEN** the tool returns only tasks where `flagged` is `true`, excluding complete and dropped tasks
-
-#### Scenario: Filter by status array
-- **WHEN** `list_tasks` is called with `{ scope: { all: true }, filter: { status: ["overdue", "dueSoon"] } }`
-- **THEN** the tool returns only tasks with status `overdue` or `dueSoon`
-
-#### Scenario: Filter by tagId
-- **WHEN** `list_tasks` is called with `{ scope: { projectId: "abc123" }, filter: { tagId: "tag456" } }`
-- **THEN** the tool returns only tasks in that project that have the specified tag assigned
-
-#### Scenario: Filter by dueBeforeDate
-- **WHEN** `list_tasks` is called with `{ scope: { all: true }, filter: { dueBeforeDate: "2026-04-09T23:59:59Z" } }`
-- **THEN** the tool returns only tasks with a non-null dueDate on or before the specified date, excluding complete and dropped tasks
-
-#### Scenario: Default excludes complete and dropped
-- **WHEN** `list_tasks` is called with no filter
-- **THEN** the tool returns tasks with any status except `complete` and `dropped`
-
-#### Scenario: Explicit status filter overrides default exclusion
-- **WHEN** `list_tasks` is called with `{ filter: { status: ["complete"] } }`
-- **THEN** the tool returns completed tasks (the default exclusion does not apply)
-
-#### Scenario: Combined filters act as AND
-- **WHEN** `list_tasks` is called with `{ filter: { flagged: true, tagId: "tag456" } }`
-- **THEN** the tool returns only tasks that are both flagged AND have that tag
-
-### Requirement: Limit list_tasks results
-
-The system SHALL allow `list_tasks` to accept an optional `limit` integer that caps the number of tasks returned. When `limit` is omitted, a default of 200 SHALL apply.
-
-#### Scenario: Default limit of 200
-- **WHEN** `list_tasks` is called without a `limit` and more than 200 tasks match
-- **THEN** the tool returns at most 200 tasks
-
-#### Scenario: Custom limit
-- **WHEN** `list_tasks` is called with `{ limit: 50 }`
-- **THEN** the tool returns at most 50 tasks
-
-### Requirement: Enriched task summary includes dueDate and tagIds
-
-The `TaskSummary` returned by `list_tasks` SHALL include `dueDate` (ISO datetime or null) and `tagIds` (array of tag ID strings) in addition to existing fields.
-
-#### Scenario: Summary includes dueDate
-- **WHEN** `list_tasks` returns a task that has a due date set
-- **THEN** the task summary includes `dueDate` as an ISO datetime string
-
-#### Scenario: Summary includes tagIds
-- **WHEN** `list_tasks` returns a task that has tags assigned
-- **THEN** the task summary includes `tagIds` as an array of tag ID strings

package/openspec/specs/task-management/spec.md

@@ -1,51 +0,0 @@
-# task-management
-
-## Purpose
-
-Defines tools for reading and listing OmniFocus tasks, including scoped listing and full detail retrieval by ID.
-
-## Requirements
-
-### Requirement: List tasks with scope filter
-
-The system SHALL provide a `list_tasks` tool that returns tasks within a caller-specified scope. The scope SHALL be one of: `{projectId: string}`, `{folderId: string}` (all tasks in projects under that folder, recursively), `{inbox: true}`, or `{all: true}` (the full flattened task list). The tool SHALL accept an optional `filter` object (see task-filtering spec) and an optional `limit` integer (default 200). The tool SHALL return an array of task summaries, each containing `{id, name, status, flagged, containerId, containerType, dueDate, tagIds}`. When no `filter.status` is provided, tasks with status `complete` or `dropped` SHALL be excluded by default.
-
-#### Scenario: List tasks in a specific project
-- **WHEN** `list_tasks` is called with `{projectId: "abc123"}`
-- **THEN** the tool returns actionable tasks (non-complete, non-dropped) directly or transitively contained in that project, each carrying the project id as `containerId` and `"project"` as `containerType`
-
-#### Scenario: List inbox tasks
-- **WHEN** `list_tasks` is called with `{inbox: true}`
-- **THEN** the tool returns actionable inbox tasks with `containerType` set to `"inbox"`
-
-#### Scenario: Invalid scope is rejected at the TS boundary
-- **WHEN** `list_tasks` is called with `{projectId: "abc", inbox: true}` (mutually exclusive scopes)
-- **THEN** the tool returns a validation error before any snippet executes
-
-### Requirement: Get task by ID
-
-The system SHALL provide a `get_task` tool that accepts `{id: string}` and returns the full detail record of the named task, including `{id, name, note, status, flagged, deferDate, plannedDate, dueDate, completionDate, estimatedMinutes, containerId, containerType, tagIds, parentTaskId, repetitionRule}`. The `plannedDate` field SHALL be `null` when no planned date is set. The `parentTaskId` field SHALL be `null` for top-level tasks and SHALL contain the parent task's `id.primaryKey` for subtasks. The `repetitionRule` field SHALL be `null` when no repetition rule is set, and SHALL be a structured object with `{frequency, interval, daysOfWeek?, method}` when a rule exists. If no task exists with that ID, the tool SHALL return a structured not-found error.
-
-#### Scenario: Existing task returns full detail
-- **WHEN** `get_task` is called with the ID of an existing task
-- **THEN** the tool returns the task's full detail record including all scalar fields, the list of tag IDs assigned to it, `parentTaskId`, `repetitionRule`, and `plannedDate`
-
-#### Scenario: Subtask includes parentTaskId
-- **WHEN** `get_task` is called with the ID of a subtask
-- **THEN** the returned record includes `parentTaskId` set to the parent task's stable ID
-
-#### Scenario: Task without repetition returns null repetitionRule
-- **WHEN** `get_task` is called for a task with no repetition rule
-- **THEN** the returned TaskDetail includes `repetitionRule: null`
-
-#### Scenario: Task with repetition returns structured repetitionRule
-- **WHEN** `get_task` is called for a task that has a repetition rule
-- **THEN** the returned TaskDetail includes `repetitionRule` with `frequency`, `interval`, `method`, and `daysOfWeek` (if applicable)
-
-#### Scenario: Task with planned date returns plannedDate
-- **WHEN** `get_task` is called for a task that has a planned date set
-- **THEN** the returned TaskDetail includes `plannedDate` as an ISO datetime string
-
-#### Scenario: Missing task returns not-found error
-- **WHEN** `get_task` is called with an ID that does not correspond to any task
-- **THEN** the tool returns a structured error with a not-found code and does not throw an unhandled exception

package/openspec/specs/task-write/spec.md

@@ -1,115 +0,0 @@
-# task-write
-
-## Purpose
-
-TBD — Defines tools for creating and mutating OmniFocus tasks, including create, edit, complete, drop, and delete operations.
-
-## Requirements
-
-### Requirement: Create task
-
-The system SHALL provide a `create_task` tool that creates a new OmniFocus task and returns its full detail record. The tool SHALL accept `{name: string, note?: string, flagged?: boolean, deferDate?: string, plannedDate?: string, dueDate?: string, estimatedMinutes?: number, projectId?: string, parentTaskId?: string, tagIds?: string[], repetitionRule?: RepetitionRuleInput}`. Placement SHALL be determined as follows: if both `projectId` and `parentTaskId` are provided the tool SHALL return an error; if only `projectId` is provided the task is placed at the project root; if only `parentTaskId` is provided the task is created as a subtask inheriting its parent's project; if neither is provided the task is placed in the inbox. When `repetitionRule` is provided, the task SHALL have the specified recurrence set at creation.
-
-#### Scenario: Create inbox task
-- **WHEN** `create_task` is called with `{name: "Buy milk"}` and no `projectId` or `parentTaskId`
-- **THEN** the tool creates the task in the OmniFocus inbox and returns its full detail record including a stable `id`
-
-#### Scenario: Create task in a project
-- **WHEN** `create_task` is called with `{name: "Write tests", projectId: "abc123"}`
-- **THEN** the tool creates the task at the root of the specified project and returns its full detail record
-
-#### Scenario: Create subtask
-- **WHEN** `create_task` is called with `{name: "Review PR", parentTaskId: "xyz789"}`
-- **THEN** the tool creates the task as a child of the specified parent task and returns its full detail record
-
-#### Scenario: Ambiguous placement is rejected
-- **WHEN** `create_task` is called with both `projectId` and `parentTaskId`
-- **THEN** the tool returns a validation error before any snippet executes
-
-#### Scenario: Non-existent project returns not-found error
-- **WHEN** `create_task` is called with a `projectId` that does not correspond to any project
-- **THEN** the tool returns a structured not-found error
-
-#### Scenario: Create task with repetition rule
-- **WHEN** `create_task` is called with `{ name: "Weekly review", repetitionRule: { frequency: "weekly", interval: 1, method: "start" } }`
-- **THEN** the task is created with the specified recurrence and the returned TaskDetail includes the parsed repetitionRule
-
-#### Scenario: Create task with planned date
-- **WHEN** `create_task` is called with `{ name: "Clean kitchen", plannedDate: "2026-04-15T09:00:00Z" }`
-- **THEN** the task is created with the specified planned date and the returned TaskDetail includes `plannedDate`
-
-### Requirement: Edit task
-
-The system SHALL provide an `edit_task` tool that modifies an existing task and returns its updated full detail record. The tool SHALL accept `{id: string}` plus any subset of `{name?: string, note?: string, flagged?: boolean, deferDate?: string | null, plannedDate?: string | null, dueDate?: string | null, estimatedMinutes?: number | null, tagIds?: string[], repetitionRule?: RepetitionRuleInput | null}`. Fields omitted from the call SHALL be left unchanged. When `tagIds` is provided it SHALL replace the task's entire tag set; when omitted, tags SHALL be unchanged. Passing `null` for a date or `estimatedMinutes` SHALL clear the field. Passing `repetitionRule: null` SHALL clear the task's recurrence; passing a `RepetitionRuleInput` object SHALL set or replace the recurrence; omitting `repetitionRule` SHALL leave the existing recurrence unchanged.
-
-#### Scenario: Edit a single field
-- **WHEN** `edit_task` is called with `{id: "abc123", flagged: true}`
-- **THEN** only the `flagged` field is changed; all other fields retain their previous values
-
-#### Scenario: Replace tag set
-- **WHEN** `edit_task` is called with `{id: "abc123", tagIds: ["t1", "t2"]}`
-- **THEN** the task's tags are set to exactly `["t1", "t2"]`, replacing any previously assigned tags
-
-#### Scenario: Clear a date field
-- **WHEN** `edit_task` is called with `{id: "abc123", dueDate: null}`
-- **THEN** the task's due date is cleared
-
-#### Scenario: Clear planned date
-- **WHEN** `edit_task` is called with `{id: "abc123", plannedDate: null}`
-- **THEN** the task's planned date is cleared
-
-#### Scenario: Non-existent task returns not-found error
-- **WHEN** `edit_task` is called with an ID that does not correspond to any task
-- **THEN** the tool returns a structured not-found error
-
-#### Scenario: Non-existent tag ID returns not-found error
-- **WHEN** `edit_task` is called with a `tagIds` array containing an ID that does not correspond to any tag
-- **THEN** the tool returns a structured not-found error and the task is not modified
-
-#### Scenario: Set repetition via edit
-- **WHEN** `edit_task` is called with `{ id: "t1", repetitionRule: { frequency: "monthly", interval: 1, method: "dueDate" } }`
-- **THEN** the task's recurrence is set and all other fields are unchanged
-
-#### Scenario: Clear repetition via edit
-- **WHEN** `edit_task` is called with `{ id: "t1", repetitionRule: null }`
-- **THEN** the task's recurrence is cleared and all other fields are unchanged
-
-### Requirement: Complete task
-
-The system SHALL provide a `complete_task` tool that marks an existing task complete using OmniJS `markComplete()` and returns the task's updated full detail record.
-
-#### Scenario: Complete an existing task
-- **WHEN** `complete_task` is called with the ID of an available task
-- **THEN** the task's status becomes `"complete"` and the tool returns the updated detail record
-
-#### Scenario: Non-existent task returns not-found error
-- **WHEN** `complete_task` is called with an ID that does not correspond to any task
-- **THEN** the tool returns a structured not-found error
-
-### Requirement: Drop task
-
-The system SHALL provide a `drop_task` tool that marks an existing task dropped using OmniJS `drop()` and returns the task's updated full detail record.
-
-#### Scenario: Drop an existing task
-- **WHEN** `drop_task` is called with the ID of an available task
-- **THEN** the task's status becomes `"dropped"` and the tool returns the updated detail record
-
-#### Scenario: Non-existent task returns not-found error
-- **WHEN** `drop_task` is called with an ID that does not correspond to any task
-- **THEN** the tool returns a structured not-found error
-
-### Requirement: Delete task
-
-The system SHALL provide a `delete_task` tool that permanently deletes a task and all its subtasks using OmniJS `deleteObject()`. The tool description SHALL instruct the AI to confirm with the user before invoking this tool, noting that deletion is permanent and includes all subtasks.
-
-#### Scenario: Delete an existing task
-- **WHEN** `delete_task` is called with the ID of an existing task
-- **THEN** the task and all its subtasks are permanently removed from OmniFocus and the tool returns a confirmation envelope
-
-#### Scenario: Delete task with subtasks removes all children
-- **WHEN** `delete_task` is called with the ID of a task that has subtasks
-- **THEN** the task and all descendant subtasks are deleted
-
-#### Scenario: Non-existent task returns not-found error
-- **WHEN** `delete_task` is called with an ID that does not correspond to any task
-- **THEN** the tool returns a structured not-found error

package/openspec/specs/url-automation/spec.md

@@ -1,15 +0,0 @@
-# url-automation
-
-## Purpose
-
-Covers `omnifocus://` URL construction and parsing. Individual tools will be defined in the `url-automation` change.
-
-## Requirements
-
-### Requirement: Capability declared
-
-The `url-automation` capability SHALL cover `omnifocus://` URL construction (including task-paste format for bulk creation, add-to-inbox URLs, and deep links to entities by ID) and parsing of incoming `omnifocus://` URLs into structured form. Requirements for individual tools SHALL be added by the `url-automation` change.
-
-#### Scenario: Capability is named and scoped
-- **WHEN** a future change proposes adding URL-automation tools
-- **THEN** it lands requirements under this capability rather than inventing a new capability name

package/openspec/specs/window-state/spec.md

@@ -1,15 +0,0 @@
-# window-state
-
-## Purpose
-
-Covers read-only inspection of OmniFocus document window state. Window mutation is an explicit non-goal. Individual tools will be defined in the `perspectives-and-windows` change.
-
-## Requirements
-
-### Requirement: Capability declared
-
-The `window-state` capability SHALL cover read-only inspection of OmniFocus document window state, including the currently active window, active perspective, sidebar selection, and content selection. Window *mutation* (resize, close, focus, open) is an explicit non-goal. Requirements for individual tools SHALL be added by the `perspectives-and-windows` change.
-
-#### Scenario: Capability is named and read-only scope is fixed
-- **WHEN** a future change proposes adding window-state tools
-- **THEN** it lands read-only requirements under this capability; any mutation proposal requires first revisiting the non-goal in design

package/scripts/cleanup-fixtures.ts

@@ -1,89 +0,0 @@
-/**
- * Cleanup script: removes any stale __MCP_TEST_*__ folders, __mcp_*__ projects,
- * __MCP_*__ tags, and __mcp_*__ inbox tasks from OmniFocus.
- * Run via: npm run test:cleanup-fixtures
- */
-
-import { spawnSync } from "child_process";
-
-const snippet = `(() => {
-  function deleteFolder(f) {
-    f.flattenedProjects.forEach(function(p) { deleteObject(p); });
-    f.folders.forEach(function(child) { deleteFolder(child); });
-    deleteObject(f);
-  }
-  var removed = [];
-
-  // Stale test folders
-  flattenedFolders.filter(function(f) {
-    return f.name.startsWith('__MCP_TEST_') && f.name.endsWith('__');
-  }).forEach(function(f) { removed.push("folder: " + f.name); deleteFolder(f); });
-
-  // Stale test projects (orphaned at top level by move_project tests)
-  flattenedProjects.filter(function(p) {
-    return p.name.startsWith('__mcp_') && p.name.endsWith('__');
-  }).forEach(function(p) { removed.push("project: " + p.name); deleteObject(p); });
-
-  // Stale test tags
-  flattenedTags.filter(function(t) {
-    return (t.name.startsWith('__mcp_') || t.name.startsWith('__MCP_')) && t.name.endsWith('__');
-  }).forEach(function(t) { removed.push("tag: " + t.name); deleteObject(t); });
-
-  // Stale test inbox tasks
-  inbox.filter(function(t) {
-    return t.name.startsWith('__mcp_') && t.name.endsWith('__');
-  }).forEach(function(t) { removed.push("task: " + t.name); deleteObject(t); });
-
-  return JSON.stringify({ok:true,data:{removed:removed,count:removed.length}});
-})()`;
-
-const script = `
-(function() {
-  var app = Application('OmniFocus');
-  app.includeStandardAdditions = true;
-  try {
-    var r = app.evaluateJavascript(${JSON.stringify(snippet)});
-    $.NSFileHandle.fileHandleWithStandardOutput.writeData(
-      $.NSString.alloc.initWithString(r+'\\n').dataUsingEncoding($.NSUTF8StringEncoding)
-    );
-  } catch(e) {
-    $.NSFileHandle.fileHandleWithStandardOutput.writeData(
-      $.NSString.alloc.initWithString(JSON.stringify({ok:false,error:{message:e.message}})+'\\n').dataUsingEncoding($.NSUTF8StringEncoding)
-    );
-  }
-})();
-`;
-
-const result = spawnSync("osascript", ["-l", "JavaScript"], {
-  input: script,
-  encoding: "utf-8",
-  timeout: 15_000,
-});
-
-const stdout = result.stdout || "";
-const line = stdout.split("\n").find((l) => l.trim().startsWith("{"));
-if (!line) {
-  console.error("No output from OmniFocus:", stdout);
-  process.exit(1);
-}
-
-const parsed = JSON.parse(line) as {
-  ok: boolean;
-  data?: { removed: string[]; count: number };
-  error?: { message: string };
-};
-
-if (!parsed.ok) {
-  console.error("Cleanup failed:", parsed.error?.message);
-  process.exit(1);
-}
-
-const { removed, count } = parsed.data!;
-if (count === 0) {
-  console.log("No stale test fixtures found.");
-} else {
-  console.log(`Removed ${count} stale test fixture(s):`);
-  for (const item of removed) {
-    console.log(`  - ${item}`);
-  }
-}

package/server.json

@@ -1,21 +0,0 @@
-{
-  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
-  "name": "io.github.steveardis/omnifocus",
-  "title": "OmniFocus",
-  "description": "MCP server for OmniFocus (macOS task manager) via Omni Automation JavaScript API. Full CRUD on tasks, projects, folders, and tags, plus repetition rules, planned dates, filtering, and move operations.",
-  "repository": {
-    "url": "https://github.com/steveardis/omnifocus-mcp",
-    "source": "github"
-  },
-  "version": "0.1.0",
-  "packages": [
-    {
-      "registryType": "npm",
-      "identifier": "@scardis/omnifocus-mcp",
-      "version": "0.1.0",
-      "transport": {
-        "type": "stdio"
-      }
-    }
-  ]
-}

package/src/runtime/bridge.ts

@@ -1,97 +0,0 @@
-import { spawn } from "child_process";
-import { loadSnippet } from "./snippetLoader.js";
-import { buildJxaScript } from "./jxaShim.js";
-import { parseResultLine, ExecutionError } from "./resultProtocol.js";
-
-const DEFAULT_TIMEOUT_MS = 30_000;
-
-export interface RunOptions {
-  timeoutMs?: number;
-}
-
-/**
- * Execute an OmniJS snippet inside OmniFocus via the JXA bridge.
- *
- * @param name - Snippet filename (without .js extension) under src/snippets/
- * @param args - Arguments to inject. Embedded as a JSON literal; safe for
- *               all unicode, apostrophes, quotes, etc. (Design Decision 2).
- * @param opts - Optional timeout override (default 30s)
- * @returns The `data` field from the success envelope
- * @throws ExecutionError if the snippet throws inside OmniJS
- * @throws Error on timeout, process errors, or protocol violations
- */
-export async function runSnippet(
-  name: string,
-  args: unknown,
-  opts: RunOptions = {}
-): Promise<unknown> {
-  const timeoutMs = opts.timeoutMs ?? DEFAULT_TIMEOUT_MS;
-
-  // Load and inject args — the only interpolation allowed (Decision 2)
-  const template = loadSnippet(name);
-  const snippet = template.replace("__ARGS__", JSON.stringify(args));
-
-  // Wrap snippet in JXA shim
-  const jxaScript = buildJxaScript(snippet);
-
-  return new Promise((resolve, reject) => {
-    const MAX_OUTPUT_BYTES = 10 * 1024 * 1024; // 10 MB
-
-    const ac = new AbortController();
-    const timer = setTimeout(() => {
-      ac.abort();
-      child.kill("SIGKILL");
-      reject(new Error(`Snippet "${name}" timed out after ${timeoutMs}ms`));
-    }, timeoutMs);
-
-    const child = spawn("osascript", ["-l", "JavaScript"], {
-      signal: ac.signal,
-    });
-
-    let stdout = "";
-    let stderr = "";
-
-    child.stdout.on("data", (chunk: Buffer) => {
-      stdout += chunk.toString();
-      if (stdout.length > MAX_OUTPUT_BYTES) {
-        child.kill("SIGKILL");
-        clearTimeout(timer);
-        reject(new Error(`Snippet "${name}" exceeded maximum output size`));
-      }
-    });
-
-    child.stderr.on("data", (chunk: Buffer) => {
-      stderr += chunk.toString();
-    });
-
-    child.on("error", (err) => {
-      clearTimeout(timer);
-      if ((err as NodeJS.ErrnoException).code === "ABORT_ERR") return; // handled by timer
-      reject(err);
-    });
-
-    child.on("close", (code) => {
-      clearTimeout(timer);
-      try {
-        const envelope = parseResultLine(stdout);
-        if (envelope.ok) {
-          resolve(envelope.data);
-        } else {
-          reject(new ExecutionError(envelope.error));
-        }
-      } catch (parseErr) {
-        const hint = stdout.slice(0, 200) || stderr.slice(0, 200);
-        reject(
-          new Error(
-            `Failed to parse bridge output for snippet "${name}" (exit ${code})` +
-              (hint ? `: ${hint}` : "")
-          )
-        );
-      }
-    });
-
-    // Write JXA script to stdin
-    child.stdin.write(jxaScript);
-    child.stdin.end();
-  });
-}

package/src/runtime/index.ts

@@ -1,4 +0,0 @@
-export { runSnippet, type RunOptions } from "./bridge.js";
-export { loadSnippet, clearSnippetCache } from "./snippetLoader.js";
-export { parseResultLine, ExecutionError, type ResultEnvelope } from "./resultProtocol.js";
-export { buildJxaScript } from "./jxaShim.js";