pbip-workflowlisted

# PBIP Workflow Power BI's default `.pbix` is a binary zip — opaque to git, impossible to diff or merge, and it bloats history. The **Power BI Project (PBIP)** format saves the same work as folders of plain text, so your semantic model and report become reviewable code. This skill owns Seshat's PBIP version-control and adoption delta. It is not a native report or semantic-model authoring implementation: when execution is authorized and discoverable, route report mechanics to Microsoft's official `powerbi-report-authoring` skill and semantic-model mechanics to Microsoft's authoring/Modeling MCP surfaces through `powerbi-workflows`. > PBIP is a **preview feature** (per Microsoft docs as of 2025-12). It can change. > Verify specifics against the current docs: > https://learn.microsoft.com/power-bi/developer/projects/projects-overview ## When this matters The whole reason to use PBIP is that **the semantic model becomes code**. Tables, relationships, and especially **DAX measures** are saved as TMDL (Tabular Model Definition Language) text — so "who changed the Gross Margin measure and why" is answerable from `git log`, and a teammate can review a measure change in a pull request the same way they'd review a function. Treat the model with the same care as source code. ## Adopt an existing PBIP into Seshat BI When the analyst already has a PBIP project, start with the governed, read-only intake rather than treating its report pages or measures as readiness evidence: ```powe