@aitne-sh/aitne 0.1.7 → 0.1.9

package/agent-assets/skills/management-task-stop/SKILL.md

@@ -1,166 +0,0 @@
----
-name: management-task-stop
-description: Stop (hard-delete) an existing managed task (`mt_<n>`) from a DM — "stop the daily Zoom check", "cancel mt_42". Owns DELETE on §B rows. SKIP for cadence tweaks (modify), pause (no soft-pause), or one-off skip.
-when_to_use: User wants to end a recurring agent commitment. SKIP for cadence / intent / output-path tweaks (`management-task-modify`), pause-then-resume (no soft-pause exists; user must re-register), or removing a one-off scheduled task (`schedule` skill DELETE).
-allowed-tools:
-  - Bash(curl *)
-  - Bash(jq *)
-  - Read
----
-
-# Stop a Managed Task
-
-Hard-deletes a managed-task row. The `recurring_schedules` row
-cascade-deletes via FK and any pending `agent_schedule` rows for the
-old cron are cancelled. History is preserved entirely in
-`agent_actions` (`action_type='management_task.deleted'`) and
-`md_file_snapshots` — there is no soft-stop placeholder in the
-file (ADR §8.5).
-
-## When to use
-
-The user clearly asks to **end** a recurring commitment:
-
-- "Stop the daily Zoom check"
-- "Cancel `mt_42`"
-- "Remove the gmail invoice triage — I'm not reading those anymore"
-- "I don't need the Drive receipts pull anymore"
-
-## When NOT to use
-
-| Shape | Use instead |
-|---|---|
-| User wants to keep it running but tweak it | `management-task-modify` |
-| User wants to pause for a few days then resume | No soft-pause exists. Stop now; user re-registers when they want it back. Spell this out in the confirmation. |
-| User wants to skip exactly one upcoming run | DELETE the pending `/api/schedule/:id` row (the row in `agent_schedule`); the next slot fires normally. Use the `schedule` skill. |
-| User wants to drop a one-off `/api/schedule` reminder | `schedule` skill DELETE |
-| User wants to clear `_activity/<source>.md` | The reconciler regenerates it within 90 days; nothing to delete here |
-
-## Algorithm (mirror of design 21 §10.3)
-
-### Step 1 — Locate the row
-
-Same lookup as `management-task-modify`. Either the user named the id
-directly, or you fuzzy-match by `(app, cadence, intent)`.
-
-```bash
-curl -s "http://localhost:8321/api/managed-tasks/mt_42" | jq .item
-# or:
-curl -s "http://localhost:8321/api/managed-tasks" | jq '.items[] | select(.app_normalized == "zoom")'
-```
-
-GET-by-id wraps the row in `{item:<row>}`; the list returns
-`{items:[…], count:N}`.
-
-If multiple rows could match, list them and ask which to stop. Stop
-until the user picks. **Never stop more than one row in a single
-turn.** A bulk stop ("stop all gmail tasks") requires explicit
-confirmation per row.
-
-If no row matches, DM:
-
-> No managed task for `<app>` is registered.
-
-### Step 2 — Confirm with the user (Notify tier — destructive)
-
-DELETE on a managed task is **Notify tier** (§13.1) AND removes a
-recurring commitment that the user themselves set up. Both safety
-invariants ("destructive ops require user confirmation" from
-CLAUDE.md, plus the Notify-tier policy) demand a real DM confirmation.
-Output language: follow `<output_language_policy>`. Never auto-stop.
-
-> Stop `mt_42` Zoom check (daily 10:00 JST · last run ok 3 new)? It
-> won't auto-resume.
-
-If the user declines, stop the flow. If they amend ("actually just
-make it weekly"), route to `management-task-modify` instead — do not
-stop and re-register on their behalf.
-
-The "last run" line in the confirmation matters: a row that has been
-silently failing (`consecutive_failures ≥ 3`) is exactly the kind the
-user is most likely stopping by mistake (they may not realize the
-failures alone are the problem). Surface `last_result` so they can
-make an informed call.
-
-### Step 3 — DELETE /api/managed-tasks/:id
-
-```bash
-curl -sS -X DELETE http://localhost:8321/api/managed-tasks/mt_42
-```
-
-The server-side transaction (atomic):
-
-a. snapshots the row's full state into `agent_actions.detail`,
-b. DELETEs `managed_tasks` (cascades to `recurring_schedules` via FK),
-c. cancels pending `agent_schedule` rows for the old cron,
-d. re-renders `rules/management.md` from DB (locked + snapshotted into
-   `md_file_snapshots`),
-e. INSERTs `agent_actions` (`action_type='management_task.deleted'`,
-   `detail={mt_id, original_row, deleted_at, by_user_message}`).
-
-The pre-delete file snapshot in `md_file_snapshots` plus the
-`detail.original_row` blob in `agent_actions` together let the user
-or the activity-view reconciler reconstruct the row at any later
-date — there is no further "soft-stop" archive needed.
-
-### Step 4 — Confirm to user
-
-One DM:
-
-> Stopped `mt_42` Zoom check. The row is gone from the registry; ask
-> me to register a new one any time.
-
-Persona / language rules from `notify` apply. Don't list the internal
-mechanics ("snapshotted, cascade-deleted") — the audit log is for
-the agent, not the user.
-
-The `_activity/zoom.md` file's "Recently changed (90d)" section
-auto-updates within ~10 s as the activity-view reconciler picks up
-the new `agent_actions` row. You do NOT touch that file.
-
-## Error envelope
-
-| HTTP | `error` | What to do |
-|---|---|---|
-| 400 | `invalid_id` | The `:id` segment didn't match `^mt_[1-9]\d*$`; ask the user to repeat |
-| 404 | `not_found` | DM "No managed task with that id"; if you used a fuzzy match, re-list candidates |
-| 5xx | `internal_error` | Surface `body.message` if present; advise `aitne logs` |
-
-The daemon's DELETE is unconditional — there is no `running_now` /
-`?force=true` in-flight guard today. If the cascade collides with a
-fire that is mid-execution the dispatcher's retry / orphan-detection
-path picks it up; do not try to "wait for it to finish" in the skill.
-
-The pre-delete row snapshot in `agent_actions` (`detail.original_row`)
-together with the file snapshot in `md_file_snapshots` is the
-recovery surface — surface it in audit/debug contexts only, never in
-the user-facing DM.
-
-## What this skill does NOT do
-
-- Does NOT pause / disable. There is no soft-stop; the row is gone.
-  If the user wants a temporary hiatus, tell them they'll need to
-  re-register when ready.
-- Does NOT delete entity files (`<domain>/<type-plural>/<slug>.md`)
-  produced by past runs. Those stay; the user's notes / receipts are
-  not the agent's to discard.
-- Does NOT regenerate `_activity/<source>.md`. The reconciler does.
-- Does NOT manipulate `recurring_schedules` directly. DELETE
-  `/api/managed-tasks/:id` is the chokepoint; cascade is automatic.
-- Does NOT touch §A (SoT bindings) or §C (Active Policies).
-- Does NOT PUT `rules/management.md` directly. The daemon owns the
-  file write.
-- Does NOT bulk-stop without per-row confirmation. "Stop all gmail
-  tasks" is a series of DM round-trips, one per row.
-
-## API summary
-
-| Verb + path | Used in |
-|---|---|
-| `GET /api/managed-tasks` / `/api/managed-tasks/:id` | Step 1 (lookup) |
-| `DELETE /api/managed-tasks/:id` | Step 3 (Notify-tier; destructive) |
-| `POST /api/notify` | Step 4 (user-facing confirmation) |
-
-The DELETE writes one `agent_actions` row, snapshots the file, and
-cascades the schedule — do NOT call any separate audit / cleanup
-endpoint.

package/agent-assets/skills/receipts/SKILL.md

@@ -1,134 +0,0 @@
----
-name: receipts
-description: Load when the user asks about receipts/invoices, tax-prep needs an annual list, or an unsaved receipt should be filed.
-when_to_use: Downloads Gmail-observer-flagged attachments to the user's external Obsidian vault, separate from the agent's primary management store.
-allowed-tools:
-  - Bash(curl *)
-  - Read
----
-
-# Receipt & Document Manager
-
-The daemon's Gmail observer scans travel-booking emails for PDF/image
-attachments and can retain previously detected generic documents.
-Attachment metadata is stored in the `receipts` SQLite table. Actual files
-are downloaded on demand and can be saved to the user's **external**
-Obsidian vault (separate from the agent's primary management store).
-
-## When to Use
-
-- **User asks about receipts**: list detected receipts, check save status.
-- **Tax preparation season**: generate annual receipt list, save unsaved receipts.
-- **Monthly/yearly review**: report on receipt collection completeness.
-
-## Workflow
-
-1. Fetch receipt list from `/api/receipts`.
-2. To save a receipt to the external Obsidian vault, download via
-   `/api/receipts/:id/download` then save to the vault via
-   `POST /api/obsidian/notes` and update the receipt record with the
-   vault-relative path via `PATCH /api/receipts/:id`. (`obsidianPath` is
-   a path inside the external vault, not the primary management store.)
-3. For tax preparation, filter by date range and category.
-
----
-
-## API Reference
-
-Base URL: `http://localhost:8321`
-
-### GET /api/receipts
-
-List detected receipt attachments.
-
-```bash
-# All receipts
-curl -s "http://localhost:8321/api/receipts?limit=50"
-
-# Unsaved receipts only
-curl -s "http://localhost:8321/api/receipts?saved=false"
-
-# Filter by category
-curl -s "http://localhost:8321/api/receipts?category=document"
-```
-
-| Param | Type | Default | Description |
-|-------|------|---------|-------------|
-| `category` | string | — | document, travel |
-| `saved` | boolean | — | true = saved to Obsidian, false = not yet saved |
-| `limit` | number | 50 | Max results (1–200) |
-
-Response:
-```json
-{
-  "receipts": [
-    {
-      "id": 1,
-      "gmailMessageId": "18f...",
-      "attachmentId": "ANGj...",
-      "filename": "receipt.pdf",
-      "mimeType": "application/pdf",
-      "sizeBytes": 45000,
-      "category": "document",
-      "obsidianPath": null,
-      "savedAt": null,
-      "createdAt": "2026-04-12T10:00:00Z"
-    }
-  ],
-  "total": 1
-}
-```
-
-### GET /api/receipts/summary
-
-Receipt statistics.
-
-```bash
-curl -s "http://localhost:8321/api/receipts/summary"
-```
-
-Response:
-```json
-{
-  "total": 25,
-  "saved": 10,
-  "unsaved": 15,
-  "byCategory": [
-    { "category": "document", "count": 23 },
-    { "category": "travel", "count": 2 }
-  ]
-}
-```
-
-### POST /api/receipts/:id/download
-
-Download the actual attachment file from Gmail.
-
-```bash
-curl -s -X POST "http://localhost:8321/api/receipts/1/download" -o receipt.pdf
-```
-
-### PATCH /api/receipts/:id
-
-Update receipt metadata (change category or mark as saved).
-
-```bash
-# Mark as saved to Obsidian
-curl -s -X PATCH "http://localhost:8321/api/receipts/1" \
-  -H "Content-Type: application/json" \
-  -d '{"obsidianPath": "receipts/2026/04/amazon-receipt.pdf"}'
-
-# Reclassify a receipt
-curl -s -X PATCH "http://localhost:8321/api/receipts/1" \
-  -H "Content-Type: application/json" \
-  -d '{"category": "travel"}'
-```
-
----
-
-## External Obsidian Vault Save Convention
-
-Save receipts to: `receipts/YYYY/MM/<merchant>-<date>.<ext>` inside the
-external Obsidian vault.
-
-Example: `receipts/2026/04/amazon-2026-04-12.pdf`

package/agent-assets/skills/travel/SKILL.md

@@ -1,132 +0,0 @@
----
-name: travel
-description: Load when the user asks about an upcoming trip or reservation, morning routines need to surface travel within the next 7 days, or reviews need a travel overview — flight, hotel, restaurant, train, and bus bookings detected by the Gmail observer.
-allowed-tools:
-  - Bash(curl *)
-  - Read
----
-
-# Travel & Booking Tracker
-
-The daemon's Gmail observer detects booking confirmation emails from airlines,
-hotels, OTAs, restaurant reservation platforms, and rail services. Data is
-stored in the `travel_bookings` SQLite table.
-
-## When to Use
-
-- **Morning routine**: include upcoming travel/bookings in today.md.
-- **Evening review**: report newly detected bookings.
-- **User asks about trips/reservations**: query bookings and summarize.
-- **Pre-trip reminders**: surface upcoming travel day before departure.
-
-## Workflow
-
-1. Fetch upcoming bookings from `/api/travel-bookings/upcoming`.
-2. For morning routine, highlight bookings within the next 7 days.
-3. For evening review, check for newly detected bookings (today's createdAt).
-
----
-
-## API Reference
-
-Base URL: `http://localhost:8321`
-
-### GET /api/travel-bookings
-
-List travel bookings with optional filters.
-
-```bash
-# All bookings
-curl -s "http://localhost:8321/api/travel-bookings?limit=20"
-
-# Filter by type
-curl -s "http://localhost:8321/api/travel-bookings?type=flight"
-
-# Upcoming only
-curl -s "http://localhost:8321/api/travel-bookings?status=upcoming"
-
-# Date range
-curl -s "http://localhost:8321/api/travel-bookings?from=2026-04-01&to=2026-05-01"
-```
-
-| Param | Type | Default | Description |
-|-------|------|---------|-------------|
-| `type` | string | — | flight, hotel, restaurant, train, bus, other |
-| `status` | string | all | upcoming, completed, cancelled, all |
-| `from` | ISO date | — | Bookings with start_date on or after |
-| `to` | ISO date | — | Bookings with start_date before |
-| `limit` | number | 50 | Max results (1–200) |
-
-Response:
-```json
-{
-  "bookings": [
-    {
-      "id": 1,
-      "type": "flight",
-      "provider": "United",
-      "destination": null,
-      "startDate": "2026-05-15T10:30:00Z",
-      "endDate": null,
-      "confirmationNumber": "ABC123",
-      "amount": 350,
-      "currency": "USD",
-      "status": "upcoming",
-      "gmailMessageId": "18f...",
-      "createdAt": "2026-04-12T10:00:00Z"
-    }
-  ],
-  "total": 1
-}
-```
-
-### GET /api/travel-bookings/upcoming
-
-Convenience endpoint for upcoming bookings sorted by start date.
-
-```bash
-curl -s "http://localhost:8321/api/travel-bookings/upcoming?limit=10"
-```
-
-### PATCH /api/travel-bookings/:id
-
-Update booking status or destination.
-
-```bash
-curl -s -X PATCH "http://localhost:8321/api/travel-bookings/1" \
-  -H "Content-Type: application/json" \
-  -d '{"status": "completed"}'
-```
-
----
-
-## Formatting Guide
-
-### Morning routine — today.md
-
-```
-## Travel & Reservations
-Upcoming flight: United to SFO (May 15) — confirmation ABC123
-Hotel: Marriott SF (May 15-17) — confirmation XYZ789
-Restaurant: OpenTable reservation tonight 19:00
-```
-
-Omit section if no upcoming bookings within 7 days.
-
-### Evening review
-
-```
-## New Bookings Detected
-- United flight: May 15, confirmation ABC123, $350
-```
-
-### Booking type display names
-
-| type value | Display name |
-|------------|-------------|
-| flight | Flight |
-| hotel | Hotel |
-| restaurant | Restaurant |
-| train | Train |
-| bus | Bus |
-| other | Reservation |

package/agent-assets/skills/travel-time/SKILL.md

@@ -1,158 +0,0 @@
----
-name: travel-time
-description: Load when a calendar event needs a departure time, the user asks about commute / transit duration, or a reminder includes "leave by HH:MM".
-when_to_use: Backed by Google Maps Directions — requires `googleMapsApiKey` in the daemon secret store; falls back gracefully when missing.
-allowed-tools:
-  - Bash(curl *)
-  - Read
----
-
-# Travel Time & Commute Optimizer
-
-Uses the Google Maps Directions API to estimate travel time between locations.
-Integrates with the calendar to compute departure times for events with
-location fields.
-
-**Prerequisite**: Google Maps API key must be configured in the daemon's
-secret store (`googleMapsApiKey`). The API key needs the Directions API
-enabled.
-
-## When to Use
-
-- **Morning routine**: check today's calendar events with locations,
-  compute departure times, add to today.md.
-- **User asks about commute/travel time**: query specific routes.
-- **Pre-event reminders**: DM departure time suggestions.
-
-## Workflow
-
-1. Fetch today's calendar events. The right call depends on the current
-   Google Calendar mode (read `<integration_modes>` injected at session
-   start):
-<!-- mode:direct:google_calendar -->
-   Direct mode → `GET /api/calendar/events?date=today&days=1`
-   (see the `external-services` skill).
-<!-- /mode:direct:google_calendar -->
-<!-- mode:delegated-same:google_calendar -->
-   Same-backend delegated → use this session backend's native Calendar
-   list-events MCP tool. `/api/calendar/events` returns 410.
-<!-- /mode:delegated-same:google_calendar -->
-<!-- mode:delegated-cross:google_calendar -->
-   Cross-backend delegated → `POST /api/integrations/google_calendar/exec`
-   with a natural-language `task` + `outputSchema` (see the
-   `external-services` skill — cross-backend variant for worked
-   examples).
-<!-- /mode:delegated-cross:google_calendar -->
-<!-- mode:native:google_calendar -->
-   Native mode → use this session backend's native Calendar
-   list-events MCP tool (same call shape as `delegated-same`). The
-   materialized `external-services` skill body
-   (`SKILL.native.<session-backend>.md`) lists the per-backend tool
-   names. The daemon does not proxy in native mode;
-   `/api/calendar/events` returns 410 and
-   `/api/integrations/google_calendar/exec` returns 410 too.
-<!-- /mode:native:google_calendar -->
-<!-- mode:disabled:google_calendar -->
-   Disabled → skip this skill; there is no calendar to source events from.
-<!-- /mode:disabled:google_calendar -->
-2. For events with a `location` field, call `/api/travel-time` or
-   `/api/travel-time/for-event/:eventId` to get travel duration.
-3. Include departure time recommendations in today.md or DM.
-
----
-
-## API Reference
-
-Base URL: `http://localhost:8321`
-
-### GET /api/travel-time
-
-Estimate travel time between two locations.
-
-```bash
-# Transit (default)
-curl -s "http://localhost:8321/api/travel-time?origin=Grand+Central&destination=Times+Square"
-
-# Driving with arrival time
-curl -s "http://localhost:8321/api/travel-time?origin=Brooklyn&destination=Newark&mode=driving&arrival=2026-04-12T14:00:00-04:00"
-```
-
-| Param | Type | Default | Description |
-|-------|------|---------|-------------|
-| `origin` | string | (required) | Origin address or place name |
-| `destination` | string | (required) | Destination address or place name |
-| `mode` | string | transit | driving, transit, walking, bicycling |
-| `arrival` | ISO 8601 | — | Desired arrival time (computes departure time) |
-
-Response:
-```json
-{
-  "origin": "Grand Central Terminal, NY",
-  "destination": "Times Square, NY",
-  "mode": "transit",
-  "durationSeconds": 1380,
-  "durationText": "23 mins",
-  "distanceMeters": 8500,
-  "distanceText": "8.5 km",
-  "departBy": "2026-04-12T13:34:00.000Z"
-}
-```
-
-### GET /api/travel-time/for-event/:eventId
-
-Estimate travel time for a specific calendar event.
-
-```bash
-curl -s "http://localhost:8321/api/travel-time/for-event/abc123?origin=Home&mode=transit"
-```
-
-| Param | Type | Default | Description |
-|-------|------|---------|-------------|
-| `origin` | string | (required) | Your starting location |
-| `mode` | string | transit | Travel mode |
-
-Response:
-```json
-{
-  "event": {
-    "id": "abc123",
-    "summary": "Team meeting",
-    "location": "WeWork Times Square",
-    "start": "2026-04-12T14:00:00-04:00"
-  },
-  "travelTime": {
-    "origin": "Home, NY",
-    "destination": "WeWork Times Square, NY",
-    "mode": "transit",
-    "durationSeconds": 2400,
-    "durationText": "40 mins",
-    "distanceMeters": 15000,
-    "distanceText": "15 km",
-    "departBy": "2026-04-12T13:16:00.000Z"
-  }
-}
-```
-
----
-
-## Formatting Guide
-
-### Morning routine — today.md
-
-```
-## Commute & Travel
-14:00 Team meeting @ WeWork Times Square — depart by 13:15 (transit, 40 min)
-18:30 Dinner @ Restaurant ABC — depart by 18:00 (transit, 25 min)
-```
-
-Only include events that have a `location` field.
-Omit section if no events with locations today.
-
-### Mode display names
-
-| mode | Display |
-|------|---------|
-| transit | Transit |
-| driving | Driving |
-| walking | Walking |
-| bicycling | Bicycle |