Add explicit debug boolean input to always enable debug logs

[warp-agent-staging]

Summary

Adds an explicit debug boolean input to the Oz Agent GitHub Action so users can always enable Oz debug logging, independent of GitHub's step-debug signal.

Previously, the action enabled --debug only when GitHub requested it (via core.isDebug(), which reflects the runner's step-debug signal). This adds a new debug input (default false) and enables debug logging when debug is true OR core.isDebug() is true — purely additive, preserving the existing GitHub-requested-debug behavior.

• action.yml: new debug boolean input (default false)
• src/index.ts: read core.getBooleanInput('debug'); pass --debug when debug || core.isDebug()
• src/index.test.ts: 4 new regression tests covering all combinations of the debug input and core.isDebug() (see Verification)
• README.md: new "Debug Logging" section documenting the input
• dist/index.js + dist/index.js.map: rebuilt bundle (this repo ships a compiled dist/)
• package-lock.json: repair pre-existing lockfile drift (from the CVE-2026-13149 fix in fix: update brace-expansion to resolve CVE-2026-13149 #39) that broke npm ci on main and on this branch — see Rework changes below

Verification

This is a headless GitHub Action change (no UI), verified in code per the repo's documented checks.

Regression tests (src/index.test.ts, 4 new — 27 total passing):

• omits --debug when debug is false and GitHub step-debug is off — baseline behavior preserved
• adds --debug when the debug input is true even without GitHub step-debug — the new behavior (this test fails before the fix: old if (core.isDebug()) returned false → no --debug)
• still adds --debug from GitHub step-debug when the debug input is false — existing GitHub-requested-debug behavior preserved
• adds --debug exactly once when both debug input and GitHub step-debug are on — no duplicate flag

Repo checks (all passing on Node 24.4.0, the version pinned in .node-version and used by CI):

• npm ci → clean install, 333 packages
• npm test → 27 passed (23 baseline + 4 new)
• npm run lint → clean
• npm run format:check → clean
• npm run build → dist/ and generated workflows unchanged (check-dist clean)

Rework changes

Rework cycle 1 — addressed the code-review finding that all four required CI jobs failed at npm ci.

• 🚨 CRITICAL (package-lock.json): npm ci fails on Node 24 — fixed. The lockfile was missing the top-level @emnapi/core@1.11.3 and @emnapi/runtime@1.11.3 entries (optional peers of @napi-rs/wasm-runtime), so npm ci aborted with EUSAGE … Missing: @emnapi/core@1.11.3 from lock file. This drift is pre-existing on main (introduced by the hand-edited lockfile in fix: update brace-expansion to resolve CVE-2026-13149 #39); the earlier partial patch on this branch fixed only @emnapi/wasi-threads. The lockfile was regenerated in full with npm install --package-lock-only using the repo's pinned toolchain (Node 24.4.0 / npm 11.4.2), which adds the two missing packages and reconciles stale peer markers. No dependency versions changed beyond those additions.
• Re-ran the complete documented gate on Node 24.4.0 after the fix: npm ci, npm run format:check, npm run lint, npm test (27 passed), npm run build (no diff in dist/, .github/workflows/, or consumer-workflows/). All four required CI jobs are green on the PR.

Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1784974804290319