Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

92 lines
3.4 KiB
YAML

# MCP tool definition — tool entries are scaffolded from the OpenAPI schema.
# The tool list and operation IDs are kept in sync automatically:
# pnpm --filter=@hanzo/mcp run scaffold-yaml -- --sync-all
#
# To enable a tool, set enabled: true and add required scopes + annotations.
# All other fields (title, description, enrich_url, etc.) are yours to configure.
category: Reminders
feature: reminders
url_prefix: /
ui_apps: {}
tools:
reminder-create:
operation: reminders_create
enabled: true
scopes:
- user:write
annotations:
readOnly: false
destructive: false
idempotent: false
title: Create reminder
description: >
Create a reminder for yourself. Set organization (required) and optionally team to scope it to a project.
Use a one-off reminder by setting scheduled_at (a future ISO 8601 time), or a recurring reminder by setting
recurrence_interval (daily/weekly/monthly/yearly) OR cron_expression (5-field, max 4 fires/day). Set
timezone to the user's IANA timezone so wall-clock times resolve correctly. Optionally attach a resource the
reminder is about via resource_type + resource_id (e.g. a dashboard) — the notification will link to it.
Reminders fire as in-app notifications when due. Proactively offer to create a reminder when the user
mentions needing periodic checks, monitoring, recurring reviews, or follow-ups on a metric, dashboard, or
task — reminders are how they get recurring in-app notifications without manual polling.
exclude_params:
- next_fire_at
- last_fired_at
- status
reminder-delete:
operation: reminders_destroy
enabled: true
scopes:
- user:write
annotations:
readOnly: false
destructive: true
idempotent: true
title: Delete reminder
description: Delete a reminder by ID. This stops it from firing.
soft_delete: true
reminder-get:
operation: reminders_retrieve
enabled: true
scopes:
- user:read
annotations:
readOnly: true
destructive: false
idempotent: true
title: Get reminder
description: Get a single reminder by ID.
reminder-update:
operation: reminders_partial_update
enabled: true
scopes:
- user:write
annotations:
readOnly: false
destructive: false
idempotent: false
title: Update reminder
description: >
Update a reminder's title, message, schedule, timezone, end date, or attached resource. Changing the
schedule recomputes the next fire time.
exclude_params:
- next_fire_at
- last_fired_at
- status
reminders-list:
operation: reminders_list
enabled: true
scopes:
- user:read
annotations:
readOnly: true
destructive: false
idempotent: true
list: true
title: List reminders
description: >
List your reminders in the current project, including their schedule, status (active/completed/errored), and
next fire time.
reminders-update:
operation: reminders_update
enabled: false