Skip to content

fleet: pilot: first Jules schedule — weekly GitHub Actions version-bump sweep on developing-today/code (from #2020) #2265

New issue
New issue
Closed
Closed
fleet: pilot: first Jules schedule — weekly GitHub Actions version-bump sweep on developing-today/code (from #2020)#2265
Assignees
dezren39
Labels
priority/highImportant and time-sensitive

Description

@dezren39
dezren39
opened on Oct 29, 2026

From the #2020 investigation (Jules scheduled tasks)

Investigation #2020 (queue task 3339, result posted on that issue 2026-10-29) produced the Jules fit matrix and a proposed first schedule. This issue is that pilot, scoped to exactly what the investigation proposed — no expansion without the 2-week review.

Pilot

  1. Create one Jules schedule on the fleet's collected Jules account: weekly (Monday, early UTC) GitHub Actions version-bump sweep on developing-today/code — check .github/workflows/ for actions pinned to superseded majors; open at most one PR with per-action changelog links and breaking-change flags; never change workflow permissions, triggers, or secrets references; open nothing when nothing is outdated.
    • Blocker, stated plainly: schedule creation happens in the Jules web UI under Drew's Google account. Whoever executes this needs that browser session; any Google sign-in challenge goes to Drew immediately (standing rule) — it is a step, not a dead end. If no session is available, record the exact prompt + settings as ready-to-create in the registry (step 2) and block this issue on the session rather than improvising another creation path.
  2. Register the schedule in the fleet schedule registry (alongside the cron inventory / placement docs): repo, cadence, prompt verbatim, budget expectation, creation date, kill criteria.
  3. Report the first run on this issue: what Jules opened (or correctly didn't), reviewer time spent, any breakage.

Review gate (2 weeks after creation)

Pass = PRs correct/mergeable with at most trivial edits, zero attributable workflow breakage, reviewer time < 10 min/PR → propose schedule #2 (docs-drift, one repo) as a new issue. Fail = pause the schedule, record why; conclusion "Jules = ad-hoc only" is an acceptable pilot outcome.

Out of scope

Suggested Tasks (stays off), issue-driven Jules work, additional repos/accounts, any auto-merge of Jules PRs.

Program: fleet expansion & placement, epic #2055. Parent investigation: #2020. Related: #2019 (OpenCode scheduled tasks), #2024 (placement synthesis).

Activity

  1. dezren39
    added
    status/needs-triageNot yet triaged; needs a first look
    priority/highImportant and time-sensitive
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Oct 29, 2026

  2. developing-today commented on Oct 29, 2026

    @developing-today
    developing-todayBot
    on Oct 29, 2026 – with developing.today
    Contributor

    CODE-1128

  3. dezren39
    added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Oct 29, 2026
  4. github-actions
    assigned
    dezren39
    on Oct 29, 2026
  5. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 30, 2026

  6. dezren39 commented on Oct 30, 2026

    @dezren39
    dezren39
    on Oct 30, 2026
    MemberAuthor

    🤖 Agent note · picked up

  7. dezren39 commented on Oct 30, 2026

    @dezren39
    dezren39
    on Oct 30, 2026
    MemberAuthor

    🤖 Agent note · escalated

    • Agent: queue worker (repo-worker-code), Lane E shift
    • Session / ID: queue task 3419
    • Found via: queue claim
    • Task: Triage fleet: pilot: first Jules schedule — weekly GitHub Actions version-bump sweep on developing-today/code (from #2020) #2265 — complete as prepared + blocked on Drew, exactly the fallback the issue specifies. Everything creatable without the Jules session is done:
      • Spec verified against current .github/workflows/ (25 workflow files; live pins include actions/checkout@v7, setup-go/setup-node/setup-python@v7, upload-artifact@v7, download-artifact@v8, github-script@v7, goreleaser-action@v7, SHA-pinned DeterminateSystems/deno/bun actions — full snapshot in the registry).
      • Registry entry created: hidden_files/fleet-schedule-registry.md (this goal) entry 1 — repo, cadence (weekly, Monday 04:00 UTC), the finalized prompt verbatim, settings (Suggested Tasks off, no auto-merge, max 1 PR/run), budget expectation, and the 2-week kill criteria from this issue.
      • What Drew needs to do (the one blocking step): open the Jules web UI in a browser signed in to the collected Jules/Google account and create one schedule with the registry's prompt + settings. Any Google sign-in challenge is part of this step. After creation, note the date on the registry entry; the first Monday run then gets its report on this issue.
      • No other creation path was improvised (per the issue: block on the session rather than inventing one). No Jules schedule exists yet, so there is no first run to report — that acceptance item stays open with the block.
    • Expectation: blocked until Drew creates the schedule (minutes in the Jules UI with the prepared prompt); task 3419 blocked with reason class escalated-to-user.
    • Links: parent investigation investigate: Jules scheduled tasks — what fits, and how Muse manages the schedule #2020 · epic epic: fleet expansion & placement program (2026-10-28 directive, LIST 1–5) #2055
  8. dezren39
    added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    user/escalatedQueue or user escalation state
    and removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Oct 30, 2026

  9. dezren39 commented on Oct 30, 2026

    @dezren39
    dezren39
    on Oct 30, 2026
    MemberAuthor

    agent-note:v1 — CLOSED as moot (wont_do). Drew (2026-10-30): the fleet is moving off Jules altogether, so this schedule will not be created. The earlier blocked-on-Drew escalation was wrong on a second count too: the fleet holds Jules API token access, so schedule creation was never Drew-only — the lane should not have parked it as needing his browser session. Queue task 3419 completed with outcome wont_do; the fleet-schedule-registry entry is marked retired.

  10. dezren39
    removed
    status/blockedQueue or user escalation state
    user/escalatedQueue or user escalation state
    queue/blockedQueue or user escalation state
    on Oct 30, 2026
  11. dezren39
    closed this as completedon Oct 30, 2026

  12. dezren39 commented on Oct 30, 2026

    @dezren39
    dezren39
    on Oct 30, 2026
    MemberAuthor

    Agent note — verified already done (queue task 3419, Lane C shift)

    Re-claimed 3419 and revalidated fresh: issue #2265 is CLOSED (2026-10-30T12:08Z). The earlier Lane E pass did the prepared-work, and Drew then closed the pilot as moot — the fleet is moving off Jules altogether, so the schedule will not be created; the registry entry is marked retired. Nothing remains to do and no new work was created. Completing 3419 with outcome already_done on that evidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority/highImportant and time-sensitive

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions