Fabric Agentic Workspace — One-Click Setup — v0.7.0

Specialist teams, clearer delegation, and leaner startup

This prerelease strengthens how the 47-agent Fabric workspace discovers knowledge, delegates work, validates changes, and reports results.

Highlights

• Configures nested delegation in folder and workspace settings for Master → Team Lead → Worker execution.
• Adds specialist knowledge, playbooks, validation requirements, tool preferences, and scope boundaries.
• Registers upstream skills natively, discovers relevant skills automatically, and improves handling of renamed skill paths.
• Introduces shared WORK ORDER / WORK RESULT contracts, Architect PLAN, QA VERDICT, and approval escalation.
• Replaces startup menus and repeated probes with a single session-status script.
• Introduces a Master-owned live-model connection procedure and passes connection context to semantic-model specialists.
• Improves vendor-refresh observability and aligns maintenance guidance.
• Expands generated-content and refresh regression tests.

Validation and status

71 Windows CI tests passed on the release commit.

This remains a prerelease. Known follow-up work includes the Master's MCP permission wiring, vendor-refresh failure handling, and recovery from uncertain write outcomes.

Full changelog

Fabric Agentic Workspace – One-Click Setup – v0.6.2

The installer is now authoritative — and safely self-pruning.

This release makes re-running the installer deterministic and honest. On every run the installer is the single source of truth for everything it ships, cleans up after itself when files are renamed or removed, and never touches anything you own.

Vendor skill repos are now authoritative-from-upstream: skills-for-fabric/ and power-bi-agentic-development/ are force-refreshed to upstream (fetch --prune + reset --hard origin/HEAD) instead of a fast-forward-only pull, so they always mirror live upstream and never silently drift. Any local edit is auto-stashed onto a timestamped stash first, so nothing is lost and nothing lingers as drift.

The installer is also self-pruning. It reads the previous installed-manifest.json write-log and removes only the strict old − new set difference — files it shipped before but no longer ships (renamed agents, superseded configs, dropped skills). It is scoped to installer-owned roots, excludes machine-local state, and is never a directory sweep, so user files, Fabric workspace folders, and business clones are never touched. The purge is skipped on an unrecognised manifest schema.

Also in this release

• Opt-in pull for existing business clones — when a re-run finds a repository already cloned under source-control-repositories/, it asks "Pull existing branches so they match online? (y/N)" (default No). Accept and it fast-forwards only clean, strictly-behind branch worktrees; dirty or diverged branches are left as-is for a manual pull. Decline and it keeps the previous fetch-only behaviour. No local work is ever moved without your say-so.

• Self-test respects user-authored agents — the post-generation check now asserts all managed agents are present and reports any extra *.agent.md files as preserved, instead of demanding an exact manifest count. Adding your own agent no longer trips a false failure.

• README "Keeping it up to date" contract — a new maintainability section documents exactly how updates behave and which files you should and should not edit.

• Re-scoped Capability Maintenance agents — the Upstream Repository Sync Agent (071) and the Environment & Tooling Team Lead (070) now describe the force-refresh model rather than the old "clean-repository git pull --ff-only, never reset" behaviour.

The result is a re-run you can trust: managed files are refreshed, obsolete ones are pruned by a strict manifest diff, upstream skills stay current, and everything you authored — agents, Fabric content, and business clones — is left exactly as you left it.

Fabric Agentic Workspace – One-Click Setup – v0.6.1

Trust, but verify — now the workspace verifies itself.

This release makes the installer provably correct. A machine-readable JSON Schema (draft-07) now describes the agent manifest, and a full Pester suite validates it on every push: manifest integrity, the 3 / 7 / 37 hierarchy, least-privilege tool scopes, version-and-doc consistency, and a real generator dry-run that emits all 47 agents into a throwaway folder and checks them.

Also in this release:

• GitHub Actions CI runs the suite on every push and pull request.
• Install-time self-test writes guardrail-status.json (structure, hierarchy, least-privilege).
• SHA-256 integrity manifest (installed-manifest.json) + -VerifyRoot drift detection.
• Agents now read the user's intent before choosing local vs live, running the MCP self-test first when the work is clearly in-service.

Fabric Agentic Workspace – One-Click Setup – v0.6.0

Fabric Agentic Workspace – One-Click Setup – v0.6.0

This release turns eight agents into a coordinated organisation.

The workspace is now a 47-agent hierarchy with one clear front door. The Fabric Workspace Master is a strict coordinator — it receives every request, routes it to the owning team, and owns the outcome, but never edits an artifact itself. A specialist worker implements the change and its Team Lead reviews it, so there is always exactly one writer per artifact and one reviewer behind it.

The new structure

• 1 Master coordinator (000) — primary contact, orchestration, final outcome.
• 2 executive reviewers (001/002) — Solution Architect for cross-domain design, Integration QA for cross-artifact validation.
• 7 Team Leads (010–070) — Semantic Model, Reporting, Data Engineering, Administration & Governance, ALM & DevOps, Applications & Integration, and Capability Maintenance.
• 37 delegated workers — each owns a bounded artifact type and reports evidence back to its lead. Leads keep the dropdown compact; workers are delegated, not selected.

Also in this release

Capability Maintenance team — a dedicated team owns vendor-repo refresh, skill inventory and mapping, agent-coverage checks, installer health, tool detection, and approved installs/recovery on locked-down machines.

MCP that actually works — a per-agent tools: allowlist was silently excluding extension-contributed MCP tools. The generator now grants powerbi-modeling-mcp/* or Fabric MCP/* to the 27 agents that need them, VS Code ignores the wildcard where the extension is absent, and the Master runs a startup self-test that verifies the servers are running and falls back to REST/CLI when they are not. MCP availability is now verified, never assumed.

Optional GitHub / Azure DevOps onboarding — the installer can collect repo metadata, branch topology, and write policy into a machine-local repository-map.local.json, then open everything as a multi-root workspace. Business clones stay isolated: cloned once, no pull/reset, dirty folders preserved, no PAT stored, excluded from outer commits.

Honest locked-down installs — Tabular Editor 2 and pbi-tools (whose GitHub-release ZIPs are often blocked by TLS-inspection proxies) now print the exact portable link instead of fetching a broken empty ZIP. Tool updates are reviewed explicitly (Current / Update / Unverified) and confirmed versions are written back to tool-status.json.

Truthful Git and safety boundaries — ownership-scoped commits, honest commit-result messages, transactional portable installs, publisher-verified downloads, and clear README warnings on initial-commit scope and Fabric Git limits.

The result is a workspace that behaves like a real delivery team: one coordinator, clear ownership, deterministic tools, verified MCP, and graceful degradation when a tool or server is missing.

Fabric Agentic Workspace – One-Click Setup – v0.5.1-pre-release

This release makes the workspace properly tool-aware

Every agent now has a bounded purpose, owns a minimum set of deterministic tools, and loads only the skills needed for the current task — no more eager “read everything” behaviour.

The installer now builds a machine-specific tool-status.json inventory covering core tools, MCP servers, and the six optional specialist tools:

• pbir-cli
• Tabular Editor CLI
• pbi-tools
• sqlcmd
• GitHub CLI
• Azure DevOps CLI extension

Agents read the inventory before invoking any CLI or MCP, re-check tools at runtime when needed, and fall back gracefully when something is missing.

Tool availability never changes which specialist receives the task.

Also in this release

• New Fabric DevOps Agent — dedicated coordination for Fabric Git Integration, Deployment Pipelines, Azure DevOps, GitHub, PRs, CI/CD, PBIP workflows, conflicts, and review of text-based Fabric definitions.

• Optional specialist-tool installation — each tool is detected, explained, and installed only after an explicit Y/N confirmation.

• Optional tool update checks — the installer can check installed managed tools for newer published versions and prompt per tool before upgrading. The check is disabled by default so normal runs remain fast.

• Skills Maintainer tool refresh — both maintenance modes can re-detect the current machine and rebuild tool-status.json without installing anything.

• Agent → tools → skills documentation — the README now includes ownership matrices, coverage tables, design principles, startup rules, and graceful-degradation behaviour.

• CLI-FUNCTIONALITIES.md expanded — now includes a provider-sourced practical chapter for every specialist CLI.

• Narrow MCP ownership — Fabric MCP is limited to the Data Engineer and DevOps agents; Power BI semantic-model MCP remains with the Semantic Model and App Development agents.

• Corporate-PC resilience improved — stalled winget downloads now time out, direct downloads force TLS 1.2, dead fallbacks were removed, and failed optional-tool installs point users to the README recovery workflow and ready-to-paste Master-agent prompt.

The result is a more deterministic, maintainable, and corporate-friendly workspace where agents use the right tools when available, stay useful when they are not, and keep context loading tightly controlled.

Fabric Agentic Workspace – One-Click Setup – v0.4.0-pre-release

v0.4.0-pre-release

This release is about how you actually work day-to-day. Three ways of working are now documented end to end:

• Full local (file-first) — edit Fabric items as files, push them back.
• Full live — agents act directly on the running DEV workspace via Fabric REST updateDefinition + MCP: live DAX TEST-vs-PROD comparison, reading real deployed GUIDs/endpoints, in-place edits.
• Hybrid — mix both, guarded by the "keep local = live workspace" golden rule.

All three share the same Azure DevOps commit safety net, so the edit mechanism never changes how a change is promoted.

Also in this release:

• MCP auto-install fixed — the Fabric MCP and Power BI semantic-model MCP servers are now detected via code --list-extensions and auto-installed if missing (no more mcp.json false negatives).
• fab/az CLI + MCP install hardening — more reliable optional-tool installs on corporate/locked-down machines (PATH refresh, idempotent re-runs, resilient az/MCP handling).

Fabric Agentic Workspace – One-Click Setup – v0.3.0-pre-release

v0.3.0-pre-release

fabric-pipelines skill enhanced after real-world usage — added a "Operational practices (battle-tested)" section generalized from production pipeline work

Fabric Agentic Workspace – One-Click Setup – v0.2.0-pre-release

v0.2.0-pre-release

Second pre-release. This one is all about trust and resilience: the agents now survive the upstream skill repos restructuring their folders, the freshness display tells you the truth, and provenance/licensing is documented end to end. The pipeline skill also got a maintainer pass against the latest Microsoft docs.

Fabric Agentic Workspace - Once Click Set Up - v0.1.0-pre-release

Initial pre-release of a one-click installer that scaffolds a complete VS Code Microsoft Fabric agentic development
environment — eight specialist AI agents, custom skills for TMDL and pipeline authoring, and integration with two open-source skill repositories.