fruxon 2.2.9__tar.gz → 2.3.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (237) hide show
  1. {fruxon-2.2.9 → fruxon-2.3.0}/HISTORY.md +84 -0
  2. {fruxon-2.2.9 → fruxon-2.3.0}/PKG-INFO +9 -6
  3. {fruxon-2.2.9 → fruxon-2.3.0}/README.md +8 -5
  4. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/__init__.py +0 -4
  5. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/_version.py +2 -2
  6. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/checks/agent.py +148 -6
  7. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/__init__.py +3 -1
  8. fruxon-2.3.0/src/fruxon/cli/access_requests.py +289 -0
  9. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_sandbox.py +14 -1
  10. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/applications.py +65 -4
  11. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/applications_entry_points.py +262 -13
  12. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/assets.py +110 -0
  13. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/escalation_desks.py +14 -2
  14. fruxon-2.3.0/src/fruxon/cli/escalation_operators.py +277 -0
  15. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/escalations.py +62 -1
  16. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/examples.py +23 -11
  17. fruxon-2.3.0/src/fruxon/cli/integrations_webhooks.py +392 -0
  18. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers.py +0 -1
  19. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/fruxon.py +321 -117
  20. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/models.py +26 -49
  21. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/sandbox_scenario.py +16 -1
  22. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-agent-mode/SKILL.md +3 -0
  23. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-build-agent/SKILL.md +30 -26
  24. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-meet/SKILL.md +8 -1
  25. {fruxon-2.2.9 → fruxon-2.3.0}/tests/.test_durations.json +0 -1
  26. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agents_check_cli.py +26 -0
  27. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_assets.py +109 -0
  28. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_checks_agent.py +1 -1
  29. fruxon-2.3.0/tests/test_cli_friction_round3.py +738 -0
  30. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_entry_points.py +5 -0
  31. fruxon-2.3.0/tests/test_escalation_operators.py +274 -0
  32. fruxon-2.2.9/src/fruxon/cli/pipelines.py +0 -307
  33. fruxon-2.2.9/tests/test_pipelines.py +0 -412
  34. {fruxon-2.2.9 → fruxon-2.3.0}/.gitignore +0 -0
  35. {fruxon-2.2.9 → fruxon-2.3.0}/LICENSE +0 -0
  36. {fruxon-2.2.9 → fruxon-2.3.0}/pyproject.toml +0 -0
  37. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/__main__.py +0 -0
  38. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/_request_id.py +0 -0
  39. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/_ssl.py +0 -0
  40. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/checks/__init__.py +0 -0
  41. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/checks/ledger.py +0 -0
  42. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/checks/references.py +0 -0
  43. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_crash.py +0 -0
  44. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_last_failure.py +0 -0
  45. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_ledger_passes.py +0 -0
  46. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_plugin_hint.py +0 -0
  47. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_schema.py +0 -0
  48. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_shared.py +0 -0
  49. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/_stream.py +0 -0
  50. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents.py +0 -0
  51. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_approvals.py +0 -0
  52. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_budget.py +0 -0
  53. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_channels.py +0 -0
  54. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_draft.py +0 -0
  55. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_evaluations.py +0 -0
  56. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_executions.py +0 -0
  57. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_improvements.py +0 -0
  58. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_lifecycle.py +0 -0
  59. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_memory.py +0 -0
  60. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_reply_style.py +0 -0
  61. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_revisions.py +0 -0
  62. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_sandbox_test.py +0 -0
  63. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_slots.py +0 -0
  64. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_system_blocks.py +0 -0
  65. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_tests.py +0 -0
  66. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_topics.py +0 -0
  67. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/agents_voice_calls.py +0 -0
  68. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/auth.py +0 -0
  69. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/capabilities.py +0 -0
  70. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/completion.py +0 -0
  71. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/config.py +0 -0
  72. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/consult_pins.py +0 -0
  73. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/conversation_imports.py +0 -0
  74. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/dash.py +0 -0
  75. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/describe.py +0 -0
  76. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/doctor.py +0 -0
  77. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/environments.py +0 -0
  78. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/feedback.py +0 -0
  79. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/guides.py +0 -0
  80. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/integrations.py +0 -0
  81. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/integrations_sandbox.py +0 -0
  82. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/keys.py +0 -0
  83. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/knowledge_bases.py +0 -0
  84. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/knowledge_documents.py +0 -0
  85. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/knowledge_notices.py +0 -0
  86. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/knowledge_sources.py +0 -0
  87. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/llm_providers.py +0 -0
  88. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/messages.py +0 -0
  89. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/metrics.py +0 -0
  90. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/participants.py +0 -0
  91. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/secrets.py +0 -0
  92. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/skills.py +0 -0
  93. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/storage.py +0 -0
  94. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/tools.py +0 -0
  95. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_budget.py +0 -0
  96. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_check.py +0 -0
  97. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_ledger.py +0 -0
  98. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_ledger_stage_tests.py +0 -0
  99. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_questions.py +0 -0
  100. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/triggers_shape.py +0 -0
  101. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/working_hours.py +0 -0
  102. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/cli/workspaces.py +0 -0
  103. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/credentials.py +0 -0
  104. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/device_auth.py +0 -0
  105. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/doctor.py +0 -0
  106. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/exceptions.py +0 -0
  107. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/flow_validation.py +0 -0
  108. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/output.py +0 -0
  109. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/params.py +0 -0
  110. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/__init__.py +0 -0
  111. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-create-integration/SKILL.md +0 -0
  112. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-debug-trace/SKILL.md +0 -0
  113. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/skills/fruxon-use-integrations/SKILL.md +0 -0
  114. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/telemetry.py +0 -0
  115. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/__init__.py +0 -0
  116. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/app.py +0 -0
  117. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/demo.py +0 -0
  118. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/links.py +0 -0
  119. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/__init__.py +0 -0
  120. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/agent.py +0 -0
  121. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/base.py +0 -0
  122. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/home.py +0 -0
  123. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/ledger.py +0 -0
  124. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/loader.py +0 -0
  125. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/pickers.py +0 -0
  126. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/screens/trace.py +0 -0
  127. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/source.py +0 -0
  128. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/theme.py +0 -0
  129. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/views.py +0 -0
  130. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/tui/widgets.py +0 -0
  131. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/ui.py +0 -0
  132. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/update_check.py +0 -0
  133. {fruxon-2.2.9 → fruxon-2.3.0}/src/fruxon/validation.py +0 -0
  134. {fruxon-2.2.9 → fruxon-2.3.0}/tests/__init__.py +0 -0
  135. {fruxon-2.2.9 → fruxon-2.3.0}/tests/conftest.py +0 -0
  136. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_actor.py +0 -0
  137. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agent_lifecycle.py +0 -0
  138. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agent_revisions_list.py +0 -0
  139. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agent_slots.py +0 -0
  140. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agents_revisions_cli.py +0 -0
  141. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_agents_sandbox.py +0 -0
  142. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_applications.py +0 -0
  143. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_approvals.py +0 -0
  144. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_budgets.py +0 -0
  145. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_capabilities.py +0 -0
  146. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_channels.py +0 -0
  147. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_checks_ledger.py +0 -0
  148. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli.py +0 -0
  149. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli_base_url_routing.py +0 -0
  150. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli_crash.py +0 -0
  151. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli_feedback.py +0 -0
  152. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli_friction_round2.py +0 -0
  153. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_cli_root_flags.py +0 -0
  154. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_client.py +0 -0
  155. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_connect_nudge.py +0 -0
  156. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_consult.py +0 -0
  157. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_conversation_imports.py +0 -0
  158. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_credentials.py +0 -0
  159. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_dash_app.py +0 -0
  160. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_dash_cli.py +0 -0
  161. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_dash_client.py +0 -0
  162. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_dash_links.py +0 -0
  163. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_dash_source.py +0 -0
  164. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_describe.py +0 -0
  165. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_device_auth.py +0 -0
  166. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_docs_commands_exist.py +0 -0
  167. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_doctor.py +0 -0
  168. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_draft_bootstrap.py +0 -0
  169. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_draft_evaluate_cli.py +0 -0
  170. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_draft_pull_shape.py +0 -0
  171. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_draft_run_replay.py +0 -0
  172. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_draft_validate_cli.py +0 -0
  173. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_drafts.py +0 -0
  174. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_environments.py +0 -0
  175. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_escalations.py +0 -0
  176. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_evaluations.py +0 -0
  177. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_execution_records.py +0 -0
  178. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_flow_validation.py +0 -0
  179. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_fruxon.py +0 -0
  180. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_guides.py +0 -0
  181. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_improvements.py +0 -0
  182. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_integration_configs_write_cli.py +0 -0
  183. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_integration_sandbox_cli.py +0 -0
  184. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_integration_triggers_cli.py +0 -0
  185. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_integrations_authorize_cli.py +0 -0
  186. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_integrations_connect_cli.py +0 -0
  187. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_kb_trial_cli.py +0 -0
  188. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_knowledge_bases.py +0 -0
  189. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_knowledge_documents.py +0 -0
  190. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_knowledge_notices.py +0 -0
  191. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_knowledge_sources.py +0 -0
  192. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_llm_provider_configs_cli.py +0 -0
  193. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_llm_providers_connect_cli.py +0 -0
  194. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_llm_providers_list_cli.py +0 -0
  195. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_managed_by.py +0 -0
  196. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_memory.py +0 -0
  197. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_messages.py +0 -0
  198. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_metrics.py +0 -0
  199. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_online_llm_config_refs.py +0 -0
  200. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_online_prefetch_refs.py +0 -0
  201. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_online_secret_refs.py +0 -0
  202. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_output.py +0 -0
  203. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_params.py +0 -0
  204. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_participants.py +0 -0
  205. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_participants_write.py +0 -0
  206. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_plugin_hint.py +0 -0
  207. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_project_urls.py +0 -0
  208. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_reply_style.py +0 -0
  209. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_request_id.py +0 -0
  210. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_sandbox_scenario.py +0 -0
  211. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_schema.py +0 -0
  212. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_schema_fetch.py +0 -0
  213. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_secrets.py +0 -0
  214. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_skills.py +0 -0
  215. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_ssl.py +0 -0
  216. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_storage.py +0 -0
  217. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_system_blocks.py +0 -0
  218. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_system_blocks_cli.py +0 -0
  219. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_telemetry.py +0 -0
  220. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_test_chats.py +0 -0
  221. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_topics.py +0 -0
  222. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_trigger_budgets.py +0 -0
  223. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers.py +0 -0
  224. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_check_cli.py +0 -0
  225. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_ledger.py +0 -0
  226. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_ledger_batch_views.py +0 -0
  227. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_ledger_stage_tests.py +0 -0
  228. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_questions.py +0 -0
  229. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_shape.py +0 -0
  230. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_triggers_write.py +0 -0
  231. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_tui_boundary.py +0 -0
  232. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_ui.py +0 -0
  233. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_update_check.py +0 -0
  234. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_validation.py +0 -0
  235. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_voice_calls.py +0 -0
  236. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_working_hours_cli.py +0 -0
  237. {fruxon-2.2.9 → fruxon-2.3.0}/tests/test_workspaces_cli.py +0 -0
@@ -1,5 +1,89 @@
1
1
  # History
2
2
 
3
+ ## Unreleased — taking a Telegram channel live from the CLI
4
+
5
+ - **`fruxon integrations configs webhook generate|rotate|apply|inspect|remove <integration> <config>`**
6
+ (F-024): register the provider webhook a connection receives on. Connecting Telegram from the CLI never
7
+ registered it, so the bot received nothing. The minted URL is printed only with `--show-url`, or when it
8
+ could not be registered; `rotate` / `remove` need `--yes` in agent mode (EXIT 16); a URL the provider
9
+ refused exits 12. **`FruxonClient.generate_config_webhook_url`**, **`rotate_config_webhook`**,
10
+ **`apply_config_webhook`**, **`inspect_config_webhook`**, **`remove_config_webhook`**, **`get_connector_info`**.
11
+ - **`applications entry-points connect`** reports where the connection's provider webhook stands as
12
+ `webhook: {status, message, source}` — the server's `INSTALLED` / `ALREADY_INSTALLED` / `UNVERIFIED` /
13
+ `MANUAL_INSTALL_REQUIRED` / `FAILED` (a `FAILED` is retried once from the CLI). The connection's URL is
14
+ printed only with `--show-url` or while it still needs registering. Against a server that does not
15
+ install on connect, the CLI registers it itself for auto-install providers (`--no-webhook` skips).
16
+ `ConnectedChannel.webhook` carries the server's report.
17
+ - **`agents check`**: the **Inbound path** row asks the provider and fails when it does not deliver to
18
+ this config (`registeredToThisConfig: false`, or no URL on older servers); a new **Unknown senders** row
19
+ warns when a messaging channel is on `REQUEST_ACCESS`.
20
+ - **`fruxon access-requests list|get|approve|reject`** (F-025): the senders a channel is holding for
21
+ approval. **`FruxonClient.list_access_requests`**, **`get_access_request`**, **`approve_access_request`**,
22
+ **`reject_access_request`**.
23
+ - **`--unknown-senders REQUEST_ACCESS|REJECT|PROVISION|OPEN`** on `applications entry-points update` (with
24
+ `--inherit-unknown-senders`) and on the new **`fruxon applications update`**; passed through for the server
25
+ to validate. **`FruxonClient.update_application`**; `update_entry_point(unknown_sender_admission=…,
26
+ clear_unknown_sender_admission=…)`; `EntryPoint.unknown_sender_admission` and
27
+ `Application.unknown_sender_admission`.
28
+ - **Sandbox escalations are marked rehearsals** (F-023): `escalate_to_human` tool frames carry
29
+ `"rehearsal": true` and `agents sandbox turn` prints "escalation rehearsed — nobody was paged".
30
+ `escalations list --include-rehearsals` (`list_escalations(include_rehearsals=True)`,
31
+ `EscalationQueueItem.is_rehearsal`, `rehearsal` in the JSON) asks for rehearsal bridges, and warns when the
32
+ server ignored it.
33
+ - **Unreachable operators are not staffing** (F-028): `agents check`'s Escalation row (and `draft validate
34
+ --online`) subtracts the policy's `unreachableOperators` from the ladder — a desk whose operators can all
35
+ not be reached reaches nobody; some unreachable is a `warn`. `escalations policy` lists them with the
36
+ reason. `EscalationPolicy.unreachable_operators`.
37
+ - **`applications entry-points get <entry-point>`** takes the id alone (`FruxonClient.find_entry_point`).
38
+
39
+ ## Unreleased — collection pipelines removed (breaking)
40
+
41
+ The backend retired collection pipelines as a product: the
42
+ `/collectionPipelines` routes, the `run_pipeline` / `start_pipeline` agent
43
+ tools, the per-step `pipelines` binding and a trigger's pipeline target are
44
+ gone, so every call below already returned 404 or an empty value.
45
+
46
+ - **`fruxon pipelines list|get`** removed, with its `fruxon examples pipelines`
47
+ entries.
48
+ - **`FruxonClient.list_collection_pipelines`** and
49
+ **`get_collection_pipeline`** removed, and the **`CollectionPipeline`** and
50
+ **`PipelineSourceRef`** types are no longer exported.
51
+ - **`TriggerDetail.pipeline_id`** removed, and `fruxon triggers get -o json`
52
+ no longer prints `pipelineId`.
53
+ - The `fruxon-build-agent` skill no longer lists the `pipelines` config or
54
+ its "Binding a collection pipeline" section. To run an agent per item, give
55
+ a schedule trigger a work shape; `fruxon triggers ledger` inspects its items.
56
+
57
+ The `pipelines:read|write|run` token scopes are unchanged; the backend still
58
+ defines them.
59
+
60
+ ## Unreleased — Application operators from the CLI
61
+
62
+ - **`fruxon escalations operators list|candidates|add|remove`**: make a participant an operator of an
63
+ Application, so an escalation desk can name them. `desks create --operator` and `set-policy
64
+ --operator` only accept active operators, and adding one used to need the dashboard (Application →
65
+ People). `candidates [--search …] [--limit …]` shows the server's verdict per person: `ELIGIBLE`,
66
+ `PROMOTABLE` (not yet classified — `add` marks them internal) or `INELIGIBLE` with a reason. `add`
67
+ is idempotent and re-activates a disabled operator; a customer is a 400 (EXIT 12) whose hint names
68
+ `candidates`. `remove` confirms and needs `--yes` in agent mode (EXIT 16). `--agent` / `--application`
69
+ resolve the Application as `desks` does. **`FruxonClient.list_application_operators`**,
70
+ **`get_application_operator`**, **`list_application_operator_candidates`**,
71
+ **`add_application_operator`**, **`remove_application_operator`**.
72
+ - **`desks create` / `set-policy`** refused with "Operators […] are not active operators of network …"
73
+ now hint the exact `fruxon escalations operators add <ids> --application <id>` command.
74
+
75
+ ## Unreleased — replace an uploaded file asset's contents
76
+
77
+ - **`fruxon assets replace-file <asset> --file <path>`** gives an uploaded-file asset new contents
78
+ under the same id, so agents, step scopes and prompts that use it read the new file. `--wait`
79
+ blocks on the re-index (`--timeout`, default 300 s); search answers from the previous file until it
80
+ finishes and keeps it if the new file can't be indexed. Confirms, and refuses without `--yes` in
81
+ agent mode (EXIT 16): the previous file is no longer offered for download. `-o json` returns the
82
+ server's `{asset, longOperation}` plus `reindexing` and `waited`; `-o id` prints the asset id. A 409
83
+ (indexing running) names `fruxon assets wait`; a 400 names `fruxon assets supported-types`.
84
+ **`FruxonClient.replace_asset_file(asset, path)`** (`POST /assets/{asset}:replaceFile`). Needs the
85
+ backend's endpoint (fruxon-backend #1846).
86
+
3
87
  ## Unreleased — escalation desks, reply-style schema, deploy output
4
88
 
5
89
  - **`fruxon escalations desks list|create|attach|detach`**: an Application with no escalation desk
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: fruxon
3
- Version: 2.2.9
3
+ Version: 2.3.0
4
4
  Summary: The Fruxon SDK is a lightweight Python client for integrating with the Fruxon platform.
5
5
  Project-URL: homepage, https://fruxon.com
6
6
  Project-URL: documentation, https://docs.fruxon.com/guides/cli
@@ -101,8 +101,9 @@ Execution:
101
101
  | `fruxon agents approvals list/get/respond/cancel <agent>` | Operate human-in-the-loop approval gates — see what a run is blocked on and answer it. `respond`/`cancel` confirm first and refuse without `--yes` in agent mode (an LLM must not silently auto-approve). |
102
102
  | `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--query`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
103
103
  | `fruxon agents topics list/search/get/messages/sessions <agent>` + `fruxon agents inbox <agent>` | Read the conversation spine — the agent's topics (threads), one topic's transcript, its episodes, and its inbox (what it's focused on). `list`/`search` filter server-side by `--state`/`--participant`/`--query`. Read-only. Each message carries `author` — a human colleague's turn is stored as `ASSISTANT` on purpose, so `role` alone cannot tell their reply from the agent's; `HUMAN_OPERATOR` can. A message the runtime *withheld* is in no transcript at all — see `fruxon messages list`. `sessions` explains a fresh, blind session: a topic outlives its sessions, and `endCause` on the previous one (`CONSOLE_ALREADY_RESOLVED` — a human closed it in the provider's console) is why the next started with no history. |
104
- | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human — and names the desk it went through. `set-policy <agent>` changes that desk: `--operator` (repeatable, one tier; `--strategy`), `--working-hours <schedule|none>`, `--default-reason`, `--entry-point` for a channel's desk. It reads the desk and PUTs it back with only those changed, for every agent on the desk (`participants:write`). |
104
+ | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it; `list --include-rehearsals` also shows sandbox rehearsals, which page nobody (newer servers; it warns when the server ignored the flag). **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human — and names the desk it went through. `set-policy <agent>` changes that desk: `--operator` (repeatable, one tier; `--strategy`), `--working-hours <schedule|none>`, `--default-reason`, `--entry-point` for a channel's desk. It reads the desk and PUTs it back with only those changed, for every agent on the desk (`participants:write`). |
105
105
  | `fruxon escalations desks list/create/attach/detach` | An Application's escalation desks. `create --name … [--mode BRIDGE\|NATIVE_HANDOFF] [--operator …] [--working-hours …] [--attach other\|<entry-point>]` makes one and attaches it; `attach <desk> other <entry-point>…` / `detach other <entry-point>…` move hand-off between desks. `other` is conversations through no channel (operator desks only). `--agent` picks the agent's Application, `--application` names one. |
106
+ | `fruxon escalations operators list/candidates/add/remove` | An Application's human operators — the only people a desk's `--operator` ladder accepts. `candidates [--search …]` shows who can be added (`ELIGIBLE`, `PROMOTABLE` = marked internal on add, `INELIGIBLE`); `add <participant>…`; `remove <participant>… --yes`. Same `--agent` / `--application` as `desks`. |
106
107
  | `fruxon working-hours list/get/create/update/delete` | Working-hours schedules: a time zone, a week (`--hours "sun-thu 08:00-20:00"`, repeatable; a day not named is closed), dated closures (`--closed 2026-12-25`), or `--file` with the full body. A schedule governs the escalation hand-off once a desk uses it (`escalations set-policy --working-hours`); what the agent says about opening hours stays in its prompt. `participants:read` / `participants:write`. |
107
108
  | `fruxon messages list` | The channel ledger — including inbound an agent was never shown. A **withheld** message (a human owns the chat in the source console, or admission refused the sender) never becomes a conversation turn, so it is in no transcript and the thread reads as a customer being ignored. `--delivery WITHHELD_PENDING` lists the ones nothing has ever acted on; nothing drains them. |
108
109
  | `fruxon agents sandbox open/turn/fire/resolve-input/stream/answer/close <session>` | Drive an agent-network sandbox end-to-end without real channels — send turns as participants, test-fire triggers, and watch the run (`--wait` on `turn` / `fire` follows it to the end; `stream` shows only what happens after it connects; NDJSON in agent mode). Sandbox **captures the reply and hard-blocks every real send**; `--await` makes consult/approval gates suspend so they can be resolved (`answer` for consults, `approvals respond` for approvals). `--draft` runs your unpublished draft instead of the deployed revision (`sandbox draft <session>` says which); `--confirm-writes` holds every create/update/delete tool call for approval, because sandbox does **not** block integration writes; a write that did not run (rejected, expired, or one the run could not pause for) shows on `stream` as `refused`. |
@@ -129,7 +130,7 @@ Agent authoring + management:
129
130
  | `fruxon agents revisions create/get/deploy` | Mint and deploy immutable revisions. `create --deploy` does both in one step, and skips the deploy when the new revision is already live (an agent's first revision goes live on create). Deploying needs `revisions:deploy` (`fruxon login --preset maintainer`); a 403 says so. `get --as-draft` converts a stored revision back into a postable body. |
130
131
  | `fruxon agents revisions list/deploys <id>` | `list` shows revisions newest first (20 unless `--all` or `-n`): number, ★ on the live one, who created it and its comment. After a rollback the ★ is not the top row. `-o json` adds `lastDeployedAt`. Bodies are not listed; `get <id> <n>` fetches one. `deploys` is the deploy history: each attempt, failed ones too, `from → to` with ↩ on a rollback, who made it and why. A backend without the list endpoint gets a warning and the same list built from the older history endpoint. |
131
132
  | `fruxon agents slots list/bind/unbind <id>` | An agent's contacts — the humans `notify` / `ask` / `escalate` reach. The definition declares them; the binding says who receives (`--participant`, `--role`, or `--queue`). Declared but unbound means the reach-out dead-ends at run time, so `list` calls that out and `unbind` is `--yes`-gated. `bind --role` warns first when nobody holds the role — advisory, since binding ahead of staffing is legitimate. |
132
- | `fruxon agents check <id>` | Audit whether a **deployed** agent is wired to run end-to-end, beyond the definition: a deployed revision, an inbound path (bound trigger / channel binding / active entry point), a consult roster if the agent enables consult, declared **and bound** contacts, every bound trigger populating the agent's required params, and that the revision's references resolve. `{overall, checks[]}` (doctor-style); exits non-zero only on a hard fail (no deployed revision) — advisory `warn` rows stay exit 0. |
133
+ | `fruxon agents check <id>` | Audit whether a **deployed** agent is wired to run end-to-end, beyond the definition: a deployed revision, an inbound path (bound trigger / channel binding / active entry point — and, where the provider can be asked, a webhook registered to this config: none is a `fail`), whether a messaging channel queues every new sender (`Unknown senders`, `warn` on `REQUEST_ACCESS`), a consult roster if the agent enables consult, declared **and bound** contacts, every bound trigger populating the agent's required params, and that the revision's references resolve. `{overall, checks[]}` (doctor-style); exits non-zero only on a hard fail (no deployed revision) — advisory `warn` rows stay exit 0. |
133
134
  | `fruxon agents draft pull/push/status/undo/redo/reset/discard` | Local working-copy authoring loop — same draft an open studio tab edits. |
134
135
  | `fruxon agents draft evaluate <id> --dataset <uuid>` | Score the draft against a golden dataset (expensive — every sample is a full agent run). |
135
136
  | `fruxon agents tests list/show/watch/cost/delete` | Browse + tail the test-chat sessions you've run on an agent (owner-scoped). |
@@ -146,6 +147,7 @@ Integrations + tools:
146
147
  | `fruxon integrations list/get/create/update/verify/open` | Manage external integrations — the connections agents draw tools from. `create`/`update`/`verify` take a `--file` JSON body; `open` opens the dashboard. |
147
148
  | `fruxon integrations configs list/get/update/publish` | The per-integration auth/config records. `update --file` patches a config's draft (only the fields sent; `{"egressCountry": ""}` clears an egress pin) and prints it with secrets masked; `publish` makes the draft the revision tool calls resolve, asks first (`--yes` in agent mode), and prints the new revision's `id` and `version`, never the credentials. |
148
149
  | `fruxon integrations authorize <integration>` | `connect` for an OAuth integration (Gmail, Google Sheets, Outlook…): creates a config for its OAuth2 method (auto-detected; `--auth-method` to pick, `--scope` for what to ask, `--config-param` for connection settings, `--config <id>` for an existing config) and prints a credential link. A human opens it, signs in to Fruxon and then to the provider, and the account is connected and the config published, ready for a slot to pin. |
150
+ | `fruxon integrations configs webhook generate/rotate/apply/inspect/remove <integration> <config>` | The provider webhook a messaging connection receives on (Telegram today) — without one the bot gets nothing. `generate` mints the config's URL and registers it with the provider; `rotate --yes` replaces it; `apply --url -` registers one you hold; `inspect` asks the provider what it has (`registeredToThisConfig`, `lastErrorMessage`); `remove --yes` stops delivery. The URL carries the secret and is printed only with `--show-url` — or when it could not be registered, since it is never returned again. Exits 12 when the provider refuses. |
149
151
  | `fruxon integrations configs create <integration> --simulated` | A config with `sandboxMode: SIMULATED` and no credentials, published in one step: every tool call a sandbox run makes through it is answered from its simulated store. `--file` creates an unpublished draft from a full body instead. |
150
152
  | `fruxon integrations configs sandbox status/entities/generate/import/reset/snapshot/restore <integration> <config>` | Read and seed a simulated config's store. `generate --type event --prompt … --count N` has a model write entities (the server snapshots first); `import --file` inserts them as written (`payload` may be an object); `snapshot --name` saves a state (no `--name` lists them), `restore` / `reset` are `--yes`-gated. |
151
153
  | `fruxon integrations connect <integration>` | Create a config for an integration and print a **credential link**: a human opens it and signs in to Fruxon, then types the API key, token or password (Stripe, most REST APIs), and the page tests it and publishes the config; or, for an OAuth integration, signs in to the provider (`--scope` picks what they grant) and the account is connected and the config published. The secret never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a connection setting, `--no-sign-in` mints a link anyone holding it can fill (for a client without a Fruxon login), `--expires-in-hours` 1–720. Needs `integrations:write` (the default login preset); `--no-sign-in` also needs `workspace:write` (Admin or Owner). |
@@ -157,7 +159,7 @@ Integrations + tools:
157
159
  | `fruxon llm-providers connect <provider>` / `link-status` | Create a config for an LLM provider and print a **credential link**: a human opens it, signs in to Fruxon, types the API key (or access keys, or service account key), and the page tests it with the provider and publishes the config an agent pins as `provider.tenantConfigId`. The key never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a non-secret setting such as Bedrock's `region`, `--no-sign-in` mints a link anyone holding it can fill (Admin or Owner). `link-status <provider> <config> <request> [--wait]` says when it was filled. |
158
160
  | `fruxon llm-providers configs list/get/test/publish` | The workspace's saved LLM credentials — the `provider.tenantConfigId` an agent pins. `get` shows the draft (secrets masked), the published revision and last known health. `test` probes the draft on every provider surface that shares the credential (or just one, given that surface's provider id), one line per failing surface, exit 12 on failure (`llm_providers:test`). `publish` ships the draft as a new revision that every agent on the config switches to — it confirms, needs `--yes` in agent mode, and does not wait on a passing test (`llm_providers:write`). |
159
161
  | `fruxon llm-providers configs complete <provider> <config> --model M` | One completion on a saved config's published revision, with no agent, session or execution — to see whether a model follows a prompt or a system block's instruction. `--system` (text, `@file`, `-`; repeatable), `-m [user:\|assistant:]TEXT` (repeatable) or `--messages chat.json`, `--temperature`, `--max-tokens` (server cap 8192), `--param k=v`. The reply goes to stdout, the model, finish reason, tokens and latency to stderr (`llm_providers:test`). Fruxon-hosted providers are refused. |
160
- | `fruxon assets create/list/get/wait/operations/delete` | Manage knowledge-base (RAG) assets an agent can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `delete` confirms + refuses without `--yes` in agent mode. |
162
+ | `fruxon assets create/list/get/wait/operations/replace-file/delete` | Manage knowledge-base (RAG) assets an agent can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `replace-file <asset> --file …` gives an uploaded-file asset new contents under the same id (`--wait` blocks on the re-index; search keeps the previous file until it finishes). `replace-file` and `delete` confirm + refuse without `--yes` in agent mode. |
161
163
  | `fruxon knowledge-bases list/get/create/update/publish/archive/delete` | The authored, reviewable corpus behind a `manual_knowledge` asset — **not** the asset itself, which is what gets searched (`get` prints the asset id as `backingAssetId`). **`publish` is the step that makes any of it findable**: only `PUBLISHED` documents travel in a snapshot, and only publishing the *base* moves one, so a base full of finished articles answers nothing until it runs. It returns on *acceptance*, not searchability — RAG ingests afterwards, so a pending publish state is normal. `list` hides archived bases, which keep answering for agents already attached to them; `delete` is refused while an agent revision still attaches one, and `archive` is the reversible path. |
162
164
  | `fruxon knowledge-bases usage <kb>` | Whether agents actually use the base: searches per hour, day or week (`--interval`), the passage tokens each search handed the agent, how many found nothing (split from searches that **could not fully search** it — index missing or still building, a phrasing failed), and which agents searched (up to 20 you can open, the rest counted together). `--origin test` counts test runs instead of production. Retrieved tokens are counted by the search index, so what the model read can be less when a large result is trimmed or offloaded. Searches are recorded from 15 October 2026 and kept 90 days at most, so a window reaching further back says where counting began rather than showing empty days. A 404 is a wrong id or a backend that predates the read. |
163
165
  | `fruxon knowledge-bases notices/notice/post-notice/edit-notice/extend-notice/withdraw-notice` | Time-boxed notices on a base — an outage being fixed, a known bug, a closure. **Not documents**: never indexed or published, so every agent attaching the base is given each active notice whole from its next turn. `post-notice --valid-for 4h` (or `--until`) — every notice ends, at most 30 days after it was posted, and a base holds ten active ones (409 `notice_limit` / `notice_too_long`, each with its remedy). The body is Markdown, at most 1,200 characters, best as four headings: *What is happening*, *Applies when*, *Tell the customer*, *Do not*. A time without an offset is read in the notice's zone (`--time-zone`, else this machine's), which is also the zone agents tell customers the end in. `withdraw-notice` tells each conversation that was given it, on its next turn, that it ended; it confirms, and needs `--yes` in agent mode. An ended notice is not extended: `post-notice --from <id>` posts it again as a new one. |
@@ -193,9 +195,10 @@ Integrations + tools:
193
195
  | `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--query` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
194
196
  | `fruxon applications roles <id>` | The Application's roster roles — who holds each, who defers to it, and how many holders are `consultable`. The answer to what a `--role` contact binding leaves open: the server takes any role string, so a role with references and no holders refuses at delivery time. `--unheld-only` lists just those. Trust the consultable count — every role path, delivery and consult alike, resolves through the consult-allowed member edges, so a holder without one is tagged but unreachable. |
195
197
  | `fruxon applications list/get` | Inspect Applications — the container that owns agents, workflows and people. Every agent belongs to exactly one, and `agents create` needs its id, so this is where you find it. Creating and re-homing an Application itself stays in the dashboard. |
196
- | `fruxon applications entry-points list/get/connect/attach/disconnect/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?". `connect` mints a new doorway (and prints the webhook URL **once**); `attach` adopts an existing one; `move` re-homes a claimed address; `disconnect` deletes the doorway and frees the address. Writes — `disconnect`/`move` confirm first. |
198
+ | `fruxon applications entry-points list/get/connect/attach/disconnect/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?"; `get <entry-point>` alone finds a claimed one without its Application. `connect` mints a new doorway (and prints a per-channel webhook URL **once**); for a provider whose webhook belongs to the connection (Telegram) it reports `webhook.status` — `INSTALLED`, `ALREADY_INSTALLED`, `UNVERIFIED`, `MANUAL_INSTALL_REQUIRED` or `FAILED` (retried once) — and shows that URL only with `--show-url` or while it still needs registering. `attach` adopts an existing one; `move` re-homes a claimed address; `disconnect` deletes the doorway and frees the address; `update --unknown-senders REQUEST_ACCESS\|REJECT\|PROVISION\|OPEN` (or `--inherit-unknown-senders`) sets how this channel treats strangers. Writes — `disconnect`/`move` confirm first. |
199
+ | `fruxon applications update <app> [--unknown-senders …] [--name …]` | The Application-wide unknown-sender policy its channels inherit. The value is passed through for the server to validate. |
200
+ | `fruxon access-requests list/get/approve/reject` | Senders a channel on `REQUEST_ACCESS` is holding — they get no answer until approved. `list` (`--status PENDING` by default, `--agent`, `--application`); `approve <id>` creates a person, binds the matched one, or with `--participant` adds the channel to an existing person (`--mode` to pick); `reject <id> [--note]` — they can ask again. |
197
201
  | `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --query` filters; `archive` confirms + refuses without `--yes` in agent mode. |
198
- | `fruxon pipelines list/get` | Read collection pipelines — one Agent or Workflow run per item of a source. An agent's `pipelines.bindings` allowlist names them **by id** and `run_pipeline` refuses any id it does not name, so this is where those ids come from (`get` also lists the reusable `sourceId`s `allowedSourceIds` takes). Read-only. |
199
202
  | `fruxon capabilities list/get/create/update/delete` | Manage the consult-routing vocabulary (capabilities = name/area/description) that roster bindings and pins reference. `create`/`update` take `--file` (+`--schema`); `delete` --yes-gated in agent mode. |
200
203
  | `fruxon participants bind/unbind/roster` + `fruxon agents roster` | Wire a participant onto an agent's consult roster and set its policy (roles / urgency / response policy); `agents roster` reads who advises an agent. `unbind` --yes-gated. |
201
204
  | `fruxon consult-pins list/get/create/delete` | Deterministic capability→participant routing overrides (skip the network's scoring). `create` takes `--file` (+`--schema`); `delete` --yes-gated. |
@@ -67,8 +67,9 @@ Execution:
67
67
  | `fruxon agents approvals list/get/respond/cancel <agent>` | Operate human-in-the-loop approval gates — see what a run is blocked on and answer it. `respond`/`cancel` confirm first and refuse without `--yes` in agent mode (an LLM must not silently auto-approve). |
68
68
  | `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--query`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
69
69
  | `fruxon agents topics list/search/get/messages/sessions <agent>` + `fruxon agents inbox <agent>` | Read the conversation spine — the agent's topics (threads), one topic's transcript, its episodes, and its inbox (what it's focused on). `list`/`search` filter server-side by `--state`/`--participant`/`--query`. Read-only. Each message carries `author` — a human colleague's turn is stored as `ASSISTANT` on purpose, so `role` alone cannot tell their reply from the agent's; `HUMAN_OPERATOR` can. A message the runtime *withheld* is in no transcript at all — see `fruxon messages list`. `sessions` explains a fresh, blind session: a topic outlives its sessions, and `endCause` on the previous one (`CONSOLE_ALREADY_RESOLVED` — a human closed it in the provider's console) is why the next started with no history. |
70
- | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human — and names the desk it went through. `set-policy <agent>` changes that desk: `--operator` (repeatable, one tier; `--strategy`), `--working-hours <schedule|none>`, `--default-reason`, `--entry-point` for a channel's desk. It reads the desk and PUTs it back with only those changed, for every agent on the desk (`participants:write`). |
70
+ | `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it; `list --include-rehearsals` also shows sandbox rehearsals, which page nobody (newer servers; it warns when the server ignored the flag). **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human — and names the desk it went through. `set-policy <agent>` changes that desk: `--operator` (repeatable, one tier; `--strategy`), `--working-hours <schedule|none>`, `--default-reason`, `--entry-point` for a channel's desk. It reads the desk and PUTs it back with only those changed, for every agent on the desk (`participants:write`). |
71
71
  | `fruxon escalations desks list/create/attach/detach` | An Application's escalation desks. `create --name … [--mode BRIDGE\|NATIVE_HANDOFF] [--operator …] [--working-hours …] [--attach other\|<entry-point>]` makes one and attaches it; `attach <desk> other <entry-point>…` / `detach other <entry-point>…` move hand-off between desks. `other` is conversations through no channel (operator desks only). `--agent` picks the agent's Application, `--application` names one. |
72
+ | `fruxon escalations operators list/candidates/add/remove` | An Application's human operators — the only people a desk's `--operator` ladder accepts. `candidates [--search …]` shows who can be added (`ELIGIBLE`, `PROMOTABLE` = marked internal on add, `INELIGIBLE`); `add <participant>…`; `remove <participant>… --yes`. Same `--agent` / `--application` as `desks`. |
72
73
  | `fruxon working-hours list/get/create/update/delete` | Working-hours schedules: a time zone, a week (`--hours "sun-thu 08:00-20:00"`, repeatable; a day not named is closed), dated closures (`--closed 2026-12-25`), or `--file` with the full body. A schedule governs the escalation hand-off once a desk uses it (`escalations set-policy --working-hours`); what the agent says about opening hours stays in its prompt. `participants:read` / `participants:write`. |
73
74
  | `fruxon messages list` | The channel ledger — including inbound an agent was never shown. A **withheld** message (a human owns the chat in the source console, or admission refused the sender) never becomes a conversation turn, so it is in no transcript and the thread reads as a customer being ignored. `--delivery WITHHELD_PENDING` lists the ones nothing has ever acted on; nothing drains them. |
74
75
  | `fruxon agents sandbox open/turn/fire/resolve-input/stream/answer/close <session>` | Drive an agent-network sandbox end-to-end without real channels — send turns as participants, test-fire triggers, and watch the run (`--wait` on `turn` / `fire` follows it to the end; `stream` shows only what happens after it connects; NDJSON in agent mode). Sandbox **captures the reply and hard-blocks every real send**; `--await` makes consult/approval gates suspend so they can be resolved (`answer` for consults, `approvals respond` for approvals). `--draft` runs your unpublished draft instead of the deployed revision (`sandbox draft <session>` says which); `--confirm-writes` holds every create/update/delete tool call for approval, because sandbox does **not** block integration writes; a write that did not run (rejected, expired, or one the run could not pause for) shows on `stream` as `refused`. |
@@ -95,7 +96,7 @@ Agent authoring + management:
95
96
  | `fruxon agents revisions create/get/deploy` | Mint and deploy immutable revisions. `create --deploy` does both in one step, and skips the deploy when the new revision is already live (an agent's first revision goes live on create). Deploying needs `revisions:deploy` (`fruxon login --preset maintainer`); a 403 says so. `get --as-draft` converts a stored revision back into a postable body. |
96
97
  | `fruxon agents revisions list/deploys <id>` | `list` shows revisions newest first (20 unless `--all` or `-n`): number, ★ on the live one, who created it and its comment. After a rollback the ★ is not the top row. `-o json` adds `lastDeployedAt`. Bodies are not listed; `get <id> <n>` fetches one. `deploys` is the deploy history: each attempt, failed ones too, `from → to` with ↩ on a rollback, who made it and why. A backend without the list endpoint gets a warning and the same list built from the older history endpoint. |
97
98
  | `fruxon agents slots list/bind/unbind <id>` | An agent's contacts — the humans `notify` / `ask` / `escalate` reach. The definition declares them; the binding says who receives (`--participant`, `--role`, or `--queue`). Declared but unbound means the reach-out dead-ends at run time, so `list` calls that out and `unbind` is `--yes`-gated. `bind --role` warns first when nobody holds the role — advisory, since binding ahead of staffing is legitimate. |
98
- | `fruxon agents check <id>` | Audit whether a **deployed** agent is wired to run end-to-end, beyond the definition: a deployed revision, an inbound path (bound trigger / channel binding / active entry point), a consult roster if the agent enables consult, declared **and bound** contacts, every bound trigger populating the agent's required params, and that the revision's references resolve. `{overall, checks[]}` (doctor-style); exits non-zero only on a hard fail (no deployed revision) — advisory `warn` rows stay exit 0. |
99
+ | `fruxon agents check <id>` | Audit whether a **deployed** agent is wired to run end-to-end, beyond the definition: a deployed revision, an inbound path (bound trigger / channel binding / active entry point — and, where the provider can be asked, a webhook registered to this config: none is a `fail`), whether a messaging channel queues every new sender (`Unknown senders`, `warn` on `REQUEST_ACCESS`), a consult roster if the agent enables consult, declared **and bound** contacts, every bound trigger populating the agent's required params, and that the revision's references resolve. `{overall, checks[]}` (doctor-style); exits non-zero only on a hard fail (no deployed revision) — advisory `warn` rows stay exit 0. |
99
100
  | `fruxon agents draft pull/push/status/undo/redo/reset/discard` | Local working-copy authoring loop — same draft an open studio tab edits. |
100
101
  | `fruxon agents draft evaluate <id> --dataset <uuid>` | Score the draft against a golden dataset (expensive — every sample is a full agent run). |
101
102
  | `fruxon agents tests list/show/watch/cost/delete` | Browse + tail the test-chat sessions you've run on an agent (owner-scoped). |
@@ -112,6 +113,7 @@ Integrations + tools:
112
113
  | `fruxon integrations list/get/create/update/verify/open` | Manage external integrations — the connections agents draw tools from. `create`/`update`/`verify` take a `--file` JSON body; `open` opens the dashboard. |
113
114
  | `fruxon integrations configs list/get/update/publish` | The per-integration auth/config records. `update --file` patches a config's draft (only the fields sent; `{"egressCountry": ""}` clears an egress pin) and prints it with secrets masked; `publish` makes the draft the revision tool calls resolve, asks first (`--yes` in agent mode), and prints the new revision's `id` and `version`, never the credentials. |
114
115
  | `fruxon integrations authorize <integration>` | `connect` for an OAuth integration (Gmail, Google Sheets, Outlook…): creates a config for its OAuth2 method (auto-detected; `--auth-method` to pick, `--scope` for what to ask, `--config-param` for connection settings, `--config <id>` for an existing config) and prints a credential link. A human opens it, signs in to Fruxon and then to the provider, and the account is connected and the config published, ready for a slot to pin. |
116
+ | `fruxon integrations configs webhook generate/rotate/apply/inspect/remove <integration> <config>` | The provider webhook a messaging connection receives on (Telegram today) — without one the bot gets nothing. `generate` mints the config's URL and registers it with the provider; `rotate --yes` replaces it; `apply --url -` registers one you hold; `inspect` asks the provider what it has (`registeredToThisConfig`, `lastErrorMessage`); `remove --yes` stops delivery. The URL carries the secret and is printed only with `--show-url` — or when it could not be registered, since it is never returned again. Exits 12 when the provider refuses. |
115
117
  | `fruxon integrations configs create <integration> --simulated` | A config with `sandboxMode: SIMULATED` and no credentials, published in one step: every tool call a sandbox run makes through it is answered from its simulated store. `--file` creates an unpublished draft from a full body instead. |
116
118
  | `fruxon integrations configs sandbox status/entities/generate/import/reset/snapshot/restore <integration> <config>` | Read and seed a simulated config's store. `generate --type event --prompt … --count N` has a model write entities (the server snapshots first); `import --file` inserts them as written (`payload` may be an object); `snapshot --name` saves a state (no `--name` lists them), `restore` / `reset` are `--yes`-gated. |
117
119
  | `fruxon integrations connect <integration>` | Create a config for an integration and print a **credential link**: a human opens it and signs in to Fruxon, then types the API key, token or password (Stripe, most REST APIs), and the page tests it and publishes the config; or, for an OAuth integration, signs in to the provider (`--scope` picks what they grant) and the account is connected and the config published. The secret never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a connection setting, `--no-sign-in` mints a link anyone holding it can fill (for a client without a Fruxon login), `--expires-in-hours` 1–720. Needs `integrations:write` (the default login preset); `--no-sign-in` also needs `workspace:write` (Admin or Owner). |
@@ -123,7 +125,7 @@ Integrations + tools:
123
125
  | `fruxon llm-providers connect <provider>` / `link-status` | Create a config for an LLM provider and print a **credential link**: a human opens it, signs in to Fruxon, types the API key (or access keys, or service account key), and the page tests it with the provider and publishes the config an agent pins as `provider.tenantConfigId`. The key never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a non-secret setting such as Bedrock's `region`, `--no-sign-in` mints a link anyone holding it can fill (Admin or Owner). `link-status <provider> <config> <request> [--wait]` says when it was filled. |
124
126
  | `fruxon llm-providers configs list/get/test/publish` | The workspace's saved LLM credentials — the `provider.tenantConfigId` an agent pins. `get` shows the draft (secrets masked), the published revision and last known health. `test` probes the draft on every provider surface that shares the credential (or just one, given that surface's provider id), one line per failing surface, exit 12 on failure (`llm_providers:test`). `publish` ships the draft as a new revision that every agent on the config switches to — it confirms, needs `--yes` in agent mode, and does not wait on a passing test (`llm_providers:write`). |
125
127
  | `fruxon llm-providers configs complete <provider> <config> --model M` | One completion on a saved config's published revision, with no agent, session or execution — to see whether a model follows a prompt or a system block's instruction. `--system` (text, `@file`, `-`; repeatable), `-m [user:\|assistant:]TEXT` (repeatable) or `--messages chat.json`, `--temperature`, `--max-tokens` (server cap 8192), `--param k=v`. The reply goes to stdout, the model, finish reason, tokens and latency to stderr (`llm_providers:test`). Fruxon-hosted providers are refused. |
126
- | `fruxon assets create/list/get/wait/operations/delete` | Manage knowledge-base (RAG) assets an agent can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `delete` confirms + refuses without `--yes` in agent mode. |
128
+ | `fruxon assets create/list/get/wait/operations/replace-file/delete` | Manage knowledge-base (RAG) assets an agent can query — upload local files, wait for async ingestion, inspect operations, and use the ids for `assetConfig.assetIds`. `replace-file <asset> --file …` gives an uploaded-file asset new contents under the same id (`--wait` blocks on the re-index; search keeps the previous file until it finishes). `replace-file` and `delete` confirm + refuse without `--yes` in agent mode. |
127
129
  | `fruxon knowledge-bases list/get/create/update/publish/archive/delete` | The authored, reviewable corpus behind a `manual_knowledge` asset — **not** the asset itself, which is what gets searched (`get` prints the asset id as `backingAssetId`). **`publish` is the step that makes any of it findable**: only `PUBLISHED` documents travel in a snapshot, and only publishing the *base* moves one, so a base full of finished articles answers nothing until it runs. It returns on *acceptance*, not searchability — RAG ingests afterwards, so a pending publish state is normal. `list` hides archived bases, which keep answering for agents already attached to them; `delete` is refused while an agent revision still attaches one, and `archive` is the reversible path. |
128
130
  | `fruxon knowledge-bases usage <kb>` | Whether agents actually use the base: searches per hour, day or week (`--interval`), the passage tokens each search handed the agent, how many found nothing (split from searches that **could not fully search** it — index missing or still building, a phrasing failed), and which agents searched (up to 20 you can open, the rest counted together). `--origin test` counts test runs instead of production. Retrieved tokens are counted by the search index, so what the model read can be less when a large result is trimmed or offloaded. Searches are recorded from 15 October 2026 and kept 90 days at most, so a window reaching further back says where counting began rather than showing empty days. A 404 is a wrong id or a backend that predates the read. |
129
131
  | `fruxon knowledge-bases notices/notice/post-notice/edit-notice/extend-notice/withdraw-notice` | Time-boxed notices on a base — an outage being fixed, a known bug, a closure. **Not documents**: never indexed or published, so every agent attaching the base is given each active notice whole from its next turn. `post-notice --valid-for 4h` (or `--until`) — every notice ends, at most 30 days after it was posted, and a base holds ten active ones (409 `notice_limit` / `notice_too_long`, each with its remedy). The body is Markdown, at most 1,200 characters, best as four headings: *What is happening*, *Applies when*, *Tell the customer*, *Do not*. A time without an offset is read in the notice's zone (`--time-zone`, else this machine's), which is also the zone agents tell customers the end in. `withdraw-notice` tells each conversation that was given it, on its next turn, that it ended; it confirms, and needs `--yes` in agent mode. An ended notice is not extended: `post-notice --from <id>` posts it again as a new one. |
@@ -159,9 +161,10 @@ Integrations + tools:
159
161
  | `fruxon participants list/get/create/update/delete/enable/disable` | Manage agent-network participants (people / groups / agents the network routes to). `list` takes `--query` (matches names **and channel addresses and account ids**, so a phone number or handle resolves to an id, and searches both directory tiers by default), `--kind`, `--tier`, `--agent`, `--environment-id`, and pages up to `--limit` / `--all`. `create`/`update` take `--file` (+`--schema`); `enable`/`disable` toggle routing; `delete` confirms + refuses without `--yes` in agent mode. |
160
162
  | `fruxon applications roles <id>` | The Application's roster roles — who holds each, who defers to it, and how many holders are `consultable`. The answer to what a `--role` contact binding leaves open: the server takes any role string, so a role with references and no holders refuses at delivery time. `--unheld-only` lists just those. Trust the consultable count — every role path, delivery and consult alike, resolves through the consult-allowed member edges, so a holder without one is tagged but unreachable. |
161
163
  | `fruxon applications list/get` | Inspect Applications — the container that owns agents, workflows and people. Every agent belongs to exactly one, and `agents create` needs its id, so this is where you find it. Creating and re-homing an Application itself stays in the dashboard. |
162
- | `fruxon applications entry-points list/get/connect/attach/disconnect/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?". `connect` mints a new doorway (and prints the webhook URL **once**); `attach` adopts an existing one; `move` re-homes a claimed address; `disconnect` deletes the doorway and frees the address. Writes — `disconnect`/`move` confirm first. |
164
+ | `fruxon applications entry-points list/get/connect/attach/disconnect/move/update` | How inbound actually reaches an agent: an Application's claim on an external address. `list` with no Application answers "is this address already taken?"; `get <entry-point>` alone finds a claimed one without its Application. `connect` mints a new doorway (and prints a per-channel webhook URL **once**); for a provider whose webhook belongs to the connection (Telegram) it reports `webhook.status` — `INSTALLED`, `ALREADY_INSTALLED`, `UNVERIFIED`, `MANUAL_INSTALL_REQUIRED` or `FAILED` (retried once) — and shows that URL only with `--show-url` or while it still needs registering. `attach` adopts an existing one; `move` re-homes a claimed address; `disconnect` deletes the doorway and frees the address; `update --unknown-senders REQUEST_ACCESS\|REJECT\|PROVISION\|OPEN` (or `--inherit-unknown-senders`) sets how this channel treats strangers. Writes — `disconnect`/`move` confirm first. |
165
+ | `fruxon applications update <app> [--unknown-senders …] [--name …]` | The Application-wide unknown-sender policy its channels inherit. The value is passed through for the server to validate. |
166
+ | `fruxon access-requests list/get/approve/reject` | Senders a channel on `REQUEST_ACCESS` is holding — they get no answer until approved. `list` (`--status PENDING` by default, `--agent`, `--application`); `approve <id>` creates a person, binds the matched one, or with `--participant` adds the channel to an existing person (`--mode` to pick); `reject <id> [--note]` — they can ask again. |
163
167
  | `fruxon environments list/get/create/update/archive` | Manage end-customer environments — the slugs connector bindings and `execute(environmentSlug=…)` attribute runs to (per-customer cost tracking, quotas, analytics). `list --query` filters; `archive` confirms + refuses without `--yes` in agent mode. |
164
- | `fruxon pipelines list/get` | Read collection pipelines — one Agent or Workflow run per item of a source. An agent's `pipelines.bindings` allowlist names them **by id** and `run_pipeline` refuses any id it does not name, so this is where those ids come from (`get` also lists the reusable `sourceId`s `allowedSourceIds` takes). Read-only. |
165
168
  | `fruxon capabilities list/get/create/update/delete` | Manage the consult-routing vocabulary (capabilities = name/area/description) that roster bindings and pins reference. `create`/`update` take `--file` (+`--schema`); `delete` --yes-gated in agent mode. |
166
169
  | `fruxon participants bind/unbind/roster` + `fruxon agents roster` | Wire a participant onto an agent's consult roster and set its policy (roles / urgency / response policy); `agents roster` reads who advises an agent. `unbind` --yes-gated. |
167
170
  | `fruxon consult-pins list/get/create/delete` | Deterministic capability→participant routing overrides (skip the network's scoring). `create` takes `--file` (+`--schema`); `delete` --yes-gated. |
@@ -28,7 +28,6 @@ from fruxon.models import (
28
28
  Capability,
29
29
  ChannelBinding,
30
30
  ChannelMessage,
31
- CollectionPipeline,
32
31
  ConnectedChannel,
33
32
  ConsoleHandoff,
34
33
  ConsultPin,
@@ -117,7 +116,6 @@ from fruxon.models import (
117
116
  Memory,
118
117
  MessagingEndpoint,
119
118
  Participant,
120
- PipelineSourceRef,
121
119
  RecentSupportHandoff,
122
120
  ScheduleTime,
123
121
  Secret,
@@ -163,7 +161,6 @@ __all__ = [
163
161
  "Capability",
164
162
  "ChannelBinding",
165
163
  "ChannelMessage",
166
- "CollectionPipeline",
167
164
  "ConflictError",
168
165
  "ConnectedChannel",
169
166
  "ConsultPin",
@@ -259,7 +256,6 @@ __all__ = [
259
256
  "MessagingEndpoint",
260
257
  "NotFoundError",
261
258
  "Participant",
262
- "PipelineSourceRef",
263
259
  "RecentSupportHandoff",
264
260
  "ScheduleTime",
265
261
  "Secret",
@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
18
18
  commit_id: str | None
19
19
  __commit_id__: str | None
20
20
 
21
- __version__ = version = '2.2.9'
22
- __version_tuple__ = version_tuple = (2, 2, 9)
21
+ __version__ = version = '2.3.0'
22
+ __version_tuple__ = version_tuple = (2, 3, 0)
23
23
 
24
24
  __commit_id__ = commit_id = None
@@ -36,7 +36,13 @@ EXPLAIN: dict[str, str] = {
36
36
  "Revision body": "The rows about consults and approvals read the revision's body.",
37
37
  "Inbound path": (
38
38
  "Something has to start a run: a trigger bound to the agent, a channel binding, or an active "
39
- "entry point on its Application. With none, the agent only runs from a test or the SDK."
39
+ "entry point on its Application. With none, the agent only runs from a test or the SDK. A messaging "
40
+ "channel also needs the provider to know where to deliver: where the provider can be asked (Telegram), "
41
+ "a channel with no webhook registered fails this row."
42
+ ),
43
+ "Unknown senders": (
44
+ "What a channel does when someone it does not know writes. On REQUEST_ACCESS (the default) the message "
45
+ "is held and the sender gets no answer until someone approves them with fruxon access-requests."
40
46
  ),
41
47
  "Consult roster": (
42
48
  "An agent that consults other agents needs someone on its roster, or every consult dead-ends at run time."
@@ -90,6 +96,7 @@ FIX: dict[str, str] = {
90
96
  "Deployed revision": "editor",
91
97
  "Revision body": "editor",
92
98
  "Inbound path": "channels",
99
+ "Unknown senders": "channels",
93
100
  "Consult roster": "editor",
94
101
  "Approver slots": "editor",
95
102
  "Contacts": "editor",
@@ -104,6 +111,94 @@ FIX: dict[str, str] = {
104
111
  }
105
112
 
106
113
 
114
+ def _unwired_webhooks(client, entry_points: list) -> dict:
115
+ """Ask each messaging channel's provider whether it has a webhook to deliver to.
116
+
117
+ Only providers with a webhook inspector answer (Telegram today); the rest
118
+ reply 400 and are skipped. Returns ``{"missing": [entry point, …],
119
+ "erroring": [(entry point, last error), …]}``. Best-effort: a read that
120
+ fails says nothing, never a false ``fail``.
121
+ """
122
+ from fruxon.exceptions import ValidationError
123
+
124
+ missing: list = []
125
+ erroring: list = []
126
+ seen: set[tuple[str, str]] = set()
127
+ for e in entry_points:
128
+ provider = (e.provider or "").lower()
129
+ config = e.integration_config_id
130
+ if (e.kind or "").upper() != "MESSAGING" or not provider or not config or (provider, config) in seen:
131
+ continue
132
+ seen.add((provider, config))
133
+ try:
134
+ info = client.inspect_config_webhook(provider, config)
135
+ except ValidationError:
136
+ continue # no inspector for this provider — nothing to read
137
+ except FruxonError:
138
+ continue
139
+ if not isinstance(info, dict):
140
+ continue
141
+ # registeredToThisConfig is false for no URL, another URL, or a stale key
142
+ # of this config, and null only when the probe failed; older servers
143
+ # send just providerHasUrl.
144
+ if info.get("inspectFailed"):
145
+ continue
146
+ registered = (
147
+ info.get("registeredToThisConfig") if "registeredToThisConfig" in info else info.get("providerHasUrl")
148
+ )
149
+ if registered is None:
150
+ continue
151
+ if not registered:
152
+ missing.append(e)
153
+ elif info.get("lastErrorMessage"):
154
+ erroring.append((e, str(info["lastErrorMessage"])))
155
+ return {"missing": missing, "erroring": erroring}
156
+
157
+
158
+ def _check_unknown_senders(client, agent: str, fetched, entry_points: list | None, add) -> None:
159
+ messaging = [e for e in entry_points or [] if (e.kind or "").upper() == "MESSAGING"]
160
+ if not messaging:
161
+ add("Unknown senders", "skip", "no messaging channel")
162
+ return
163
+ app_policy = ""
164
+ if any(not e.unknown_sender_admission for e in messaging) and fetched.network_id:
165
+ try:
166
+ app_policy = client.get_application(fetched.network_id).unknown_sender_admission
167
+ except FruxonError:
168
+ app_policy = ""
169
+ gated, unknown = [], []
170
+ for e in messaging:
171
+ policy = (e.unknown_sender_admission or app_policy or "").upper()
172
+ if not policy:
173
+ unknown.append(e)
174
+ elif policy == "REQUEST_ACCESS":
175
+ gated.append(e)
176
+ if gated:
177
+ waiting = ""
178
+ try:
179
+ pending = client.list_access_requests(agent=agent, status="PENDING")
180
+ if pending:
181
+ waiting = f"; {len(pending)} waiting now"
182
+ except FruxonError:
183
+ pass
184
+ add(
185
+ "Unknown senders",
186
+ "warn",
187
+ f"{len(gated)} channel(s) on REQUEST_ACCESS — every new sender waits for approval and gets no "
188
+ f"answer until then{waiting}",
189
+ hint=(
190
+ "fruxon access-requests list --agent "
191
+ f"{agent} (or stop the queue: fruxon applications update {fetched.network_id} "
192
+ "--unknown-senders PROVISION)"
193
+ ),
194
+ )
195
+ elif unknown:
196
+ add("Unknown senders", "warn", "couldn't read the Application's unknown-sender policy")
197
+ else:
198
+ policies = sorted({(e.unknown_sender_admission or app_policy).upper() for e in messaging})
199
+ add("Unknown senders", "ok", f"new senders are handled by {', '.join(policies)}")
200
+
201
+
107
202
  def check_agent(client, agent: str, *, revision: int | None = None, fetched=None) -> CheckReport:
108
203
  """Audit whether ``agent`` is wired to run end-to-end.
109
204
 
@@ -181,7 +276,20 @@ def check_agent(client, agent: str, *, revision: int | None = None, fetched=None
181
276
  except FruxonError:
182
277
  entry_points = None
183
278
 
184
- if triggers or channels or entry_points:
279
+ unwired = _unwired_webhooks(client, entry_points or [])
280
+
281
+ if unwired["missing"]:
282
+ first = unwired["missing"][0]
283
+ provider, config = (first.provider or "").lower(), first.integration_config_id
284
+ add(
285
+ "Inbound path",
286
+ "fail",
287
+ f"{len(unwired['missing'])} channel(s) are not registered with the provider "
288
+ f"({', '.join(sorted({(e.provider or '').lower() for e in unwired['missing']}))}): no webhook, or one "
289
+ "pointing elsewhere — inbound messages never arrive",
290
+ hint=f"fruxon integrations configs webhook rotate {provider} {config} --yes",
291
+ )
292
+ elif triggers or channels or entry_points:
185
293
  bits = []
186
294
  if triggers:
187
295
  bits.append(f"{len(triggers)} trigger{'s' if len(triggers) != 1 else ''}")
@@ -189,7 +297,17 @@ def check_agent(client, agent: str, *, revision: int | None = None, fetched=None
189
297
  bits.append(f"{len(channels)} channel binding{'s' if len(channels) != 1 else ''}")
190
298
  if entry_points:
191
299
  bits.append(f"{len(entry_points)} active entry point{'s' if len(entry_points) != 1 else ''}")
192
- add("Inbound path", "ok", " + ".join(bits))
300
+ if unwired["erroring"]:
301
+ e, message = unwired["erroring"][0]
302
+ add(
303
+ "Inbound path",
304
+ "warn",
305
+ " + ".join(bits) + f" — but {(e.provider or '').lower()} reports delivery errors: {message}",
306
+ hint=f"fruxon integrations configs webhook inspect {(e.provider or '').lower()} "
307
+ f"{e.integration_config_id}",
308
+ )
309
+ else:
310
+ add("Inbound path", "ok", " + ".join(bits))
193
311
  elif triggers is None and channels is None:
194
312
  add("Inbound path", "warn", "couldn't fetch triggers or channels — inbound wiring unknown")
195
313
  elif entry_points is None:
@@ -213,6 +331,11 @@ def check_agent(client, agent: str, *, revision: int | None = None, fetched=None
213
331
  ),
214
332
  )
215
333
 
334
+ # 2a. Unknown senders — a messaging channel left on REQUEST_ACCESS (the
335
+ # platform default) answers nobody new until someone approves them, which
336
+ # looks exactly like a dead bot from the outside.
337
+ _check_unknown_senders(client, agent, fetched, entry_points, add)
338
+
216
339
  # 3. Consult roster — only relevant if the agent consults (network.enabled).
217
340
  if not caps["consult_steps"]:
218
341
  add("Consult roster", "skip", "consult is off (network.enabled)")
@@ -596,12 +719,23 @@ def _desk_problem(policy, where: str) -> str | None:
596
719
  return f"{where}: no escalation desk — hand-off isn't available there"
597
720
  if (policy.mode or "").upper() == "NATIVE_HANDOFF":
598
721
  return None # the channel's own console supplies the person
722
+ name = f"desk '{policy.desk_name}'" if policy.desk_name else "its desk"
599
723
  if not policy.configured_operators:
600
- name = f"desk '{policy.desk_name}'" if policy.desk_name else "its desk"
601
724
  return f"{where}: {name} has no operators on its ladder"
725
+ if not _reachable_operators(policy):
726
+ reasons = sorted({str(u.get("liveReachability") or "unreachable") for u in policy.unreachable_operators})
727
+ return f"{where}: none of {name}'s operators can be reached ({', '.join(reasons)})"
602
728
  return None
603
729
 
604
730
 
731
+ def _reachable_operators(policy) -> list:
732
+ """The ladder minus the operators the server says a page cannot reach."""
733
+ unreachable = {
734
+ str(u.get("participantId")) for u in getattr(policy, "unreachable_operators", None) or [] if isinstance(u, dict)
735
+ }
736
+ return [o for o in policy.configured_operators if o.participant_id not in unreachable]
737
+
738
+
605
739
  def escalation_reach(client, agent: str) -> tuple[str, str, str | None]:
606
740
  """``(status, detail, hint)`` for whether ``agent``'s escalations reach a person.
607
741
 
@@ -669,13 +803,21 @@ def escalation_reach(client, agent: str) -> tuple[str, str, str | None]:
669
803
  + ". The agent still tells the customer it handed off.",
670
804
  hint,
671
805
  )
672
- reached = sorted({len(p.configured_operators) for _, p in surfaces})
806
+ reached = sorted({len(_reachable_operators(p)) for _, p in surfaces})
673
807
  consoles = sum(1 for _, p in surfaces if (p.mode or "").upper() == "NATIVE_HANDOFF")
674
808
  bits = []
675
809
  if consoles:
676
810
  bits.append(f"{consoles} desk(s) hand off to the channel's console")
677
811
  if any(reached):
678
- bits.append(f"operator ladder(s) of {', '.join(str(n) for n in reached if n)} operator(s)")
812
+ bits.append(f"operator ladder(s) of {', '.join(str(n) for n in reached if n)} reachable operator(s)")
813
+ skipped = {str(u.get("participantId")) for _, p in surfaces for u in p.unreachable_operators}
814
+ if skipped:
815
+ # Reaches a person, but not everyone listed: say who a page skips.
816
+ return (
817
+ "warn",
818
+ "hand-offs reach a person: " + "; ".join(bits) + f" — {len(skipped)} listed operator(s) can't be reached",
819
+ f"fruxon escalations policy {agent} (lists who can't be reached, and why)",
820
+ )
679
821
  return "ok", "hand-offs reach a person: " + "; ".join(bits), None
680
822
 
681
823
 
@@ -755,6 +755,7 @@ def _print_agent_manifest(*, creds: credentials.StoredCredentials, signed_in: bo
755
755
  # above. The order doesn't matter for correctness — only for the order they
756
756
  # show up in ``fruxon --help``.
757
757
 
758
+ from fruxon.cli import access_requests as _access_requests # noqa: E402, F401
758
759
  from fruxon.cli import agents as _agents # noqa: E402, F401
759
760
 
760
761
  # The ``agents`` group used to live in a single 2400-line module. It's
@@ -795,12 +796,14 @@ from fruxon.cli import describe as _describe # noqa: E402, F401
795
796
  from fruxon.cli import doctor as _doctor # noqa: E402, F401
796
797
  from fruxon.cli import environments as _environments # noqa: E402, F401
797
798
  from fruxon.cli import escalation_desks as _escalation_desks # noqa: E402, F401
799
+ from fruxon.cli import escalation_operators as _escalation_operators # noqa: E402, F401
798
800
  from fruxon.cli import escalations as _escalations # noqa: E402, F401
799
801
  from fruxon.cli import examples as _examples # noqa: E402, F401
800
802
  from fruxon.cli import feedback as _feedback # noqa: E402, F401
801
803
  from fruxon.cli import guides as _guides # noqa: E402, F401
802
804
  from fruxon.cli import integrations as _integrations # noqa: E402, F401
803
805
  from fruxon.cli import integrations_sandbox as _integrations_sandbox # noqa: E402, F401
806
+ from fruxon.cli import integrations_webhooks as _integrations_webhooks # noqa: E402, F401
804
807
  from fruxon.cli import keys as _keys # noqa: E402, F401
805
808
  from fruxon.cli import knowledge_bases as _knowledge_bases # noqa: E402, F401
806
809
  from fruxon.cli import knowledge_documents as _knowledge_documents # noqa: E402, F401
@@ -810,7 +813,6 @@ from fruxon.cli import llm_providers as _llm_providers # noqa: E402, F401
810
813
  from fruxon.cli import messages as _messages # noqa: E402, F401
811
814
  from fruxon.cli import metrics as _metrics # noqa: E402, F401
812
815
  from fruxon.cli import participants as _participants # noqa: E402, F401
813
- from fruxon.cli import pipelines as _pipelines # noqa: E402, F401
814
816
  from fruxon.cli import secrets as _secrets # noqa: E402, F401
815
817
  from fruxon.cli import skills as _skills # noqa: E402, F401
816
818
  from fruxon.cli import storage as _storage # noqa: E402, F401