Files
insights/bin/sandbox-mcps.yaml
zeekay 10e6fec4c0 debrand: the brand token is INSIGHTS_, and a wrong one stops the container
The rule table mapped HOG_ -> FN_ ahead of any POSTHOG rule, so POSTHOG_FOO
split into POST + HOG_ and came out POSTFN_FOO. Nothing sets that. The live
pods set INSIGHTS_SKIP_MIGRATION_CHECKS, which bin/migrate-check reads on the
container entrypoint, so the misspelling does not degrade a feature -- it runs
migrate --check against a database whose history this tree does not share and
the container never starts.

Both replacements are measured against the shipped tree rather than chosen:
every HOG_ name with a counterpart there is spelled INSIGHTS_ (HOG_QL ->
INSIGHTS_QL, HOG_FUNCTION_TEMPLATES -> INSIGHTS_FUNCTION_TEMPLATES, 12 of 12
determinate cases), and FN_ appears in it nowhere. Upstream carries 95 HOG_
tokens and zero FN_ ones, so repairing FN_ back out is exactly the inverse of
the bad rule and cannot collide with an upstream name.

The rule is fixed for the next convergence, and the tree it already produced is
repaired in the same commit -- the codemod is idempotent against its own output,
so it cannot undo this itself.
2026-08-01 17:42:28 -07:00

27 lines
1.2 KiB
YAML

# Curated catalog of remote MCP servers that `./bin/sandbox mcp add <name>` can
# register in your sandbox. Opt in by name; your selection lives in
# ~/.insights-sandboxes/mcps.yaml (only ${VAR} references, no tokens), never in git.
#
# Per entry:
# name required - the argument to `sandbox mcp add`
# description required - one-liner shown by `sandbox mcp list`
# env optional - env var names this server needs. `sandbox mcp add`
# prompts (hidden) for any not already in sandbox.env
# and stores them there; the server references them via
# ${VAR}, which Claude expands from the env at runtime.
# server required - the value Claude expects under mcpServers[name]:
# a remote server ({type: http, url, headers}).
#
# Keep entries alphabetical by `name` for stable diffs.
mcps:
- name: insights
description: Insights hosted MCP — insights, flags, errors, SQL
env:
- INSIGHTS_PERSONAL_API_KEY
server:
type: http
url: https://mcp.hanzo.ai/mcp
headers:
Authorization: 'Bearer ${INSIGHTS_PERSONAL_API_KEY}'