CI: all Jules workflows fail in setup — jules-action@v1 does not exist (upstream has no v1 tag) #258

Problem

Every Jules workflow in this repo fails during job setup, before any step runs, because the action ref they use does not exist:

##[error]Unable to resolve action `google-labs-code/jules-action@v1`, unable to find version `v1`

Upstream google-labs-code/jules-action publishes only these tags (verified 2026-10-18 via the GitHub API): v1.0.0, v0.0.1, ai-assisted. There is no moving v1 tag, so @v1 can never resolve.

Evidence

All six uses: sites pin the nonexistent ref:

• .github/workflows/jules.yml:47 (weekly-cleanup)
• .github/workflows/jules.yml:64 (issue-labeled)
• .github/workflows/jules.yml:80 (ci-failure-fix)
• .github/workflows/jules.yml:95 (manual)
• .github/workflows/jules-daily-codebase-ideation.yml:36
• .github/workflows/jules-daily-flake-sync.yml:36

Failing runs with the exact error above in --log-failed:

• Jules run 39105615200 (2026-10-18, ci-failure-fix job) — of the last 50 Jules workflow runs, 14 concluded failure and the rest skipped; every executed job failed this way.
• Jules Daily Codebase Innovation & Maintenance run 39023614469 (2026-10-17) — the workflow's only run so far.
• Jules Daily Flake Sync & Config Optimization run 39019503186 (2026-10-17) — the workflow's only run so far.

This is not tracked anywhere: a search for jules-action / the error text finds only Renovate's Dependency Dashboard (#24), which merely lists the dependency as v1 and does not flag that the ref does not resolve.

Why it matters

All Jules automation is dead on arrival: the weekly cleanup, the jules-label issue handler, the CI-failure auto-fix job, the manual dispatch, and both daily workflows have never successfully invoked Jules from this repo. The CI-failure job is the costly one — it fires precisely when another workflow has already failed, and then fails itself in setup, adding noise runs (14 in ~1 day) on top of the real failure.

The header comment in jules.yml (lines 14–16) notes upstream's README still references the old jules-invoke@v1 name; the rename to jules-action was handled, but the @v1 ref was carried over without checking that a v1 tag exists under the new name.

Suggested fix

Pin every site to a ref that exists — @v1.0.0 (or a full commit SHA of that tag, if the repo prefers immutable pins for third-party actions).

Acceptance criteria

• All six uses: google-labs-code/jules-action@… sites reference a tag/SHA that exists upstream (no @v1 remains).
• A workflow_dispatch of the Jules workflow (or one of the daily workflows) gets past action resolution and actually reaches the Jules step — any subsequent failure is about JULES_API_KEY / GitHub App authorisation, not about resolving the action.
• The next scheduled daily Jules run no longer fails in job setup with "Unable to resolve action".