# Validation Workflow

Choose the lightest command that still proves the change.

## 1. Always build after code changes

```powershell
dotnet build Tornado3_2026Election.slnx
```

## 2. Run scoped live validation for a cut or template

Use the local wrapper when Karisma and `D:\Elect2026\T3_Cut` are available. The root is fixed; do not pass a custom image root.

```powershell
powershell -ExecutionPolicy Bypass -File plugins/cut-design-debugger/skills/cut-design-debugger/scripts/validate-cut.ps1 `
  -Filter '1-2위_ani_광역단체장'
```

Useful flags:

- `-Limit 1`: validate only the first matching item.
- `-IncludeVideoWall`: include VideoWall templates.
- `-OutputPath <dir>`: write reports to a custom artifact directory.

## 3. Capture a scene image without running the full live pass

Use this when the problem is visual and you already know the exact `.tscn` scene path.

```powershell
dotnet run --project tools/KarismaTcpProbe/KarismaTcpProbe.csproj -- `
  --save-scene-image `
  --scene 'D:\Elect2026\T3_Cut\SomeScene.tscn' `
  --output artifacts\scene-captures\some-scene.png
```

## 4. Validate scene operations against a fixture

Use this when the issue is about values, visibility, or style updates for known scene objects.

```powershell
dotnet run --project tools/KarismaTcpProbe/KarismaTcpProbe.csproj -- `
  --validate-scene-values `
  --scene 'D:\Elect2026\T3_Cut\SomeScene.tscn' `
  --operations tools/KarismaTcpProbe/scene-ops/1-2위_ani_광역단체장_style.json `
  --output artifacts\scene-validation\style.md
```

## 5. Inspect a whole folder when the object names are unclear

```powershell
dotnet run --project tools/KarismaTcpProbe/KarismaTcpProbe.csproj -- `
  --inspect-tscn-folder `
  --output artifacts\scene-inspection\inspection.md
```
