fix: use floating point for PRU computation in extractPremiumRequestCount

[Copilot]

Models like gemini-3-flash-preview consume fractional PRU (e.g. 0.33 per request), but the log parser was always reporting 1 because the regex only matched integers and parseInt was used.

Changes

• parse_copilot_log.cjs: Updated all three regex patterns from \d+ → \d+(?:\.\d+)? and replaced parseInt with parseFloat
• parse_copilot_log.test.cjs: Added test cases covering decimal PRU values (0.33, 0.5) across all supported log format variants

// Before
const patterns = [/premium\s+requests?\s+consumed:?\s*(\d+)/i, ...];
const count = parseInt(match[1], 10);  // "0.33" → NaN → falls through to default of 1

// After
const patterns = [/premium\s+requests?\s+consumed:?\s*(\d+(?:\.\d+)?)/i, ...];
const count = parseFloat(match[1]);  // "0.33" → 0.33

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[Copilot]

Pull request overview

Updates the Copilot log parser to correctly extract fractional premium request units (PRU) from CLI output, instead of defaulting to 1 when decimals are present.

Changes:

• Broadened premium request regexes to match both integers and decimals.
• Switched parsing from parseInt to parseFloat for matched PRU values.
• Added test coverage for decimal PRU values across all supported log format variants.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
actions/setup/js/parse_copilot_log.cjs	Allows extracting decimal premium request consumption values by matching and parsing floating-point numbers.
actions/setup/js/parse_copilot_log.test.cjs	Adds unit tests validating decimal parsing for each supported log message format.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.