v0.86.2 produces different failure-issue expiry values on Windows and Linux

[robinmam]

Description

Compiling the same agentic workflow with gh-aw v0.86.2 produces platform-dependent lockfile output for GH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURS.

• Windows emits "168".
• Linux emits the canonical "0" when no workflow enforces failure-issue expiry.

This causes lockfile verification to fail in Linux CI after a contributor regenerates and commits the lockfile on Windows.

Reproduction

1. Use a repository with no aw.json or agentics-maintenance.yml, and a workflow with safe-outputs.report-failure-as-issue: false.
2. Run gh aw compile --strict with v0.86.2 on Windows.
3. Run the same command at the same revision with v0.86.2 on Linux.
4. Compare the generated lockfile.

Observed difference:

- GH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURS: "168"
+ GH_AW_ACTION_FAILURE_ISSUE_EXPIRES_HOURS: "0"

Expected behaviour

The pinned compiler should produce byte-identical lockfiles on Windows and Linux. In this configuration both platforms should emit "0".