fix(FN-2392): normalize skill-facing tool references to fn_*
- Update Fusion skill docs, prompts, and capability references to use public fn_* tool names consistently - Align engine system prompts and tool schemas for messaging/task actions with fn_send_message, fn_read_messages, fn_task_* naming - Refresh related tests across CLI, engine, dashboard, and core to match normalized tool naming and behavior - Add a patch changeset for @runfusion/fusion describing the skill-tool namespace normalization
This commit is contained in:
@@ -5,6 +5,8 @@
|
||||
|
||||
<objective>
|
||||
Guide the agent through creating well-specified tasks and organizing work using the mission hierarchy for complex multi-phase projects.
|
||||
|
||||
All tool examples in this workflow intentionally use the public `fn_*` extension namespace.
|
||||
</objective>
|
||||
|
||||
<process>
|
||||
|
||||
@@ -5,6 +5,8 @@
|
||||
|
||||
<objective>
|
||||
Guide the agent through creating, viewing, and managing tasks on the Fusion board using pi extension tools.
|
||||
|
||||
Use only the public `fn_*` extension tools in this workflow. Do not substitute internal engine runtime tools like `task_create`, `task_update`, `task_log`, or `task_done`.
|
||||
</objective>
|
||||
|
||||
<process>
|
||||
|
||||
Reference in New Issue
Block a user