fix: increase claude-token-usage-analyzer timeout to 45 minutes

[lpcox]

The Daily Claude Token Usage Analyzer workflow was timing out at 15 minutes (#1838). The agent spends significant time listing workflow runs, downloading token-usage.jsonl artifacts from each run, and compiling the analysis — 15 minutes isn't enough.

Increases timeout-minutes from 15 to 45.

Fixes #1838

[github-actions]

✅ Coverage Check Passed

Overall Coverage

Metric	Base	PR	Delta
Lines	85.85%	85.95%	📈 +0.10%
Statements	85.76%	85.85%	📈 +0.09%
Functions	87.54%	87.54%	➡️ +0.00%
Branches	78.56%	78.61%	📈 +0.05%

📁 Per-file Coverage Changes (1 files)

File	Lines (Before → After)	Statements (Before → After)
src/docker-manager.ts	86.3% → 86.6% (+0.36%)	85.9% → 86.2% (+0.35%)

---

Coverage comparison generated by scripts/ci/compare-coverage.ts

[Copilot]

Pull request overview

This PR aims to prevent the “Daily Claude Token Usage Analyzer” agentic workflow from timing out by increasing the configured timeout from 15 to 45 minutes.

Changes:

• Increase timeout-minutes to 45 in the source workflow definition.
• Regenerate the compiled workflow (*.lock.yml) so the agent execution step uses the longer timeout.
• Update the actions lockfile to include a new github/gh-aw-actions/setup@v0.67.3 entry (via regeneration).

Show a summary per file

File	Description
.github/workflows/claude-token-usage-analyzer.md	Bumps timeout-minutes to 45 in the workflow frontmatter.
.github/workflows/claude-token-usage-analyzer.lock.yml	Reflects the new timeout, but also includes additional regenerated changes (compiler/version/schedule/tool pinning).
.github/aw/actions-lock.json	Adds an entry for github/gh-aw-actions/setup@v0.67.3 due to the regenerated lock workflow.

Copilot's findings

Tip

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

Comments suppressed due to low confidence (2)

.github/workflows/claude-token-usage-analyzer.lock.yml:49

• This change shifts the scheduled cron time ("17 12" → "48 19"). The PR description only mentions increasing the timeout; if the schedule change is unintended, pin an explicit cron in the source .md (instead of relying on the compiler’s "daily (scattered)" time) or recompile without altering the schedule output.

  schedule:
  - cron: "48 19 * * *"
    # Friendly format: daily (scattered)

.github/workflows/claude-token-usage-analyzer.lock.yml:358

• This regeneration pins GitHub Copilot CLI to 1.0.21 and bumps AWF to v0.25.16. Other workflows in this repo currently install Copilot CLI as latest and use the previous AWF version, so this introduces an unadvertised behavioral change beyond the timeout update; either keep these consistent with the rest of the workflows or update the PR scope/description accordingly.

      - name: Install GitHub Copilot CLI
        run: ${RUNNER_TEMP}/gh-aw/actions/install_copilot_cli.sh 1.0.21
        env:
          GH_HOST: github.com
      - name: Install AWF binary
        run: bash ${RUNNER_TEMP}/gh-aw/actions/install_awf_binary.sh v0.25.16
      - name: Determine automatic lockdown mode for GitHub MCP Server

• Files reviewed: 3/3 changed files
• Comments generated: 2

[Copilot]

The workflow lock file was regenerated with gh-aw v0.67.3 (metadata/compiler_version), while the rest of the repo’s workflow lock files are still on v0.67.2. If this PR’s intent is only the timeout bump, consider recompiling with the repo’s current compiler version to avoid pulling in unrelated lockfile churn (dependency/version/behavior changes).

This issue also appears in the following locations of the same file:

• line 47
• line 352

[Copilot]

This adds a new global action-lock entry for github/gh-aw-actions/setup@v0.67.3. If the intent of the PR is only to increase the workflow timeout, consider avoiding a setup action/version bump (or upgrading the repo consistently) to prevent lockfile drift and unrelated changes.