Use PowerShell Safely v0.3.6

Use PowerShell Safely v0.3.6

This release includes the accepted changes since v0.3.4. The 0.3.5 source and managed-install checkpoint was retained but not released separately.

Changes

• Clarifies JSON timestamp handling: preserve original text, inspect the parser result type, use ConvertFrom-Json -DateKind only when the running PowerShell supports it, and compare intervals on a common time basis with explicit offset and endpoint rules.
• Simplifies the Skill entrypoint by pointing to the existing Runtime Readiness procedure in the same package. PowerShell 5.1/7 capability checks, authorization, native process results, encoding, path, permissions and WSL boundaries remain in their existing owners.

Package and verification

• Five-file package tree: 3e5e3f6463ad582e1279a94e27c36b07225127e2.
• SOURCE contract: 14/14 checks passed. Repository/provenance: 44 mapped files passed. Focused boundary checker: 59 assertions passed on PowerShell 7 and 59 on Windows PowerShell 5.1. Metadata validation and disposable managed lifecycle self-test passed.
• The local MANAGED 0.3.6 copy matched all five source files. Its ACL postflight showed the same owner, control fields and allow-ACE multiset on all nine checked nodes; Windows reordered inherited ACEs on eight nodes, so exact SDDL text was not identical there. The retained 0.3.5 rollback dry run passed.

Source and local installation checks do not establish fresh-task loading, natural model adherence, model qualification, or untested host/runtime behavior. See State and Verification in the repository for the evidence boundaries and retained history.