session-log-fixer

To fix session protocol validation failures, you must patch non-compliant session logs by locating missing MUST/SHOULD sections in the Job Summary and applying canonical templates from SESSION-PROTOCOL.md. This produces a COMPLIANT log with explicit evidence and traceable commits for CI re-runs.

Your GitHub Actions run fails session protocol checks because the session logs are NON_COMPLIANT, lacking required MUST/SHOULD sections like Session Start or Session End. Detecting these missing sections in the failed Run summaries allows targeted patching to restore canonical compliance.

Yes, you can target a specific GitHub Actions run-id to patch non-compliant session logs by triggering the fix with a natural-language command like "fix session validation for PR". This applies deterministic corrections to the specified run's artifacts.

You verify patched session logs meet canonical protocol requirements by using the local Validate-SessionProtocol.ps1 workflow. This validation checks that the applied templates from SESSION-PROTOCOL.md have successfully restored the session file to a COMPLIANT state.

The best way to automate remediation for failed session protocol validations is to apply deterministic corrections to non-compliant logs using canonical templates. This process commits traceable changes directly to enable clear artifact reports and immediate CI re-runs without manual intervention.

No, fixing GitHub Actions session logs does not require external dependencies. The process relies on local scripts and canonical reference templates to read failed Run summaries, apply patches, and verify compliance using the Validate-SessionProtocol.ps1 workflow.