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

69 lines
2.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: Metrics
feature: metrics
url_prefix: /metrics
ui_apps: {}
tools:
characterize-metric-anomaly:
operation: metrics_characterize_create
enabled: true
scopes:
- metrics:read
annotations:
readOnly: true
destructive: false
idempotent: true
title: Characterize metric anomaly
description_file: ./prompts/characterize-metric-anomaly.md
system_prompt_hint: First call when investigating "metric X looks wrong" — magnitude, onset, which labels moved
feature_flag: metrics
metric-names-list:
operation: metrics_values_retrieve
enabled: true
scopes:
- metrics:read
annotations:
readOnly: true
destructive: false
idempotent: true
title: List metric names
description_file: ./prompts/metric-names-list.md
system_prompt_hint: Discover which server/infrastructure metrics exist before querying them
feature_flag: metrics
response:
include:
- results
metrics-attribute-values-retrieve:
operation: metrics_attribute_values_retrieve
enabled: false
metrics-attributes-retrieve:
operation: metrics_attributes_retrieve
enabled: false
metrics-has-metrics-retrieve:
operation: metrics_has_metrics_retrieve
enabled: false
metrics-samples-create:
operation: metrics_samples_create
enabled: false
query-metrics:
operation: metrics_query_create
enabled: true
scopes:
- metrics:read
annotations:
readOnly: true
destructive: false
idempotent: true
title: Query metrics
description_file: ./prompts/query-metrics.md
system_prompt_hint: Server/infrastructure metrics (OTel/Prometheus) — time series, rates, quantiles, formulas
feature_flag: metrics
response:
include:
- results