bc-telemetry-buddy-mcp 3.3.13 → 3.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +16 -0
- package/dist/cli.js +254 -153
- package/dist/scripts/list-endpoints.js +6 -0
- package/dist/scripts/write-config.js +6 -0
- package/dist/server.js +225 -124
- package/package.json +6 -3
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [3.4.0] - 2026-06-01
|
|
11
|
+
|
|
12
|
+
_Highest blast-radius rating across all plans landed in this release: `low-risk`._
|
|
13
|
+
|
|
14
|
+
### Added
|
|
15
|
+
- **Client-agnostic connection setup workflow**: a guided "set up a connection to my BC telemetry" flow that works from any MCP client (Claude Code, GitHub Copilot agent mode, Cursor) without the VS Code extension. Delivered as both an MCP prompt (`setup-connection`) and an MCP tool (`get_setup_guide`) — both return the same workflow (authenticate → discover Application Insights endpoints → pick endpoint → choose workspace folder, multi-root aware → write `.bctb-config.json` → reload). The server serves these even when unconfigured, so the workflow is always reachable. Single source of truth in `setupInstructions.ts`; also mirrored in [docs/setup/connection-setup.md](../../docs/setup/connection-setup.md). See [docs/plans/done/guided-config-setup.md](../../docs/plans/done/guided-config-setup.md).
|
|
16
|
+
- **Setup helper CLIs** (shipped via `bin`): `bctb-setup-endpoints` enumerates Application Insights resources (`name`, `appId`, …) across subscriptions via Azure CLI, with a manual App-ID fallback when `az` is unavailable; `bctb-setup-write-config` writes or safely merges a connection profile into `.bctb-config.json` (single-profile or named profile, preserving existing profiles and `defaultProfile`). Underlying logic lives in `src/setup/` and is unit-tested; the CLIs are thin esbuild-bundled wrappers.
|
|
17
|
+
- **`SERVER_INSTRUCTIONS` pointer**: unconfigured agents are now directed to the `setup-connection` prompt / `get_setup_guide` tool instead of attempting to query.
|
|
18
|
+
|
|
19
|
+
## [3.3.14] - 2026-05-08
|
|
20
|
+
|
|
21
|
+
_Highest blast-radius rating across all plans landed in this release: `safe`._
|
|
22
|
+
|
|
23
|
+
### Changed
|
|
24
|
+
- **`get_knowledge` mandate reframed in `SERVER_INSTRUCTIONS` + workflow prompt**: Step 2 of the MANDATORY Tool-Call Sequence and `WORKFLOW_PROMPT_CONTENT` step 2 previously framed the KB around "proven KQL patterns" — easy to rationalize away on a simple `summarize count() by eventId` query. The rule now reads "the KB contains customer-specific data patterns (dual streams, tenant mappings, known quirks) AND proven KQL patterns — it tells you HOW and WHERE data flows, not just how to query it. Applies to every query regardless of complexity — no 'too simple for KB' exception." A new FORBIDDEN #7 ("Rationalizing 'the query is too simple for KB'") joins the existing customer-name anti-pattern, with the simple-`count()`-over-half-the-data example. Two new contains-assertions in `server-instructions.test.ts` pin the new phrases. Triggered by a real session that produced a confidently wrong answer over half the data because the basic aggregation skipped the KB lookup that would have surfaced the customer's dual-stream tenant topology. See [docs/plans/done/kb-mandatory-even-simplest.md](../../docs/plans/done/kb-mandatory-even-simplest.md).
|
|
25
|
+
|
|
10
26
|
## [3.3.13] - 2026-05-08
|
|
11
27
|
|
|
12
28
|
_Highest blast-radius rating across all plans landed in this release: `low-risk`._
|