- Coordinator tools in its own chat (super admin only): list_extensions,
set_extension_access, delete_extension, and update_skill /
update_mcp_server / update_custom_tool for what can't change where
anything is sent (on/off, names, arguments, left-out tools)
- Adding a skill, MCP server or tool, or changing a skill's words, a
server's URL or headers or a tool's kind or config, goes through
propose_skill / propose_mcp_server / propose_custom_tool: stored in
extension_proposals with the bot's background check, shown as a
[proposal:ID] chip that opens a card with Confirm and Reject
- The card's facts are worked out by the app from what Confirm saves: the
host, every {{env.KEY}} and whether it's saved, the config; for a skill
its links, hosts, tool names, mentions of secrets and a diff against
the saved runbook
- Confirming decides once and checks again; a server or tool missing a key
is saved switched off, and the outcome is posted to the bot in chat
- Never from a bot: stdio servers, a URL whose host a template decides,
envs in a prompt tool, a key's value
Co-Authored-By: Claude Opus 5.5 <[email protected]>
18 lines
593 B
TypeScript
18 lines
593 B
TypeScript
import { describe, expect, test } from "bun:test";
|
|
import mergeTemplateMap from "./merge-template-map";
|
|
|
|
describe("mergeTemplateMap", () => {
|
|
test("sets, replaces and removes entries, keeping the rest", () => {
|
|
expect(
|
|
mergeTemplateMap({
|
|
current: { A: "1", B: "2", C: "3" },
|
|
changes: { B: "two", C: null, D: "4" },
|
|
}),
|
|
).toEqual({ A: "1", B: "two", D: "4" });
|
|
});
|
|
|
|
test("leaves the map alone without changes", () => {
|
|
expect(mergeTemplateMap({ current: { A: "1" } })).toEqual({ A: "1" });
|
|
});
|
|
});
|