Test status

Each tool in the table below carries one of these. They come from one list of fields per tool (where it is available, what it changes, how it is tested and whether it ran live; fabric_backend/tool_status.py), so a tool has the same status on every page. Draft only says what a tool changes, Tested end to end how far it has been run: a draft tool that ran live is listed as tested, and its What it changes column says it creates nothing.

• Tested end to end — run from Claude as a custom connector, through Microsoft sign-in, against a Fabric workspace with synthetic data (an F2 capacity, the lakehouse demo_lh with the shop schema from fabric_backend/seed.py) on 27 October 2026, through the hosted server's build src-df29c45febaec4b0 (main 5adace8), read-only, as drafts or as dry runs, and then, with the maintainer's approval, one creating call that updated an existing API in place: list_workspaces, list_sources, list_tables, sample_rows, plan_backend, validate_plan, suggest_relationships, analyze_schema, join_path, describe_backend, query_graphql, answer_query_draft, app_readiness, app_starter, plan_drift, lineage, review_plan, compare_semantic_model (as far as the model lookup, which answered not_found: the demo workspace had no model that day), dbt_schema, data_dictionary, semantic_model_draft, ontology_draft, rayfin_connector, silver_notebook_draft, gold_views_draft, drift_monitor_draft, export_item_definitions, create_views (dry run only; nothing was created), create_semantic_model, create_data_agent (dry run only; nothing was created) and create_backend (as an update in place of shop_api with confirmed; no new item was created). A draft that ran so is marked (a draft; creates nothing), a creating tool whose dry run ran tested end to end as a dry run; creating keeps its own status. Not run that day, not even as a dry run: domain_draft, sap_pack_draft, create_report, create_ontology, create_silver_notebook, create_drift_monitor and create_gold_views. The first such run was on 26 October 2026 (14 steps). Changes made after the run are covered by unit tests.
• Experimental — on the hosted server and unit-tested, not yet run against a live workspace.
• Draft only — returns a draft or files and creates nothing in Fabric.
• Available when enabled by the operator — needs a permission the hosted app does not ask for today. The dry run works; asked to create, the tool answers consent with the permission's name (docs/SCOPES.md).
• Planned — not available yet, such as the Claude plugin (see For agents).