@armature-tech__mcp-analytics@0.6.36.patchfix(mcp): stop coercing external callers into sending telemetry.agent_thinking
Manufact's app-directory readiness review flagged apps/server's external MCP
server for telemetry over-collection: @armature-tech/mcp-analytics decorates
every registered tool's inputSchema with an optional `telemetry` object, but
its shipped field descriptions told the calling model to supply
`agent_thinking` "on every call" / "even when the field is marked optional" —
strong enough language that an external MCP client (one that never reads
Cedar's own system prompt) would treat it as mandatory regardless of the
JSON Schema's real optionality.
Patch @armature-tech/mcp-analytics@0.6.36 (via pnpm patch, same mechanism as
the existing postgres/@superglue/client patches) to soften that wording to
genuinely read as optional, without touching the underlying `.optional()`
zod schema (already correct) or the field's usefulness to Cedar's own
first-party agents, which keep sending it voluntarily because Cedar's own
operating conventions ask for it independent of this SDK's tool-schema text.
Co-Authored-By: Claude Sonnet 5 <<email>>Sep 19, 2026, 1:46 PM@superglue__client@3.2.2.patchfixing superglue patchApr 14, 2026, 2:24 PMpostgres.patchfeat(account-setup): wire email-analysis into account setup, fetch corpus safely from any environment
Adds a headless way to trigger and wait for initial sync from account-setup-from-transcript
(new `cedar-cli account-setup trigger-sync`/`wait-sync`, backed by the real
`admin.triggerInitialSync`/`getInitialSyncProgress` routes) instead of a human manually
driving the Playground UI. Rewrites Phase 7 to use it and adds Phase 7b to run the
email-analysis skill afterward, replacing the account_context.sentEmails-bootstrapped
email-style.md with real corpus-derived content once sync has populated real deal history.
fetch-corpus previously wrote its output to a local /tmp file on whichever server handled
the request — unusable once cedar-cli is pointed at a deployed environment instead of local
dev, since that file lands somewhere the caller has no filesystem access to. Adds a --remote
flag (new fetchCorpusToAccountContext route) that persists the corpus into
user_settings.account_context.emailAnalysisCorpus and returns it directly over the wire, so
cedar-cli can write it to the caller's own local /tmp instead — same downstream path
convention either way.
Also includes: two hard-won guardrails baked into the email-analysis skill this session
(always use exact .md-suffixed paths for existence checks; cold-outreach exclusion is
categorical, never an account-specific exception) after both caused real incidents across
a ~30-account rollout; a design doc for a deferred-task-creation approach we considered and
explicitly decided not to build yet; and a postgres client patch fixing a real crash
(process-ending TypeError on a connection dropped mid-write) confirmed under real load.
Co-Authored-By: Claude Sonnet 5 <<email>>Jul 11, 2026, 2:22 PM