Expose ticket attachment tools to ticket-aware agents

[adriandemian]

Summary

• Exposed the new read-only ticket attachment tools to the ticket-aware agent surfaces that handle ticket references, and kept them out of surfaces that do not have that contract.
• Preserved the no-secret URL constraint on fetch_ticket_attachment descriptions while tightening the tool-surface tests around the filtered MCP output.
• Updated the Rust ticket attachment service and the generated MCP server bundle/tests so the backend and plugin surface stay aligned.

User Impact

Agents that work with ticket references can now see and use the ticket attachment read-only tools through their normal MCP/tool surface. Agents without that ticket-reference contract do not receive those tools.

Technical Context

The change spans both sides of the integration:

• src-tauri/src/application/ticket_attachment_service.rs and its tests now cover the backend behavior behind ticket attachment access.
• src-tauri/src/infrastructure/agents/harness_agent_catalog_tests.rs adds coverage for which agent harnesses should and should not receive the ticket attachment tools.
• plugins/app/ralphx-mcp-server/src/ticket-attachment-tools.ts and the matching generated build/* outputs update the MCP server surface and tool description checks.
• plugins/app/ralphx-mcp-server/src/__tests__/tools.test.ts adds assertions for both the exposed tool set and the description contract.

Risks / Follow-Ups

• The exposure is intentionally narrow. Any additional ticket-aware agent surface will need matching MCP/prompt contract alignment before it can see these tools.
• The contract depends on the generated plugin bundle staying in sync with the source MCP definitions.

---

Generated by RalphX

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}