chaim
e40f3d4534
Without Controllers/AssistantRule.php, EspoCRM responds 404 "Controller 'AssistantRule' does not exist" on every POST/GET /api/v1/AssistantRule, even though scopes/AssistantRule.json declares entity=true, object=true, acl=true. The save_rule tool in shira-hermes calls the Record endpoint directly, gets the 404, falls back to nothing (because the user_id branch of the fallback rarely matches), and the LLM tells the user "✅ כלל נשמר" without verification — yet another instance of the hallucination pattern. A one-line Controller class that extends Espo\Core\Controllers\Record exposes the standard CRUD verbs and unlocks the storage path that the rest of the stack already expected. Verified in prod: GET, POST, DELETE all return 200 after this is in place. Paired with shira-hermes 06b27e9 which teaches the LLM to actually read the tool result and never report success on a ❌ response. Refs Task Master #6 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 lines
369 B
JSON
15 lines
369 B
JSON
{
|
|
"name": "SmartAssistant",
|
|
"module": "SmartAssistant",
|
|
"description": "Unified AI Assistant for Legal CRM — floating chat with case memory, office alerts, and AI Gateway integration",
|
|
"author": "klear",
|
|
"version": "2.9.2",
|
|
"acceptableVersions": [
|
|
">=8.0.0"
|
|
],
|
|
"releaseDate": "2026-05-27",
|
|
"php": [
|
|
">=8.1"
|
|
]
|
|
}
|