mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
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.
115 lines
4.2 KiB
YAML
115 lines
4.2 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: Annotations
|
|
feature: annotations
|
|
url_prefix: /data-management/annotations
|
|
ui_apps: {}
|
|
tools:
|
|
annotation-create:
|
|
operation: annotations_create
|
|
enabled: true
|
|
scopes:
|
|
- annotation:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: false
|
|
idempotent: false
|
|
title: Create annotation
|
|
description: >
|
|
Create an annotation to mark an important change (for example, a deployment) on charts and trends. Provide a
|
|
note in `content`, when it happened in `date_marker` (ISO 8601), and whether it is scoped to the current
|
|
`project` or the whole `organization`. Optionally set an `emoji` to show in place of the default badge on
|
|
the chart.
|
|
include_params:
|
|
- content
|
|
- date_marker
|
|
- scope
|
|
- emoji
|
|
- hidden_in_user_interface
|
|
annotation-delete:
|
|
operation: annotations_destroy
|
|
enabled: true
|
|
scopes:
|
|
- annotation:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: true
|
|
idempotent: true
|
|
title: Delete annotation
|
|
description: >
|
|
Soft-delete an annotation by ID. This hides the annotation from normal lists while preserving historical
|
|
records.
|
|
soft_delete: true
|
|
annotation-retrieve:
|
|
operation: annotations_retrieve
|
|
enabled: true
|
|
scopes:
|
|
- annotation:read
|
|
annotations:
|
|
readOnly: true
|
|
destructive: false
|
|
idempotent: true
|
|
title: Retrieve annotation
|
|
description: >
|
|
Retrieve a single annotation by ID from the current project. Use this when you already know the annotation
|
|
ID and want complete details.
|
|
param_overrides:
|
|
id:
|
|
cast: string-int
|
|
annotations-list:
|
|
operation: annotations_list
|
|
enabled: true
|
|
scopes:
|
|
- annotation:read
|
|
annotations:
|
|
readOnly: true
|
|
destructive: false
|
|
idempotent: true
|
|
list: true
|
|
title: List annotations
|
|
description: >
|
|
List annotations in the current project, newest first. Use this to review existing deployment markers and
|
|
analysis notes before adding new annotations. Results are paginated (default 100 per page) — use `limit` and
|
|
`offset` to page through, and `search` to filter by annotation content. Each row's `created_by` is trimmed
|
|
to `{id, email}`.
|
|
param_overrides:
|
|
limit:
|
|
description: Number of annotations to return per page (default 100).
|
|
default: 100
|
|
response:
|
|
exclude:
|
|
- created_by.uuid
|
|
- created_by.distinct_id
|
|
- created_by.first_name
|
|
- created_by.last_name
|
|
- created_by.is_email_verified
|
|
- created_by.mascot_config
|
|
- created_by.role_at_organization
|
|
annotations-partial-update:
|
|
operation: annotations_partial_update
|
|
enabled: true
|
|
scopes:
|
|
- annotation:write
|
|
annotations:
|
|
readOnly: false
|
|
destructive: false
|
|
idempotent: true
|
|
title: Update annotation
|
|
description: >
|
|
Update an existing annotation by ID. You can change its text (`content`), when it happened (`date_marker`,
|
|
ISO 8601), its visibility scope (`project` or `organization`), or its `emoji`. Only the fields you provide
|
|
are updated.
|
|
include_params:
|
|
- content
|
|
- date_marker
|
|
- scope
|
|
- emoji
|
|
- hidden_in_user_interface
|
|
annotations-update:
|
|
operation: annotations_update
|
|
enabled: false
|