Implement Stage A: rule engine, validation, audit, and safety gates

Completes 109 of 121 tasks. Every remaining task needs a tenant connection
(T055, T056, T101-T103) or an Azure Automation account (T115-T121).

  354 offline Pester tests      PASS
  Engine purity (Principle IV)  PASS
  Sanitization (SC-013)         PASS  (156 files)
  Graph module loaded in tests  none  (SC-008 holds)

What landed
  - Four-layer configuration validation with stable finding codes, covering
    every VR-002 and VR-003 condition, plus a 23-fixture invalid-config corpus
  - Run loop, audit records (NDJSON through a single sink), summaries,
    reconciliation, and exit codes 0-6
  - Persistence behind a single write-body builder whose result always has
    exactly one key
  - Invoke-PersonaEngine.ps1 and Edit-PersonaEngineConfig.ps1
  - Six docs, two pipelines, traceability matrix, V-5a and sanitization records

Three deviations from tasks.md, each recorded in its status block

  T033 is not in Resolve-UserPersona. evaluationErrorThreshold is run-level
  state and the rule engine is pure; a counter there would break Principle IV.
  It lives in New-PersonaRunCounter and is applied in the run loop.

  A new src/Engine/ layer holds Invoke-PersonaEngineRun. The entry script
  imports the manifest, which requires Microsoft.Graph.Authentication, so a
  loop living only inside it could not run on a machine without the Graph SDK
  and SC-004 could not be proven at all. The entry script is now a thin
  wrapper and what ships is what is tested.

  The invalid-config corpus is generated by a committed script, with the
  generated fixtures committed too, so a reviewer sees the fixture in the diff.

Defects found by running the code, not by reading it

  Group and role ID lists were double-wrapped: @(Get-PersonaGroupIdPage ...)
  around a comma-returned array collapsed every membership list into one
  bogus space-joined entry. That is a silent false non-match, exactly what
  FR-013 exists to prevent.

  A 403 whose status appears only in the exception message parsed as $null,
  which the retry policy treats as a transport error - five requests per
  account against a tenant already refusing. Status extraction now falls back
  to the message text, bounded to 400-599.

  The sanitization scan walked tracked files only, so it covered 34 of 156
  files and none of this phase's code. It now scans untracked non-ignored
  files too, and a negative control confirms it catches a planted leak.

  Test-Json reports one error per violating location, not first-failure-only
  as the V-5a draft claimed. Record and pin corrected.

Enforcement remains blocked on the V-4 security sign-off.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/Configuration/NonInteractive.Tests.ps1

@@ -0,0 +1,124 @@
+#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '5.0.0' }
+
+<#
+    SC-010: -NonInteractive never prompts and never hangs.
+
+    Each case runs the editor in a child pwsh with stdin redirected from an empty
+    file, which is what a build agent gives it. A tool that prompts there does not
+    fail - it blocks until the job times out, and the pipeline reports an
+    infrastructure problem rather than a bad configuration.
+
+    A wall-clock timeout is the assertion. That makes these the slowest tests in the
+    suite, and there is no cheaper way to prove the absence of a hang: inspecting the
+    source for Read-Host would only prove that one spelling of prompting is absent.
+#>
+
+BeforeAll {
+    $repoRoot = Split-Path (Split-Path $PSScriptRoot -Parent) -Parent
+    . (Join-Path $repoRoot 'tests/TestHelpers.ps1')
+
+    $script:editor = Join-Path $repoRoot 'Edit-PersonaEngineConfig.ps1'
+    $script:scratch = Join-Path ([System.IO.Path]::GetTempPath()) ("pe-ni-{0}" -f [guid]::NewGuid().ToString('N'))
+    $null = New-Item -ItemType Directory -Path $script:scratch -Force
+
+    $script:emptyStdin = Join-Path $script:scratch 'empty.txt'
+    Set-Content -LiteralPath $script:emptyStdin -Value '' -NoNewline
+
+    function Invoke-EditorWithClosedStdin {
+        <#
+            Runs the editor with stdin from an empty file and a hard timeout.
+            Returns the exit code, or -1 if it had to be killed.
+        #>
+        param(
+            [string[]] $ArgumentList,
+            [int] $TimeoutSeconds = 60
+        )
+
+        $stdout = Join-Path $script:scratch ("out-{0}.txt" -f [guid]::NewGuid().ToString('N'))
+        $stderr = Join-Path $script:scratch ("err-{0}.txt" -f [guid]::NewGuid().ToString('N'))
+
+        $process = Start-Process -FilePath (Get-Process -Id $PID).Path `
+            -ArgumentList (@('-NoProfile', '-NonInteractive', '-File', $script:editor) + $ArgumentList) `
+            -RedirectStandardInput $script:emptyStdin `
+            -RedirectStandardOutput $stdout `
+            -RedirectStandardError $stderr `
+            -PassThru -WindowStyle Hidden
+
+        if (-not $process.WaitForExit($TimeoutSeconds * 1000)) {
+            $process.Kill($true)
+            return [pscustomobject]@{ ExitCode = -1; Output = 'TIMED OUT'; TimedOut = $true }
+        }
+
+        [pscustomobject]@{
+            ExitCode = $process.ExitCode
+            Output   = (Get-Content -LiteralPath $stdout -Raw -ErrorAction SilentlyContinue)
+            Error    = (Get-Content -LiteralPath $stderr -Raw -ErrorAction SilentlyContinue)
+            TimedOut = $false
+        }
+    }
+}
+
+AfterAll {
+    Remove-Item -LiteralPath $script:scratch -Recurse -Force -ErrorAction SilentlyContinue
+}
+
+Describe 'Non-interactive mode never prompts or hangs (SC-010)' {
+
+    It 'completes on a valid configuration with stdin closed' {
+        $path = Save-TestConfiguration -Document (New-TestConfigurationDocument) -Directory $script:scratch
+
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @('-ConfigPath', $path, '-ValidateOnly', '-NonInteractive')
+
+        $run.TimedOut | Should -BeFalse
+        $run.ExitCode | Should -Be 0
+    }
+
+    It 'completes on an invalid configuration with stdin closed' {
+        $document = New-TestConfigurationDocument
+        $document.rules[1].id = $document.rules[0].id
+
+        $path = Save-TestConfiguration -Document $document -Directory $script:scratch
+
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @('-ConfigPath', $path, '-ValidateOnly', '-NonInteractive')
+
+        $run.TimedOut | Should -BeFalse
+        $run.ExitCode | Should -Be 1
+    }
+
+    It 'completes with -NonInteractive alone, without -ValidateOnly' {
+        # The case most likely to regress: -NonInteractive must short-circuit before
+        # the editor loop even when the caller did not also ask for validate-only.
+        $path = Save-TestConfiguration -Document (New-TestConfigurationDocument) -Directory $script:scratch
+
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @('-ConfigPath', $path, '-NonInteractive')
+
+        $run.TimedOut | Should -BeFalse
+        $run.ExitCode | Should -Be 0
+    }
+
+    It 'completes when the configuration file does not exist' {
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @('-ConfigPath', (Join-Path $script:scratch 'absent.json'), '-NonInteractive')
+
+        $run.TimedOut | Should -BeFalse
+        $run.ExitCode | Should -Be 3
+    }
+
+    It 'completes when running synthetic rule tests' {
+        $path = Save-TestConfiguration -Document (New-TestConfigurationDocument) -Directory $script:scratch
+
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @(
+            '-ConfigPath', $path, '-NonInteractive', '-TestDataPath', (Join-Path $repoRoot 'tests/TestData'))
+
+        $run.TimedOut | Should -BeFalse
+        $run.ExitCode | Should -Be 0
+    }
+
+    It 'emits no prompt text on the output stream' {
+        $path = Save-TestConfiguration -Document (New-TestConfigurationDocument) -Directory $script:scratch
+
+        $run = Invoke-EditorWithClosedStdin -ArgumentList @('-ConfigPath', $path, '-NonInteractive')
+
+        $run.Output | Should -Not -Match 'Choice'
+        $run.Output | Should -Not -Match 'configuration editor'
+    }
+}