fix(llm): The system prompt's "Available actions" list was stale — it listed phantom tools (create_task, delete_task, get_note) that don't exist and omitted most real tools. The model would spiral or fail silently when users asked to create tasks under a project. Replaced the hardcoded string with a dynamically-built actions list matching all registered tools, with conditional caldav/searxng extensions.
Test plan
Chat 258 confirmed: model now creates tasks via create_note(status='todo') under the correct project without confusion
Verify caldav and searxng tools appear in actions list when configured
## Summary
- **fix(llm):** The system prompt's "Available actions" list was stale — it listed phantom tools (`create_task`, `delete_task`, `get_note`) that don't exist and omitted most real tools. The model would spiral or fail silently when users asked to create tasks under a project. Replaced the hardcoded string with a dynamically-built actions list matching all registered tools, with conditional caldav/searxng extensions.
## Test plan
- [x] Chat 258 confirmed: model now creates tasks via `create_note(status='todo')` under the correct project without confusion
- [ ] Verify caldav and searxng tools appear in actions list when configured
- [ ] Verify workspace instruction references `create_note` (not `create_task`)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
create_task,delete_task,get_note) that don't exist and omitted most real tools. The model would spiral or fail silently when users asked to create tasks under a project. Replaced the hardcoded string with a dynamically-built actions list matching all registered tools, with conditional caldav/searxng extensions.Test plan
create_note(status='todo')under the correct project without confusioncreate_note(notcreate_task)