fp-cloud-cli 0.0.1b2__tar.gz → 0.0.3b0__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 (203) hide show
  1. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/CHANGELOG.md +143 -0
  2. {fp_cloud_cli-0.0.1b2/fp_cloud_cli.egg-info → fp_cloud_cli-0.0.3b0}/PKG-INFO +175 -9
  3. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/README.md +172 -6
  4. fp_cloud_cli-0.0.3b0/fp_cli/_version.py +1 -0
  5. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/app.py +13 -1
  6. fp_cloud_cli-0.0.3b0/fp_cli/auth.py +507 -0
  7. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/client.py +397 -27
  8. fp_cloud_cli-0.0.3b0/fp_cli/cloud_output.py +523 -0
  9. fp_cloud_cli-0.0.3b0/fp_cli/commands/_cloud.py +45 -0
  10. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/_write.py +3 -1
  11. fp_cloud_cli-0.0.3b0/fp_cli/commands/account_cmds.py +161 -0
  12. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/agent_cmds.py +80 -7
  13. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/alerts_cmds.py +23 -0
  14. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/audits_cmds.py +2 -0
  15. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/auth_cmds.py +218 -51
  16. fp_cloud_cli-0.0.3b0/fp_cli/commands/contracts_cmds.py +67 -0
  17. fp_cloud_cli-0.0.3b0/fp_cli/commands/dashboards_cmds.py +159 -0
  18. fp_cloud_cli-0.0.3b0/fp_cli/commands/evaluators_cmds.py +380 -0
  19. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/events_cmds.py +14 -1
  20. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/fleet_cmds.py +78 -16
  21. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/incidents_cmds.py +305 -8
  22. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/keys_cmds.py +17 -3
  23. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/list_cmds.py +4 -1
  24. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/orgs_cmds.py +18 -1
  25. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/policies_cmds.py +227 -16
  26. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/queries_cmds.py +70 -0
  27. fp_cloud_cli-0.0.3b0/fp_cli/commands/sentiment_cmds.py +49 -0
  28. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/sessions_cmds.py +95 -1
  29. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/settings_cmds.py +2 -0
  30. fp_cloud_cli-0.0.3b0/fp_cli/commands/usage_cmds.py +55 -0
  31. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/users_cmds.py +14 -0
  32. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/enforcement.py +124 -6
  33. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/errors.py +20 -3
  34. fp_cloud_cli-0.0.3b0/fp_cli/evaluator_spec.py +266 -0
  35. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/models.py +100 -6
  36. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/output.py +424 -79
  37. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/permissions.py +32 -1
  38. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/policy_check.py +172 -0
  39. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/select.py +85 -6
  40. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/theme.py +0 -3
  41. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0/fp_cloud_cli.egg-info}/PKG-INFO +175 -9
  42. fp_cloud_cli-0.0.3b0/fp_cloud_cli.egg-info/SOURCES.txt +161 -0
  43. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cloud_cli.egg-info/requires.txt +1 -1
  44. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/pyproject.toml +2 -2
  45. fp_cloud_cli-0.0.3b0/tests/__pycache__/__init__.cpython-314.pyc +0 -0
  46. fp_cloud_cli-0.0.3b0/tests/__pycache__/conftest.cpython-314-pytest-9.2.0.pyc +0 -0
  47. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_alerting.cpython-314-pytest-9.2.0.pyc +0 -0
  48. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_analytics.cpython-314-pytest-9.2.0.pyc +0 -0
  49. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_audits.cpython-314-pytest-9.2.0.pyc +0 -0
  50. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_auth.cpython-314-pytest-9.2.0.pyc +0 -0
  51. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_auth_mode.cpython-314-pytest-9.2.0.pyc +0 -0
  52. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_browser_login.cpython-314-pytest-9.2.0.pyc +0 -0
  53. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_click_compat.cpython-314-pytest-9.2.0.pyc +0 -0
  54. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_client.cpython-314-pytest-9.2.0.pyc +0 -0
  55. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_account.cpython-314-pytest-9.2.0.pyc +0 -0
  56. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_agent.cpython-314-pytest-9.2.0.pyc +0 -0
  57. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_human_views.cpython-314-pytest-9.2.0.pyc +0 -0
  58. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_jev.cpython-314-pytest-9.2.0.pyc +0 -0
  59. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_observability.cpython-314-pytest-9.2.0.pyc +0 -0
  60. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_cloud_transport.cpython-314-pytest-9.2.0.pyc +0 -0
  61. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_commands.cpython-314-pytest-9.2.0.pyc +0 -0
  62. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_config.cpython-314-pytest-9.2.0.pyc +0 -0
  63. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_dashboards_agent.cpython-314-pytest-9.2.0.pyc +0 -0
  64. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_dates.cpython-314-pytest-9.2.0.pyc +0 -0
  65. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_enforcement_logic.cpython-314-pytest-9.2.0.pyc +0 -0
  66. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_evaluator_authoring.cpython-314-pytest-9.2.0.pyc +0 -0
  67. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_facets.cpython-314-pytest-9.2.0.pyc +0 -0
  68. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_failproofai_home.cpython-314-pytest-9.2.0.pyc +0 -0
  69. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_failproofai_home.cpython-314.pyc +0 -0
  70. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_fp_home_contract.cpython-314-pytest-9.2.0.pyc +0 -0
  71. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_hardening.cpython-314-pytest-9.2.0.pyc +0 -0
  72. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_help_table_coverage.cpython-314-pytest-9.2.0.pyc +0 -0
  73. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_keys_queries.cpython-314-pytest-9.2.0.pyc +0 -0
  74. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_list.cpython-314-pytest-9.2.0.pyc +0 -0
  75. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_multivalue.cpython-314-pytest-9.2.0.pyc +0 -0
  76. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_no_customer_identifiers.cpython-314-pytest-9.2.0.pyc +0 -0
  77. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_operator.cpython-314-pytest-9.2.0.pyc +0 -0
  78. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_orgs.cpython-314-pytest-9.2.0.pyc +0 -0
  79. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_output.cpython-314-pytest-9.2.0.pyc +0 -0
  80. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_pagination.cpython-314-pytest-9.2.0.pyc +0 -0
  81. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_policy_check.cpython-314-pytest-9.2.0.pyc +0 -0
  82. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_readme_matches_reality.cpython-314-pytest-9.2.0.pyc +0 -0
  83. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_request_id.cpython-314-pytest-9.2.0.pyc +0 -0
  84. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_review_fixes.cpython-314-pytest-9.2.0.pyc +0 -0
  85. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_round4_behaviour.cpython-314-pytest-9.2.0.pyc +0 -0
  86. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_screen_language.cpython-314-pytest-9.2.0.pyc +0 -0
  87. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_session_reevaluate.cpython-314-pytest-9.2.0.pyc +0 -0
  88. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_staging_parity.cpython-314-pytest-9.2.0.pyc +0 -0
  89. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_telemetry_completeness.cpython-314-pytest-9.2.0.pyc +0 -0
  90. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_usage.cpython-314-pytest-9.2.0.pyc +0 -0
  91. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_v1_origin_diagnostic.cpython-314-pytest-9.2.0.pyc +0 -0
  92. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_v1_routing.cpython-314-pytest-9.2.0.pyc +0 -0
  93. fp_cloud_cli-0.0.3b0/tests/__pycache__/test_whoami.cpython-314-pytest-9.2.0.pyc +0 -0
  94. fp_cloud_cli-0.0.3b0/tests/fake_cloud_smoke.py +312 -0
  95. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_alerting.py +184 -0
  96. fp_cloud_cli-0.0.3b0/tests/test_browser_login.py +943 -0
  97. fp_cloud_cli-0.0.3b0/tests/test_cloud_account.py +123 -0
  98. fp_cloud_cli-0.0.3b0/tests/test_cloud_agent.py +249 -0
  99. fp_cloud_cli-0.0.3b0/tests/test_cloud_human_views.py +283 -0
  100. fp_cloud_cli-0.0.3b0/tests/test_cloud_jev.py +527 -0
  101. fp_cloud_cli-0.0.3b0/tests/test_cloud_observability.py +116 -0
  102. fp_cloud_cli-0.0.3b0/tests/test_cloud_transport.py +141 -0
  103. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_enforcement_logic.py +46 -0
  104. fp_cloud_cli-0.0.3b0/tests/test_evaluator_authoring.py +449 -0
  105. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_help_table_coverage.py +15 -0
  106. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_keys_queries.py +82 -0
  107. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_output.py +70 -20
  108. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_policy_check.py +61 -0
  109. fp_cloud_cli-0.0.3b0/tests/test_request_id.py +111 -0
  110. fp_cloud_cli-0.0.3b0/tests/test_round4_behaviour.py +145 -0
  111. fp_cloud_cli-0.0.3b0/tests/test_screen_language.py +141 -0
  112. fp_cloud_cli-0.0.3b0/tests/test_session_reevaluate.py +33 -0
  113. fp_cloud_cli-0.0.3b0/tests/test_staging_parity.py +198 -0
  114. fp_cloud_cli-0.0.1b2/fp_cli/_version.py +0 -1
  115. fp_cloud_cli-0.0.1b2/fp_cli/auth.py +0 -160
  116. fp_cloud_cli-0.0.1b2/fp_cli/commands/usage_cmds.py +0 -35
  117. fp_cloud_cli-0.0.1b2/fp_cloud_cli.egg-info/SOURCES.txt +0 -126
  118. fp_cloud_cli-0.0.1b2/tests/__pycache__/__init__.cpython-312.pyc +0 -0
  119. fp_cloud_cli-0.0.1b2/tests/__pycache__/conftest.cpython-312-pytest-9.1.1.pyc +0 -0
  120. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_alerting.cpython-312-pytest-9.1.1.pyc +0 -0
  121. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_analytics.cpython-312-pytest-9.1.1.pyc +0 -0
  122. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_audits.cpython-312-pytest-9.1.1.pyc +0 -0
  123. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_auth.cpython-312-pytest-9.1.1.pyc +0 -0
  124. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_auth_mode.cpython-312-pytest-9.1.1.pyc +0 -0
  125. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_click_compat.cpython-312-pytest-9.1.1.pyc +0 -0
  126. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_client.cpython-312-pytest-9.1.1.pyc +0 -0
  127. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_commands.cpython-312-pytest-9.1.1.pyc +0 -0
  128. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_config.cpython-312-pytest-9.1.1.pyc +0 -0
  129. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_dashboards_agent.cpython-312-pytest-9.1.1.pyc +0 -0
  130. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_dates.cpython-312-pytest-9.1.1.pyc +0 -0
  131. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_enforcement_logic.cpython-312-pytest-9.1.1.pyc +0 -0
  132. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_facets.cpython-312-pytest-9.1.1.pyc +0 -0
  133. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_failproofai_home.cpython-312-pytest-9.1.1.pyc +0 -0
  134. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_failproofai_home.cpython-312.pyc +0 -0
  135. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_fp_home_contract.cpython-312-pytest-9.1.1.pyc +0 -0
  136. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_hardening.cpython-312-pytest-9.1.1.pyc +0 -0
  137. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_help_table_coverage.cpython-312-pytest-9.1.1.pyc +0 -0
  138. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_keys_queries.cpython-312-pytest-9.1.1.pyc +0 -0
  139. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_list.cpython-312-pytest-9.1.1.pyc +0 -0
  140. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_multivalue.cpython-312-pytest-9.1.1.pyc +0 -0
  141. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_no_customer_identifiers.cpython-312-pytest-9.1.1.pyc +0 -0
  142. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_operator.cpython-312-pytest-9.1.1.pyc +0 -0
  143. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_orgs.cpython-312-pytest-9.1.1.pyc +0 -0
  144. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_output.cpython-312-pytest-9.1.1.pyc +0 -0
  145. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_pagination.cpython-312-pytest-9.1.1.pyc +0 -0
  146. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_policy_check.cpython-312-pytest-9.1.1.pyc +0 -0
  147. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_readme_matches_reality.cpython-312-pytest-9.1.1.pyc +0 -0
  148. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_review_fixes.cpython-312-pytest-9.1.1.pyc +0 -0
  149. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_telemetry_completeness.cpython-312-pytest-9.1.1.pyc +0 -0
  150. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_usage.cpython-312-pytest-9.1.1.pyc +0 -0
  151. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_v1_origin_diagnostic.cpython-312-pytest-9.1.1.pyc +0 -0
  152. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_v1_routing.cpython-312-pytest-9.1.1.pyc +0 -0
  153. fp_cloud_cli-0.0.1b2/tests/__pycache__/test_whoami.cpython-312-pytest-9.1.1.pyc +0 -0
  154. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/LICENSE +0 -0
  155. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/MANIFEST.in +0 -0
  156. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/__init__.py +0 -0
  157. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/__main__.py +0 -0
  158. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/_click_compat.py +0 -0
  159. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/_context.py +0 -0
  160. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/analytics.py +0 -0
  161. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/analytics_config.py +0 -0
  162. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/analytics_registry.py +0 -0
  163. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/__init__.py +0 -0
  164. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/errors_cmds.py +0 -0
  165. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/evals_cmds.py +0 -0
  166. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/commands/guardrails_cmds.py +0 -0
  167. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/config.py +0 -0
  168. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/dates.py +0 -0
  169. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/orgs.py +0 -0
  170. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cli/py.typed +0 -0
  171. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cloud_cli.egg-info/dependency_links.txt +0 -0
  172. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cloud_cli.egg-info/entry_points.txt +0 -0
  173. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/fp_cloud_cli.egg-info/top_level.txt +0 -0
  174. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/setup.cfg +0 -0
  175. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/__init__.py +0 -0
  176. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/conftest.py +0 -0
  177. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_analytics.py +0 -0
  178. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_audits.py +0 -0
  179. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_auth.py +0 -0
  180. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_auth_mode.py +0 -0
  181. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_click_compat.py +0 -0
  182. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_client.py +0 -0
  183. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_commands.py +0 -0
  184. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_config.py +0 -0
  185. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_dashboards_agent.py +0 -0
  186. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_dates.py +0 -0
  187. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_facets.py +0 -0
  188. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_failproofai_home.py +0 -0
  189. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_fp_home_contract.py +0 -0
  190. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_hardening.py +0 -0
  191. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_list.py +0 -0
  192. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_multivalue.py +0 -0
  193. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_no_customer_identifiers.py +0 -0
  194. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_operator.py +0 -0
  195. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_orgs.py +0 -0
  196. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_pagination.py +0 -0
  197. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_readme_matches_reality.py +0 -0
  198. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_review_fixes.py +0 -0
  199. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_telemetry_completeness.py +0 -0
  200. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_usage.py +0 -0
  201. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_v1_origin_diagnostic.py +0 -0
  202. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_v1_routing.py +0 -0
  203. {fp_cloud_cli-0.0.1b2 → fp_cloud_cli-0.0.3b0}/tests/test_whoami.py +0 -0
@@ -1,5 +1,148 @@
1
1
  # Changelog — `fp` CLI
2
2
 
3
+ ## 0.0.3b0 — 2026-10-25
4
+
5
+ ### Added
6
+
7
+ - `fp login` can sign you in from a browser. On a terminal it starts on a link, to use your browser or SSO: it opens where a browser can (over SSH or with no display it only shows it, and it works from any device), and the terminal finishes on its own once you authorize it. Press Tab for a 6-digit code by email instead, and Tab again to go back. `--email`, `--json` and anything without a terminal keep the code as they always did. If there's no link to offer, as on a dashboard without browser login, it uses the code and never creates a key. Either way you get the same session, with the same lifetime. (#981)
8
+
9
+ ### Changed
10
+
11
+ - Back to the earlier look: rounded panels, the purple `◆ fp` mark, lowercase panel titles and red error boxes. Ids stay whole, wrapping instead of being cut, and screens added since keep their plain tables. `--json`, exit codes and messages are unchanged. (#981)
12
+
13
+ ## 0.0.2 — 2026-10-25
14
+
15
+ **Stable release.** The `0.0.2b0` line the `bump` job opened after `0.0.1` is cut stable
16
+ here rather than published, because the server endpoints these commands drive are now
17
+ deployed to FailproofAI Cloud and the CLI should not trail them as a pre-release.
18
+
19
+ Nothing about the command surface changes at the cut: the entries below are the entire
20
+ diff from `0.0.1`, and the `bump` job opens `0.0.3b0` after the upload.
21
+
22
+ ### Added
23
+
24
+ - Hosted evaluator authoring for code, LLM judge and Jev: create/deploy, AI draft specs, dry-run, labels, toggles, instances, schema, jobs and backfill.
25
+ - Dashboards and tiles; session overview/export/history/re-evaluate; latency and sentiment; query composition/export; alert recipients/issues and agent contracts.
26
+ - Policy author/backtest/candidacy, assistant artifact tables, fail-closed interactive write approvals, and agent-curated home briefs.
27
+ - Organization creation, permission-set roles, member deletion/defaults, usage windows, offers/trial, model context windows, OTEL and Slack controls.
28
+ - `fp policies backtest` covers every policy kind: a published `jev`/`both` policy, or `--semantic checks.json` (with or without a source file), runs the dashboard's every-kind backtest — a free estimate by default, `--run [--sample N]` to spend Jev allowance. New `--kind --semantic --hours --agent-id --env --run --sample`; a regex file or id still uses the module backtest.
29
+ - `fp policies author --kind regex|jev|both` asks the assistant for Jev checks or a hybrid policy.
30
+ - `fp issues list|count` take the inbox filters (`--agent-id --env --machine --source --audit-id --assignee --archived --search --since`, and `count --alert-id`); new `fp issues facets` lists the values they can take.
31
+ - `fp sessions import FILE...` imports Claude Code transcripts, Codex rollouts or event JSONL (`--format --env --dry-run`), as the dashboard's import dialog does.
32
+ - `fp list trigger_events`, `fp list eval_envs` and `fp list metric_keys`.
33
+ - `fp fleet deploy --target POLICY=INTEGRATION[/agt_ID]` scopes a machine's assignment; repeat the flag to include multiple alternatives. `--all-agents POLICY` explicitly clears its scope. Deploy plans, show, history, rollback and JSON readback retain assignment targets.
34
+ - `fp policies publish <id> --kind regex|jev|both [--source f.mjs] [--semantic f.json]`: a
35
+ FailproofAI Cloud policy can carry Jev checks — `jev` (declarations only, no JavaScript) or
36
+ `both` (JavaScript reviewable by exactly its own checks; the server derives the authority).
37
+ The kind follows from what is given when `--kind` is omitted, and a kind that contradicts its
38
+ inputs is exit 2 before anything is sent. The positional source still works.
39
+ - No Jev mode is set by hand: FailproofAI Cloud derives a machine's Jev mode from what is
40
+ deployed to it (on while a `jev`/`both` policy is, off otherwise), so `fp fleet deploy` has
41
+ no `--jev-mode` and there is no `fp fleet jev-mode`. An `observe` effect applies to `jev`
42
+ and `both` policies like any other: their checks are recorded and decide nothing.
43
+ - `fp fleet rollback` says when the Jev mode differs (`jev mode <now> → <then>`, and
44
+ `jevModeBefore` in `--json`); `fp fleet history` shows each generation's Jev mode.
45
+ - The `fleet deploy` and `policies publish` help says Jev checks run on
46
+ FailproofAI Cloud and nothing is installed on the machine, and `fleet show`
47
+ names the reasons a machine with a mode cannot ask (`jev_unconfigured`, `transcripts_disabled`)
48
+ and the `jev_budget` report.
49
+ - `fp policies list/show` print each version's kind and Jev check names (`show` also the
50
+ declarations); `fp fleet list/show` print the machine's Jev mode and the policy errors it
51
+ reported, and `--json` carries `kind`/`semantic`/`semanticSha256`/`authority`/`reviewedBy`,
52
+ `jevMode` and `policyErrors`/`policyErrorsAt` when the server sends them.
53
+
54
+ - `jev:evaluate` is a known permission — Jev through FailproofAI Cloud, charged to the
55
+ org's plan — so `fp keys` and `fp users` accept it instead of refusing it as unknown,
56
+ and the `admin` preset carries it, as the server's built-in admin set now does. The
57
+ server refuses a KEY carrying it without both `events:add` and `policies:pull` (422,
58
+ naming what to add in `missing_permissions`); the `admin` preset has both. (#833)
59
+ - `fp keys create/update --permission-set machine`: the dashboard's key-only preset
60
+ (`events:add` + `policies:pull` + `jev:evaluate`), for an enrolled machine using Jev through
61
+ FailproofAI Cloud. `fp keys` also refuses `jev:evaluate` without both prerequisites itself
62
+ (exit 2, naming what is missing) instead of sending the key for the server's 422. (#833)
63
+ - `fp policies list` and `fp policies show` print what a `jev`/`both` version's checks take of a
64
+ machine's Jev question budget (`jevChars`), and a deploy refused with `jev_budget_exceeded`
65
+ lists each Jev policy's share, largest first (the `hint` under `--json`), so the refusal says
66
+ which policy to leave off.
67
+
68
+ ### Changed
69
+
70
+ - New Cloud API families work in key mode; unsupported session-only commands deny before HTTP and unknown-route 404s exit 6 with an availability message.
71
+ - Shared screens use the mint/pink wordmark and grey labels, without boxes/rules or shortened ids; existing JSON contracts are unchanged.
72
+ - The agent skill, command reference, README and Cloud CLI docs include end-to-end evaluator workflows. No version bump or release is performed.
73
+ - `fp policies publish`'s refusal of Jev fields in the JavaScript now says where Jev checks go:
74
+ the policy's own declarations, `--kind both --semantic checks.json`.
75
+ - `fp guardrails summary` shows how many machines run Jev in each mode, reading the summary's
76
+ `jev.machines.observe` and `jev.machines.enforce`.
77
+ - `fp policies publish` (and `policies compose --publish`) refuses a source carrying Jev
78
+ fields a cloud policy never reads — a `semanticPolicies.add(...)` call, or a registration
79
+ declaring `authority: "reviewable"` — before anything is sent (exit 1, `--no-verify` does
80
+ not skip it). Both were published as versions that read Jev-aware and are not: semantic
81
+ checks load only from a pack, and a cloud policy's authority comes from its deployment, so
82
+ it stays hard. Ship Jev checks in a pack with `failproofai publish`. Same rule, and the
83
+ same comment-aware detection, as the dashboard's publish form; the server does not read
84
+ the source, so nothing else refuses it for `fp`. (#833)
85
+
86
+ ### Fixed
87
+
88
+ - Remove the unused colour-keyed permission rank, document full-id rendering, emit UTC `Z` timestamps for deploy backfills, and report approval-answer failures without a traceback while restoring the terminal (#885).
89
+ - Reject natural-language binary judge steps, distinguish unknown routes from missing records on 404, normalize standalone backfill ranges to UTC `Z`, expose all subcommands in help, and render artifact headers before titles with consistent session-only wording (#885).
90
+ - New Cloud commands use deliberate human summaries/tables and actionable empty states at 80/140 columns without raw response blobs. Evaluator previews display before writes and require explicit `--force` after failures; plan/claim deny key mode, deploy specs can omit the positional key, and older settings-route 404s degrade clearly. Existing JSON payloads stay unchanged (#885).
91
+ - `fp evaluators deploy` keeps the previous version's condition and labels unless `--condition`/`--label` change them, so a new version no longer silently widens to every session (#885).
92
+ - Evaluation backfill covers code, LLM judge and Jev evaluators, as FailproofAI Cloud now does: `fp evaluators deploy --backfill` no longer refuses judge/Jev, and both commands warn that judge/Jev backfills spend model budget instead of saying they are skipped.
93
+ - `fp usage windows` says it needs an API key (the dashboard has no session route for it) instead of reporting the route as unavailable.
94
+ - `fp issues close --help` no longer claims exit 9 for an issue that already ended: it is exit 1, as it always was, and it names `fp audits dismiss` rather than a command that does not exist.
95
+ - `fp fleet history` keeps `gen`, `when` and `jev` visible at 80 columns (rollback needs `gen`): the policy list is shortened, then dropped, and `change` wraps first.
96
+ - `fp fleet show` and `fp fleet history` name an exact-profile target by the profile label the machine reports (`claude/.claude-work`, with the `agt_…` id kept in `show`), falling back to the bare id.
97
+
98
+ ## 0.0.1 — 2026-09-22
99
+
100
+ **First stable release.** `0.0.1b1` and `0.0.1b2` are the two betas behind it; the
101
+ `0.0.1b3` line the `bump` job opened is cut stable here rather than published, because
102
+ the server endpoints these commands drive are deployed to FailproofAI Cloud and the
103
+ CLI half should not stay a pre-release behind them. Until now `pipx install
104
+ fp-cloud-cli` resolved a beta only because no stable existed — a default that would
105
+ have silently changed the day one did. `Development Status` moves to
106
+ `5 - Production/Stable` with the version, so the classifier and the one string pip
107
+ reads say the same thing.
108
+
109
+ Nothing about the command surface changes at the cut: the entries below are the
110
+ entire diff from `0.0.1b2`, and `0.0.2b0` opens the next beta line.
111
+
112
+ ### Added
113
+
114
+ - `fp issues close <id>` — end an issue as won't-fix. Distinct from `resolve`: a
115
+ recurring audit finding reopens a **resolved** issue and leaves a **closed** one
116
+ alone. On an audit issue it marks the finding `dismissed`, without writing the
117
+ org-wide fingerprint suppression that `fp audits dismiss` writes. Exit 9 if the
118
+ issue already ended. (#815)
119
+ - `fp issues archive <id>` / `unarchive <id>` — take an issue off the board and put
120
+ it back. Orthogonal to state, allowed in any state, no confirmation prompt. (#815)
121
+ - `fp issues clear (--audit <id> | --all-audits | --everything) [--dry-run]` — resolve
122
+ every open issue in a scope plus the audit findings behind them, in one server-side
123
+ transaction. Exactly one scope flag is required. Needs `issues:close` **and**
124
+ `audits:write`. Writes no suppression, so anything still broken reopens its issue
125
+ on the next run. The confirm names the count from a dry run that shares its
126
+ scope predicate with the write. (#815)
127
+ - `issues list --state closed` is accepted, and `Incident` carries `closed_at` and
128
+ `archived_at`. (#815)
129
+
130
+ ### Fixes
131
+
132
+ - The recurrence sentence said two different things in one release. `audits resolve`'s
133
+ confirm line (`a genuine recurrence re-opens as new`), the skill and the command
134
+ reference implied a recurrence opens a **different** issue; `issues close --help`, the
135
+ audits guide and the CLI reference said the resolved issue **reopens**. The second is
136
+ the one the rest of the model needs — a `closed` issue has to have something to stay
137
+ closed through — so `reopens` is now what every surface says. (#815)
138
+ - `issues clear --help` claimed the `--dry-run` count "cannot disagree" with the write.
139
+ The two requests share a scope predicate, not a row set, so an issue entering the scope
140
+ between them is cleared without being in the confirmed number — correct for a scoped
141
+ clear, but not the guarantee that was written. The help now states the real one, and
142
+ names the closing line as the count of what changed. (#815)
143
+ - The skill answered "clear all our issues" with `--all-audits`, which leaves alert-born
144
+ and hand-opened issues untouched. Settling the scope is now the first step. (#815)
145
+
3
146
  ## 0.0.1b2 — 2026-08-25
4
147
 
5
148
  Open for the next release. `0.0.1b1` published on 2026-08-24 and the `bump` job
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: fp-cloud-cli
3
- Version: 0.0.1b2
3
+ Version: 0.0.3b0
4
4
  Summary: Command line client for FailproofAI Cloud — sessions, events, evaluations and audits from your terminal
5
5
  Author-email: Failproof AI <failproofai@exosphere.host>
6
6
  License: MIT License
@@ -51,7 +51,7 @@ Project-URL: Documentation, https://docs.befailproof.ai/reference/cloud-cli
51
51
  Project-URL: Source, https://github.com/FailproofAI/failproofai
52
52
  Project-URL: Changelog, https://github.com/FailproofAI/failproofai/blob/main/fp-cloud-cli/CHANGELOG.md
53
53
  Keywords: agents,observability,ai,monitoring,failproofai,cli
54
- Classifier: Development Status :: 4 - Beta
54
+ Classifier: Development Status :: 5 - Production/Stable
55
55
  Classifier: Environment :: Console
56
56
  Classifier: Intended Audience :: Developers
57
57
  Classifier: Programming Language :: Python :: 3
@@ -64,7 +64,7 @@ Requires-Python: >=3.10
64
64
  Description-Content-Type: text/markdown
65
65
  License-File: LICENSE
66
66
  Requires-Dist: httpx>=0.27
67
- Requires-Dist: typer<0.28,>=0.13
67
+ Requires-Dist: typer<0.30,>=0.13
68
68
  Requires-Dist: click>=8.1
69
69
  Requires-Dist: rich>=13
70
70
  Requires-Dist: pygments>=2.13
@@ -110,17 +110,24 @@ uv run fp --help
110
110
 
111
111
  ## Authentication
112
112
 
113
- The CLI talks to your dashboard (set `--base-url` or `FP_DASHBOARD_URL`) and logs in with
114
- an emailed one-time code:
113
+ The CLI talks to your dashboard (set `--base-url` or `FP_DASHBOARD_URL`) and signs you in
114
+ from a browser or with an emailed one-time code:
115
115
 
116
116
  ```bash
117
- fp login --email you@example.com
118
- # enter the 6-digit code; the session is stored in
117
+ fp login # opens a link to authorize; press tab for a code by email instead
118
+ fp login --email you@example.com # straight to the code; also what scripts and pipes use
119
+ # either way the session is stored in
119
120
  # ~/.failproofai/fpcli/cli-auth.json (mode 0600)
120
121
  fp whoami
121
122
  fp logout
122
123
  ```
123
124
 
125
+ `fp` starts on a link, to sign in with your browser or SSO, and opens it (over SSH or with no
126
+ display it only shows it, and it works from any device). Authorize it and the terminal finishes
127
+ on its own. That terminal gets your access in all your orgs until the session expires, so only
128
+ authorize a link you just asked for. Press **tab** for a code by email instead, and tab again to
129
+ go back. If there's no link to offer, as on a dashboard without browser login, it uses the code.
130
+
124
131
  Sessions expire (24h by default); re-run `fp login` when prompted.
125
132
 
126
133
  ## Working across orgs (multi-tenant)
@@ -166,7 +173,7 @@ fp keys list|show|create|update|disable|regenerate # API keys (secret shown
166
173
  fp users list|show|create|update|disable|enable
167
174
  fp settings list|schema|set
168
175
  fp alerts list|show|create|update|delete|test
169
- fp issues list|count|show|ack|assign|resolve|comment-add|comment-list|comment-delete|subscribe|subscribers|unsubscribe|open
176
+ fp issues list|count|show|ack|assign|resolve|close|archive|unarchive|clear|comment-add|comment-list|comment-delete|subscribe|subscribers|unsubscribe|open
170
177
  fp audits list|show|create|edit|delete|run|runs|findings|finding # scheduled audits
171
178
  fp audits ack|assign|resolve|dismiss|mute|reopen # triage a finding
172
179
  fp audits context-show|context-set|context-refresh # reference context
@@ -215,6 +222,46 @@ fp fleet deploy ci-runner-01 --add no-force-push
215
222
  fp guardrails summary --since 24h
216
223
  ```
217
224
 
225
+ A policy has a **kind**: `regex` (JavaScript — the default, and what every
226
+ earlier version is), `jev` (Jev checks only, from a JSON file of declarations —
227
+ each exactly a failproofai pack manifest's semantic entry), or `both`
228
+ (JavaScript whose verdict its own Jev checks may clear, deployed as one).
229
+ Jev checks run on FailproofAI Cloud; nothing is installed on the machine.
230
+ While a `jev` or `both` policy is deployed to a machine, FailproofAI Cloud
231
+ turns Jev on there and the machine sends each checked tool call to it; with
232
+ none, Jev is off. There is no Jev mode to set: trial a policy with `:observe`
233
+ (its checks are recorded, never applied), then deploy it as `enforce`, where
234
+ Jev's checks **block** calls as well as clearing the regex verdicts they
235
+ review.
236
+
237
+ ```bash
238
+ fp policies publish prod-db-intent --kind jev --semantic ./checks.json
239
+ fp policies publish no-prod-db --kind both --source ./rule.mjs --semantic ./checks.json
240
+ fp fleet deploy ci-runner-01 --add prod-db-intent:observe
241
+ fp fleet show ci-runner-01 # its Jev mode, and any policy errors it reported
242
+ ```
243
+
244
+ Published policy versions do not contain agent-routing code. Each assignment
245
+ can instead target every agent (the default), an integration including future
246
+ profiles, or a particular profile reported by that machine. The same target
247
+ applies to the regex and Jev parts of a `both` policy:
248
+
249
+ ```bash
250
+ fp fleet deploy ci-runner-01 --add no-prod-db --target no-prod-db=hermes
251
+ fp fleet deploy ci-runner-01 --target no-prod-db=hermes/agt_1234567890abcdef
252
+ fp fleet deploy ci-runner-01 --all-agents no-prod-db # explicitly remove targeting
253
+ ```
254
+
255
+ Repeat `--target` for multiple alternatives on one assignment. `fp fleet
256
+ show` and `fp fleet history` display the assigned scope; `--json` includes
257
+ `agentTargets` on each targeted policy. A machine must report agent-scoping
258
+ support before accepting a new target. When its identity cannot be resolved,
259
+ a targeted policy does not match; unscoped policy remains in force.
260
+ Newly installed shell hooks carry their settings scope. Reinstall older hooks
261
+ to add the hint; without it, or for an integration that cannot report the
262
+ source of multiple installed scopes, the machine reports
263
+ `agent_scope_unresolved` rather than guessing which profile ran the call.
264
+
218
265
  **A deploy REPLACES a machine's whole policy set.** The server takes the full
219
266
  list and does not merge, so `fleet deploy` reads what the machine currently runs,
220
267
  applies your `--add`/`--remove`, prints the complete resulting set, and writes
@@ -247,6 +294,126 @@ These commands are **session-only** (`fp login`). They are absent from the
247
294
  versioned API an API key authenticates against, so `--api-key` exits 2 with the
248
295
  reason rather than failing at the request.
249
296
 
297
+ ## Author an evaluator
298
+
299
+ `fp evaluators` authors hosted definitions; `fp evals` continues to read results.
300
+ Creation enables a definition by default. Check `fp evaluators instances` first:
301
+ Cloud needs an enabled managed instance. Writes need `evaluations:trigger`;
302
+ session dry-runs and `evaluators schema` also need `events:read`.
303
+
304
+ Write `error_free.py` as a restricted Python expression (no imports or functions):
305
+
306
+ ```python
307
+ EvalResult(score=Score(1.0 if session.count("error") == 0 else 0.0), reasoning="Error-free session")
308
+ ```
309
+
310
+ ```bash
311
+ fp --json evaluators create --key error_free --name "Error free" --code error_free.py \
312
+ --result-kind score --dry-run-on run-001
313
+ fp --json evaluators dry-run --code error_free.py --session run-001
314
+ fp --json evaluators deploy error_free --code error_free.py --version 2 --dry-run-on run-001
315
+ fp --json evaluators list --key error_free --all
316
+ ```
317
+
318
+ LLM judge (Cloud selects the model; judge dry-runs are refused):
319
+
320
+ ```bash
321
+ fp --json evaluators create --key relevance --name Relevance --judge \
322
+ --criteria "Grade how directly the answer addresses the request" --threshold 0.7
323
+ fp --json evaluators deploy relevance --version 2 --judge \
324
+ --criteria "Grade relevance and completeness" --threshold 0.8
325
+ fp --json sessions re-evaluate run-001
326
+ fp --json sessions history run-001
327
+ ```
328
+
329
+ Jev binary or graded rubric:
330
+
331
+ ```bash
332
+ fp --json evaluators create --key resolved --name Resolved --jev noul \
333
+ --instructions "Was the request resolved?" --true "Resolved" --false "Unresolved"
334
+ fp --json evaluators dry-run --jev noul --instructions "Was the request resolved?" \
335
+ --true "Resolved" --false "Unresolved" --session run-001
336
+ fp --json evaluators deploy resolved --version 2 --jev score \
337
+ --instructions "Grade resolution quality" \
338
+ --level "Unresolved" --level "Partly resolved" --level "Fully resolved"
339
+ ```
340
+
341
+ Jev dry-runs spend model budget. Rubrics need 3–5 distinct levels, worst first.
342
+ Thresholds are 0–1; judge/Jev always return a score. `deploy` creates the new
343
+ immutable version before disabling older enabled versions. If disabling fails,
344
+ the CLI names the published id; inspect `list --all` and recover explicitly.
345
+ `--backfill 7d` works for every kind (judge/Jev spend model budget); `evaluators backfill --from T --to T` accepts ≤90 days and `--dry-run` counts the work first.
346
+
347
+ Human output shows each `--dry-run-on` session's outcome before creation or
348
+ deployment. Any failed run stops the write; after reviewing the failure, an
349
+ explicit `--force` overrides this guard. Existing `--json` response shapes stay
350
+ unchanged.
351
+
352
+ AI drafting is session-only and writes an API spec that create/deploy accept:
353
+
354
+ ```bash
355
+ fp login
356
+ fp --json evaluators draft "Measure error-free sessions with code" --kind code --out evaluator.json
357
+ # Review the spec, especially eval_key and evaluator_source, before enabling it.
358
+ fp --json evaluators create --file evaluator.json --dry-run-on run-001
359
+ fp --json evaluators dry-run --file evaluator.json
360
+ ```
361
+
362
+ Spec fields: `eval_key`, `display_name`, `eval_version`, `result_kind`, `labels`,
363
+ `condition_source`, `evaluator_source`, `timeout_seconds`. Judge/Jev sources are
364
+ JSON envelope **strings**, not nested objects. `--file` is exclusive with discrete
365
+ spec flags; deploy may override a file's version. Files written by the CLI are
366
+ created exclusively, so existing files are never silently replaced.
367
+ See [the command reference](skill/references/commands.md#author-an-evaluator).
368
+
369
+ ## Dashboard parity
370
+
371
+ ```text
372
+ fp dashboards list|show|create|update|delete
373
+ fp dashboards tiles <id> list|add|update|remove|layout
374
+ fp sessions show|export|history|re-evaluate <id>
375
+ fp events latency
376
+ fp sentiment summary|messages|sessions|session <id>
377
+ fp query compose "question" [--run] # session
378
+ fp query export [<id>] [--sql SQL] --format csv|json [--out FILE]
379
+ fp alerts recipients
380
+ fp alerts issues <id> [--create --title ... --summary ...]
381
+ fp audits contracts list|show|create|update
382
+ fp policies author "intent"|backtest <file-or-id>|candidacy --issue <id> # session
383
+ fp agent brief [--range 24h|7d] # session
384
+ fp orgs create --name N [--slug S] # session
385
+ fp roles list|show|create|update|delete
386
+ fp users delete <id>
387
+ fp users defaults
388
+ fp usage windows
389
+ fp plan # session
390
+ fp plan claim <offer> # session
391
+ fp settings context-windows list|set <model> <tokens>|delete <model>
392
+ fp otel status
393
+ fp slack status|disconnect # session
394
+ ```
395
+
396
+ `fp agent ask` runs artifact SQL through the permission-gated query runner and
397
+ renders tables/stats. It prompts before approving a write on a terminal.
398
+ Scripts and `--json` **decline** unless you explicitly pass `--approve`.
399
+ Normal create/update commands keep their existing non-interactive confirmation
400
+ behavior; assistant approvals are a separate safety boundary.
401
+
402
+ All new commands accept the global `--json` before the command. Session-only
403
+ commands fail before HTTP in API-key mode, with exit 2 and a `fp login` hint.
404
+ Unknown-route 404s exit 6 with “not available on this FailproofAI Cloud yet”.
405
+ Missing-record 404s also exit 6 but report that the record was not found.
406
+ `plan` and `plan claim` require a signed-in person and deny API-key mode before
407
+ HTTP with the standard `fp login` message.
408
+ Human screens use rounded panels, the purple `◆ fp` mark and full ids, which wrap
409
+ rather than being cut; existing JSON shapes are unchanged.
410
+
411
+ Human commands show summaries, tables and wrapped text rather than response
412
+ objects. Use global `--json` for raw API results. For `sessions export` or
413
+ `query export --format json`, use `--out FILE` to save the JSON; without either
414
+ option, the terminal shows a readable session or query view. CSV exports remain
415
+ plain CSV for piping.
416
+
250
417
  ## Configuration
251
418
 
252
419
  | Setting | Flag | Env var | Default |
@@ -332,4 +499,3 @@ working as an opt-out if it is ever switched back on. See
332
499
  cd fp-cloud-cli
333
500
  uv run --extra dev pytest
334
501
  ```
335
-
@@ -34,17 +34,24 @@ uv run fp --help
34
34
 
35
35
  ## Authentication
36
36
 
37
- The CLI talks to your dashboard (set `--base-url` or `FP_DASHBOARD_URL`) and logs in with
38
- an emailed one-time code:
37
+ The CLI talks to your dashboard (set `--base-url` or `FP_DASHBOARD_URL`) and signs you in
38
+ from a browser or with an emailed one-time code:
39
39
 
40
40
  ```bash
41
- fp login --email you@example.com
42
- # enter the 6-digit code; the session is stored in
41
+ fp login # opens a link to authorize; press tab for a code by email instead
42
+ fp login --email you@example.com # straight to the code; also what scripts and pipes use
43
+ # either way the session is stored in
43
44
  # ~/.failproofai/fpcli/cli-auth.json (mode 0600)
44
45
  fp whoami
45
46
  fp logout
46
47
  ```
47
48
 
49
+ `fp` starts on a link, to sign in with your browser or SSO, and opens it (over SSH or with no
50
+ display it only shows it, and it works from any device). Authorize it and the terminal finishes
51
+ on its own. That terminal gets your access in all your orgs until the session expires, so only
52
+ authorize a link you just asked for. Press **tab** for a code by email instead, and tab again to
53
+ go back. If there's no link to offer, as on a dashboard without browser login, it uses the code.
54
+
48
55
  Sessions expire (24h by default); re-run `fp login` when prompted.
49
56
 
50
57
  ## Working across orgs (multi-tenant)
@@ -90,7 +97,7 @@ fp keys list|show|create|update|disable|regenerate # API keys (secret shown
90
97
  fp users list|show|create|update|disable|enable
91
98
  fp settings list|schema|set
92
99
  fp alerts list|show|create|update|delete|test
93
- fp issues list|count|show|ack|assign|resolve|comment-add|comment-list|comment-delete|subscribe|subscribers|unsubscribe|open
100
+ fp issues list|count|show|ack|assign|resolve|close|archive|unarchive|clear|comment-add|comment-list|comment-delete|subscribe|subscribers|unsubscribe|open
94
101
  fp audits list|show|create|edit|delete|run|runs|findings|finding # scheduled audits
95
102
  fp audits ack|assign|resolve|dismiss|mute|reopen # triage a finding
96
103
  fp audits context-show|context-set|context-refresh # reference context
@@ -139,6 +146,46 @@ fp fleet deploy ci-runner-01 --add no-force-push
139
146
  fp guardrails summary --since 24h
140
147
  ```
141
148
 
149
+ A policy has a **kind**: `regex` (JavaScript — the default, and what every
150
+ earlier version is), `jev` (Jev checks only, from a JSON file of declarations —
151
+ each exactly a failproofai pack manifest's semantic entry), or `both`
152
+ (JavaScript whose verdict its own Jev checks may clear, deployed as one).
153
+ Jev checks run on FailproofAI Cloud; nothing is installed on the machine.
154
+ While a `jev` or `both` policy is deployed to a machine, FailproofAI Cloud
155
+ turns Jev on there and the machine sends each checked tool call to it; with
156
+ none, Jev is off. There is no Jev mode to set: trial a policy with `:observe`
157
+ (its checks are recorded, never applied), then deploy it as `enforce`, where
158
+ Jev's checks **block** calls as well as clearing the regex verdicts they
159
+ review.
160
+
161
+ ```bash
162
+ fp policies publish prod-db-intent --kind jev --semantic ./checks.json
163
+ fp policies publish no-prod-db --kind both --source ./rule.mjs --semantic ./checks.json
164
+ fp fleet deploy ci-runner-01 --add prod-db-intent:observe
165
+ fp fleet show ci-runner-01 # its Jev mode, and any policy errors it reported
166
+ ```
167
+
168
+ Published policy versions do not contain agent-routing code. Each assignment
169
+ can instead target every agent (the default), an integration including future
170
+ profiles, or a particular profile reported by that machine. The same target
171
+ applies to the regex and Jev parts of a `both` policy:
172
+
173
+ ```bash
174
+ fp fleet deploy ci-runner-01 --add no-prod-db --target no-prod-db=hermes
175
+ fp fleet deploy ci-runner-01 --target no-prod-db=hermes/agt_1234567890abcdef
176
+ fp fleet deploy ci-runner-01 --all-agents no-prod-db # explicitly remove targeting
177
+ ```
178
+
179
+ Repeat `--target` for multiple alternatives on one assignment. `fp fleet
180
+ show` and `fp fleet history` display the assigned scope; `--json` includes
181
+ `agentTargets` on each targeted policy. A machine must report agent-scoping
182
+ support before accepting a new target. When its identity cannot be resolved,
183
+ a targeted policy does not match; unscoped policy remains in force.
184
+ Newly installed shell hooks carry their settings scope. Reinstall older hooks
185
+ to add the hint; without it, or for an integration that cannot report the
186
+ source of multiple installed scopes, the machine reports
187
+ `agent_scope_unresolved` rather than guessing which profile ran the call.
188
+
142
189
  **A deploy REPLACES a machine's whole policy set.** The server takes the full
143
190
  list and does not merge, so `fleet deploy` reads what the machine currently runs,
144
191
  applies your `--add`/`--remove`, prints the complete resulting set, and writes
@@ -171,6 +218,126 @@ These commands are **session-only** (`fp login`). They are absent from the
171
218
  versioned API an API key authenticates against, so `--api-key` exits 2 with the
172
219
  reason rather than failing at the request.
173
220
 
221
+ ## Author an evaluator
222
+
223
+ `fp evaluators` authors hosted definitions; `fp evals` continues to read results.
224
+ Creation enables a definition by default. Check `fp evaluators instances` first:
225
+ Cloud needs an enabled managed instance. Writes need `evaluations:trigger`;
226
+ session dry-runs and `evaluators schema` also need `events:read`.
227
+
228
+ Write `error_free.py` as a restricted Python expression (no imports or functions):
229
+
230
+ ```python
231
+ EvalResult(score=Score(1.0 if session.count("error") == 0 else 0.0), reasoning="Error-free session")
232
+ ```
233
+
234
+ ```bash
235
+ fp --json evaluators create --key error_free --name "Error free" --code error_free.py \
236
+ --result-kind score --dry-run-on run-001
237
+ fp --json evaluators dry-run --code error_free.py --session run-001
238
+ fp --json evaluators deploy error_free --code error_free.py --version 2 --dry-run-on run-001
239
+ fp --json evaluators list --key error_free --all
240
+ ```
241
+
242
+ LLM judge (Cloud selects the model; judge dry-runs are refused):
243
+
244
+ ```bash
245
+ fp --json evaluators create --key relevance --name Relevance --judge \
246
+ --criteria "Grade how directly the answer addresses the request" --threshold 0.7
247
+ fp --json evaluators deploy relevance --version 2 --judge \
248
+ --criteria "Grade relevance and completeness" --threshold 0.8
249
+ fp --json sessions re-evaluate run-001
250
+ fp --json sessions history run-001
251
+ ```
252
+
253
+ Jev binary or graded rubric:
254
+
255
+ ```bash
256
+ fp --json evaluators create --key resolved --name Resolved --jev noul \
257
+ --instructions "Was the request resolved?" --true "Resolved" --false "Unresolved"
258
+ fp --json evaluators dry-run --jev noul --instructions "Was the request resolved?" \
259
+ --true "Resolved" --false "Unresolved" --session run-001
260
+ fp --json evaluators deploy resolved --version 2 --jev score \
261
+ --instructions "Grade resolution quality" \
262
+ --level "Unresolved" --level "Partly resolved" --level "Fully resolved"
263
+ ```
264
+
265
+ Jev dry-runs spend model budget. Rubrics need 3–5 distinct levels, worst first.
266
+ Thresholds are 0–1; judge/Jev always return a score. `deploy` creates the new
267
+ immutable version before disabling older enabled versions. If disabling fails,
268
+ the CLI names the published id; inspect `list --all` and recover explicitly.
269
+ `--backfill 7d` works for every kind (judge/Jev spend model budget); `evaluators backfill --from T --to T` accepts ≤90 days and `--dry-run` counts the work first.
270
+
271
+ Human output shows each `--dry-run-on` session's outcome before creation or
272
+ deployment. Any failed run stops the write; after reviewing the failure, an
273
+ explicit `--force` overrides this guard. Existing `--json` response shapes stay
274
+ unchanged.
275
+
276
+ AI drafting is session-only and writes an API spec that create/deploy accept:
277
+
278
+ ```bash
279
+ fp login
280
+ fp --json evaluators draft "Measure error-free sessions with code" --kind code --out evaluator.json
281
+ # Review the spec, especially eval_key and evaluator_source, before enabling it.
282
+ fp --json evaluators create --file evaluator.json --dry-run-on run-001
283
+ fp --json evaluators dry-run --file evaluator.json
284
+ ```
285
+
286
+ Spec fields: `eval_key`, `display_name`, `eval_version`, `result_kind`, `labels`,
287
+ `condition_source`, `evaluator_source`, `timeout_seconds`. Judge/Jev sources are
288
+ JSON envelope **strings**, not nested objects. `--file` is exclusive with discrete
289
+ spec flags; deploy may override a file's version. Files written by the CLI are
290
+ created exclusively, so existing files are never silently replaced.
291
+ See [the command reference](skill/references/commands.md#author-an-evaluator).
292
+
293
+ ## Dashboard parity
294
+
295
+ ```text
296
+ fp dashboards list|show|create|update|delete
297
+ fp dashboards tiles <id> list|add|update|remove|layout
298
+ fp sessions show|export|history|re-evaluate <id>
299
+ fp events latency
300
+ fp sentiment summary|messages|sessions|session <id>
301
+ fp query compose "question" [--run] # session
302
+ fp query export [<id>] [--sql SQL] --format csv|json [--out FILE]
303
+ fp alerts recipients
304
+ fp alerts issues <id> [--create --title ... --summary ...]
305
+ fp audits contracts list|show|create|update
306
+ fp policies author "intent"|backtest <file-or-id>|candidacy --issue <id> # session
307
+ fp agent brief [--range 24h|7d] # session
308
+ fp orgs create --name N [--slug S] # session
309
+ fp roles list|show|create|update|delete
310
+ fp users delete <id>
311
+ fp users defaults
312
+ fp usage windows
313
+ fp plan # session
314
+ fp plan claim <offer> # session
315
+ fp settings context-windows list|set <model> <tokens>|delete <model>
316
+ fp otel status
317
+ fp slack status|disconnect # session
318
+ ```
319
+
320
+ `fp agent ask` runs artifact SQL through the permission-gated query runner and
321
+ renders tables/stats. It prompts before approving a write on a terminal.
322
+ Scripts and `--json` **decline** unless you explicitly pass `--approve`.
323
+ Normal create/update commands keep their existing non-interactive confirmation
324
+ behavior; assistant approvals are a separate safety boundary.
325
+
326
+ All new commands accept the global `--json` before the command. Session-only
327
+ commands fail before HTTP in API-key mode, with exit 2 and a `fp login` hint.
328
+ Unknown-route 404s exit 6 with “not available on this FailproofAI Cloud yet”.
329
+ Missing-record 404s also exit 6 but report that the record was not found.
330
+ `plan` and `plan claim` require a signed-in person and deny API-key mode before
331
+ HTTP with the standard `fp login` message.
332
+ Human screens use rounded panels, the purple `◆ fp` mark and full ids, which wrap
333
+ rather than being cut; existing JSON shapes are unchanged.
334
+
335
+ Human commands show summaries, tables and wrapped text rather than response
336
+ objects. Use global `--json` for raw API results. For `sessions export` or
337
+ `query export --format json`, use `--out FILE` to save the JSON; without either
338
+ option, the terminal shows a readable session or query view. CSV exports remain
339
+ plain CSV for piping.
340
+
174
341
  ## Configuration
175
342
 
176
343
  | Setting | Flag | Env var | Default |
@@ -256,4 +423,3 @@ working as an opt-out if it is ever switched back on. See
256
423
  cd fp-cloud-cli
257
424
  uv run --extra dev pytest
258
425
  ```
259
-
@@ -0,0 +1 @@
1
+ __version__ = "0.0.3b0"