feat: add lyzr-tools plugin bridging Lyzr-authorized tools into GitAgent

[akshatkumar2808]

Summary

• Adds a lyzr-tools plugin that discovers Lyzr-authorized tools (Gmail, Slack, MCP servers) and proxies execution through Lyzr instead of requiring separate local credentials
• Registers discovered tools as lyzr_-prefixed GitAgent tools; unauthorized tools return a structured authorization_required result instead of prompting for local credentials
• Redacts secrets from tool result details; adds prompt guidance preferring lyzr_* tools over local duplicate skills
• Enabled by default in agent.yaml; no-ops with a warning if LYZR_API_KEY isn't set (no network call without a key)

See docs/lyzr-tool-auth-rca.md for the RCA/design and docs/lyzr-tool-bridge-test-cases.md for the acceptance criteria this targets.

Test plan

• npm run build && npm test — 59/59 passing (32 new in test/lyzr-tools.test.ts, no real network calls)
• Verified end-to-end through the real plugin loader (not just mocks): no-API-key no-op path, and full discovery→register→execute cycle against a local HTTP stub

[shreyas-lyzr]

Four issues worth addressing before merge — one is a confirmed functional break on the default config, one is a silent misconfiguration that yields a broken user experience with no log output to help diagnose it, one is a schema normalization gap that silently drops valid tool parameters, and one is a key-based redaction limitation that can let raw credential strings through to model context. Inline comments below.

[shreyas-lyzr]

normalizeInputSchema only passes through schemas that are plain objects with a properties key. If Lyzr returns an action schema in OpenAI function-calling style — where parameters is an array of { name, type, description } objects, which is a common ACI format — that array fails the "properties" in schema check and is silently replaced with { properties: {} }.

The tool registers with no known parameters; the model has to guess argument names, which causes silent failures for any required fields.

At minimum, handle the array case by converting it to a JSON Schema object shape:

Suggested change

	function normalizeInputSchema(schema: unknown): { properties: Record<string, any>; required?: string[] } {
	function normalizeInputSchema(schema: unknown): { properties: Record<string, any>; required?: string[] } {
	if (Array.isArray(schema)) {
	// OpenAI/ACI-style: [{name, type, description, required?}]
	const properties: Record<string, any> = {};
	const required: string[] = [];
	for (const p of schema as Array<Record<string, any>>) {
	if (!p.name) continue;
	properties[p.name] = { type: p.type ?? "string", description: p.description ?? "" };
	if (p.required) required.push(p.name);
	}
	return required.length ? { properties, required } : { properties };
	}
	if (schema && typeof schema === "object" && "properties" in (schema as Record<string, unknown>)) {
	return schema as { properties: Record<string, any>; required?: string[] };
	}
	return { properties: {} };
	}