Merge pull request #7 from michaeldeongreen/test

Promote test to main

Author: michaeldeongreen

.env.sample

@@ -0,0 +1,16 @@
+# Copy this file to .env (gitignored) and paste in your feature workspace
+# IDs. The workspace_swap.py bootstrap script reads them so you don't have to
+# type GUIDs at a prompt.
+#
+# Find these in Fabric:
+#   - Workspace ID: open the workspace, gear icon (Workspace settings),
+#     "About" -> "Workspace ID".
+#   - Lakehouse ID: open the lakehouse item, copy the GUID from the URL
+#     (the segment after /lakehouses/), or from the lakehouse details pane.
+#
+# These values are per-developer and per-feature-branch. Once workspace_swap.py
+# bootstraps a branch, the IDs are cached in the value set on disk and the
+# .env file is no longer consulted for that branch.
+
+FEATURE_WORKSPACE_ID=00000000-0000-0000-0000-000000000000
+FEATURE_LAKEHOUSE_ID=00000000-0000-0000-0000-000000000000

.github/copilot-instructions.md

@@ -1,60 +1,61 @@
-# Project Guidelines
-
-## Overview
-
-Reference implementation for CI/CD in Microsoft Fabric. Demonstrates version control, deployment, and environment-specific configuration for Fabric workspace items using GitHub Actions and [fabric-cicd](https://microsoft.github.io/fabric-cicd).
-
-## Project Layout
-
-```
-scripts/              Python CLI scripts (stdlib-only, Python 3.10+)
-tests/                pytest unit tests
-data/fabric/          Fabric item definitions (git-synced from Fabric workspaces)
-.github/workflows/    GitHub Actions CI/CD pipelines
-.github/instructions/ Path-specific Copilot instructions (Python, Actions)
-```
-
-## Build and Test
-
-```bash
-pip install -r requirements-dev.txt
-python -m pytest tests/ -v
-```
-
-No build step — scripts are standalone CLI tools, not an installable package. `pyproject.toml` configures pytest only (`pythonpath = ["scripts"]`).
-
-## Key Scripts
-
-- `scripts/branch_env.py` — Manages feature branch workspace bindings (bootstrap, reset, validate). Uses an **item type registry** pattern — new Fabric item types are added as config entries, not new functions.
-- `scripts/branch_env.py --validate` — CI check for PR readiness (dev IDs present, no stray value sets).
-
-## Fabric Item Types
-
-Items fall into two categories based on how they reference environment resources:
-
-- **Actual IDs** (SemanticModel, Notebook): Embed real workspace/lakehouse GUIDs. Must be rewritten by `branch_env.py` for feature branches and reverted before PR.
-- **Logical IDs** (Ontology, DataAgent): Reference items via `.platform` `logicalId`, resolved by Fabric at runtime. Portable across Branch Out workspaces — no rewriting needed.
-
-## CI/CD Configuration
-
-- `data/fabric/parameter.yml` — Deploy-time `find_replace` rules for fabric-cicd. Maps dev IDs to dynamic placeholders (`$workspace.$id`, `$items.Lakehouse.*.$id`).
-- `data/fabric/Patterns_Variables.VariableLibrary/` — Runtime configuration via value sets (Test, Prod, feature branches).
-
-## Conventions
-
-- Path-specific instructions in `.github/instructions/` govern Python and Actions code style — follow them.
-- Never commit notebook META blocks containing internal metadata (security).
-- Validate GUIDs from external sources before using them.
-- Pin GitHub Actions to commit SHAs, not version tags.
-- All file I/O must specify `encoding="utf-8"`.
-
-## Workflows
-
-| Workflow | Trigger | Purpose |
-|----------|---------|---------|
-| `validate-branch-env.yml` | PR to `dev` | Blocks merge if dev IDs not restored |
-| `run-tests.yml` | PR (any branch) | Runs pytest when scripts/tests change |
-
-## Documentation
-
-See `fabric-development-process.md` for the Branch Out workflow, item type reference table, and step-by-step bootstrap/reset guides. See `fabric-hybrid-cicd-guide.md` for the deployment architecture.
+# Project Guidelines
+
+## Overview
+
+Reference implementation for CI/CD in Microsoft Fabric. Demonstrates version control, deployment, and environment-specific configuration for Fabric workspace items using GitHub Actions and [fabric-cicd](https://microsoft.github.io/fabric-cicd).
+
+## Project Layout
+
+```
+scripts/              Python CLI scripts (stdlib-only, Python 3.10+)
+tests/                pytest unit tests
+data/fabric/          Fabric item definitions (git-synced from Fabric workspaces)
+.github/workflows/    GitHub Actions CI/CD pipelines
+.github/instructions/ Path-specific Copilot instructions (Python, Actions)
+```
+
+## Build and Test
+
+```bash
+pip install -r requirements-dev.txt
+python -m pytest tests/ -v
+```
+
+No build step — scripts are standalone CLI tools, not an installable package. `pyproject.toml` configures pytest only (`pythonpath = ["scripts"]`).
+
+## Key Scripts
+
+- `scripts/workspace_swap.py` — Swaps Fabric workspace IDs in tracked files between dev and a feature workspace, and provides a CI readiness check (`--check-ready`). Uses an **item type registry** pattern — new Fabric item types are added as config entries, not new functions.
+- `scripts/workspace_swap.py --check-ready` — CI check for PR readiness (dev IDs present, no stray value sets).
+
+## Fabric Item Types
+
+Items fall into two categories based on how they reference environment resources:
+
+- **Actual IDs** (SemanticModel, Notebook): Embed real workspace/lakehouse GUIDs. Must be rewritten by `workspace_swap.py` for feature branches and reverted before PR.
+- **Logical IDs** (Ontology, DataAgent): Reference items via `.platform` `logicalId`, resolved by Fabric at runtime. Portable across Branch Out workspaces — no rewriting needed.
+
+## CI/CD Configuration
+
+- `data/fabric/parameter.yml` — Deploy-time `find_replace` rules for fabric-cicd. Maps dev IDs to dynamic placeholders (`$workspace.$id`, `$items.Lakehouse.*.$id`).
+- `data/fabric/Patterns_Variables.VariableLibrary/` — Runtime configuration via value sets (Test, Prod, feature branches).
+
+## Conventions
+
+- Path-specific instructions in `.github/instructions/` govern Python and Actions code style — follow them.
+- Never commit notebook META blocks containing internal metadata (security).
+- Validate GUIDs from external sources before using them.
+- Pin GitHub Actions to commit SHAs, not version tags.
+- All file I/O must specify `encoding="utf-8"`.
+- Local developer config goes in `.env` (gitignored). A committed `.env.sample` documents the expected keys. `scripts/workspace_swap.py` reads feature workspace IDs from `.env` when swapping to a feature workspace.
+
+## Workflows
+
+| Workflow | Trigger | Purpose |
+|----------|---------|---------|
+| `check-pr-ready.yml` | PR to `dev` | Blocks merge if dev IDs not restored |
+| `run-tests.yml` | PR (any branch) | Runs pytest when scripts/tests change |
+
+## Documentation
+
+See `fabric-development-process.md` for the Branch Out workflow, item type reference table, and step-by-step swap-to-feature / swap-to-dev guides. See `fabric-hybrid-cicd-guide.md` for the deployment architecture.

.github/instructions/python.instructions.md

@@ -25,7 +25,8 @@ When generating or improving Python code in this repository:
 
 ## Dependencies
 - Keep scripts stdlib-only when possible; gate optional imports with try/except
-- When external packages are needed, prefer: `requests`, `azure-identity`
+- For environment-specific config in CLI scripts, prefer `.env` files (parsed with stdlib) over external libraries like `python-dotenv`
+- When external packages are unavoidable, justify in the script docstring; add a `>=` minimum bound to the relevant requirements file
 - Never pin to exact versions in scripts; use `>=` minimum bounds in requirements files
 
 ## Security

.github/prompts/check-pr-ready.prompt.md

@@ -0,0 +1,7 @@
+---
+description: Run the CI-style readiness check locally — verifies dev IDs are restored and no stray feature value sets remain.
+mode: agent
+---
+Run `python scripts/workspace_swap.py --check-ready` from the repo root and report the output to me. This is the same check the `check-pr-ready.yml` GitHub Actions workflow runs on every PR to `dev`. It does not modify any files.
+
+If the check fails, the output will tell you which files still contain feature IDs. The fix is usually to run `/swap-to-dev`.

.github/prompts/swap-to-dev-dryrun.prompt.md

@@ -0,0 +1,7 @@
+---
+description: Preview what swap-to-dev would change without writing any files.
+mode: agent
+---
+Run `python scripts/workspace_swap.py --swap-to-dev --dry-run` from the repo root and report the output to me. This is a preview — no files will be modified. Use this before running `/swap-to-dev` to verify the planned revert looks correct.
+
+After the script finishes, summarize what would have been changed.

.github/prompts/swap-to-dev.prompt.md

@@ -0,0 +1,7 @@
+---
+description: Swap the IDs back to dev and remove the feature value set (run before opening a PR).
+mode: agent
+---
+Run `python scripts/workspace_swap.py --swap-to-dev` from the repo root and report the output to me. The script will revert tracked Fabric files (semantic model, notebooks) back to the dev workspace IDs, delete the feature value set for the current branch, and remove the feature entry from settings.json. It reads the feature IDs from the existing value set on disk — `.env` is not consulted.
+
+After the script finishes, summarize what changed and remind me to commit and push the changes before opening a PR to `dev`.

.github/prompts/swap-to-feature-dryrun.prompt.md

@@ -0,0 +1,7 @@
+---
+description: Preview what swap-to-feature would change without writing any files.
+mode: agent
+---
+Run `python scripts/workspace_swap.py --dry-run` from the repo root and report the output to me. This is a preview — no files will be modified. Use this before running `/swap-to-feature` to verify the planned changes look correct.
+
+After the script finishes, summarize what would have been changed.

.github/prompts/swap-to-feature.prompt.md

@@ -0,0 +1,7 @@
+---
+description: Swap the repo's IDs to your feature workspace and create the value set for the current branch.
+mode: agent
+---
+Run `python scripts/workspace_swap.py` from the repo root and report the output to me. The script will rewrite tracked Fabric files (semantic model, notebooks) so they point at your feature workspace instead of dev, create a feature value set, and update settings.json. It reads the feature workspace and lakehouse GUIDs from `.env` at the repo root — if `.env` is missing or empty, it will fall back to an interactive prompt.
+
+After the script finishes, summarize what changed and remind me to commit and push the changes, then sync the workspace from the Fabric UI.

.github/workflows/validate-branch-env.yml .github/workflows/check-pr-ready.yml.github/workflows/validate-branch-env.yml renamed to .github/workflows/check-pr-ready.yml

@@ -1,4 +1,4 @@
-name: Validate Branch Environment
+name: Check PR Ready
 
 on:
   pull_request:
@@ -9,7 +9,7 @@ permissions:
   contents: read
 
 jobs:
-  validate-branch-env:
+  check-pr-ready:
     name: Check for non-dev IDs in Fabric items
     runs-on: ubuntu-latest
     timeout-minutes: 5
@@ -23,5 +23,5 @@ jobs:
         with:
           python-version: "3.12"
 
-      - name: Validate branch environment
-        run: python scripts/branch_env.py --validate
+      - name: Check PR ready
+        run: python scripts/workspace_swap.py --check-ready

.gitignore

@@ -1 +1,9 @@
 *.pyc
+__pycache__/
+
+# Python virtual environments
+.venv/
+venv/
+
+# Local developer config (copied from .env.sample)
+.env