Smoke test workspace_swap + chat-driven confirmation in prompt (#35)

* Swap to feature workspace + chat-driven confirmation in prompt

Test of the updated swap-to-feature.prompt.md flow that moves the YES
confirmation into the chat UI instead of a live terminal prompt.

scripts/workspace_swap.py output for branch swap-file-smoke-test:
- New per-branch value set: Patterns_Variables.VariableLibrary/valueSets/
  swap-file-smoke-test.json
- settings.json valueSetsOrder updated
- Patterns_Semantic_Model.SemanticModel: Direct Lake URL repointed to
  feature workspace + lakehouse
- Import_Patterns_Data.Notebook: META block lakehouse dependency
  repointed to feature workspace + lakehouse

.github/prompts/swap-to-feature.prompt.md updated to instruct the agent
to ask for confirmation in the chat UI (vscode_askQuestions) and then
pipe YES into the script (echo "YES" | python ...) so the terminal
never blocks on the script's interactive Confirm: prompt.

* Swap back to dev for PR readiness

Reverts the swap-file-smoke-test branch to dev IDs ahead of opening
the PR to dev. The check-pr-ready CI workflow enforces this — feature
IDs in tracked Fabric files would block the merge.

Reverted by scripts/workspace_swap.py --swap-to-dev:
- Patterns_Semantic_Model.SemanticModel/definition/expressions.tmdl
  (Direct Lake URL: feature → dev)
- Import_Patterns_Data.Notebook/notebook-content.py
  (META block: feature → dev)
- Patterns_Variables.VariableLibrary/valueSets/swap-file-smoke-test.json
  (deleted — per-branch value set no longer needed)
- Patterns_Variables.VariableLibrary/settings.json
  (swap-file-smoke-test removed from valueSetsOrder)

Author: michaeldeongreen

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

@@ -2,6 +2,15 @@
 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.
+The script `scripts/workspace_swap.py` rewrites tracked Fabric files (semantic model, notebooks) so they point at your feature workspace instead of dev, creates a feature value set, and updates settings.json. It reads `FEATURE_WORKSPACE_ID` and `FEATURE_LAKEHOUSE_ID` from `.env` at the repo root and asks for a `YES` confirmation before applying. When invoked through this prompt, that confirmation must happen here in chat — never in the terminal — to avoid live-prompt handling problems.
 
-After the script finishes, summarize what changed and remind me to commit and push the changes, then sync the workspace from the Fabric UI.
+Follow this exact sequence:
+
+1. Read `.env` at the repo root and read the dev workspace + lakehouse IDs from `data/fabric/Patterns_Variables.VariableLibrary/variables.json`.
+2. Show me the planned swap in chat (current branch, dev → feature workspace ID, dev → feature lakehouse ID).
+3. Use the chat UI to ask me a single question with two options: `YES` and `NO` (uppercase, exact). Do not proceed until I answer.
+4. If I answer `YES`, run `echo "YES" | python scripts/workspace_swap.py`. The piped `YES` satisfies the script's confirmation gate non-interactively, so the terminal never blocks. Report the full output.
+5. If I answer `NO`, do nothing further and confirm in chat that the swap was not applied.
+6. After a successful run only, summarize what changed and remind me to commit and push the changes, then sync the workspace from the Fabric UI.
+
+Do not run the script directly without piping `YES` (it will block on the terminal prompt). Do not skip the chat confirmation — the in-script confirmation is bypassed by the pipe and the chat dialog is the gate.