Skip to content

Devkit pin updates can be starved by Renovate's three-PR limit #418

Open

Description

@shiny-code-app

Problem

On November 9, 2026, odoo-tenant-cm had exactly three open Renovate PRs, which is the prConcurrentLimit in renovate/default.json. All three needed a newer devkit pin before their previews could serve, and Renovate opened no pin PR after #415 landed. The pin went in by hand as cbusillo/odoo-tenant-cm#389.

The link between the limit and the missing PR is inferred from the count. Renovate's own logs were not read.

Finish Line

  • A devkit pin update can open while the product repository is at its Renovate PR limit.

Current Status

State: Blocked before Mend. The catalog Chrome route lists no connected browser, so MEND418-1111 could not open the signed-in Mend session. The Renovate skip cause is still unknown and no config fix is chosen.
Next actor: agent:supervisor
Next action: Ask the Director to sign the Claude extension in the Agents Chrome profile in to the catalog's pinned Claude account, confirm list_connected_browsers shows it, then relaunch the bounded log read.

MEND418-1111's handoff has the exact tool replies. The earlier Mend platform-selector read stays as recorded.

Removed: nothing.
Net lines: 0.

Activity

  1. shiny-code-app commented on Nov 9, 2026

    @shiny-code-app
    ContributorAuthor

    Claimed by DK418-PIN-SCHEDULING-1109

    Session: 01a1c29f-319b-7f92-8c82-21b8d65148db
    Branch: work/dk418-pin-scheduling-1109
    Claimed at: 2026-11-09T18:24:20-05:00
    Next action: Read hosted Renovate logs and effective CM pin routing to prove the cause before choosing a source change

    Admission: milestone; https://github.com/cbusillo/direction/issues/5

    Work record

  2. shiny-code-app commented on Nov 9, 2026

    @shiny-code-app
    ContributorAuthor

    Released claim 6754209288

    DK418-PIN-SCHEDULING-1109 finite read-only handoff. Goal remains unproved; no source correction chosen. Current Status on #418 contains evidence and a bounded GUI read brief for the lead agent:01a1a78b-2c93-7c91-af85-11d5396a26d1.

    The documented hosted job log requires a Mend session. Public read returned HTTP200 portal shell, success=false/userSession=null; Computer Use tools absent and no documented credential inventory entry. No new grant/App/credential/dispatch attempted. Actual run logs/effective config/skip cause UNKNOWN. Source says CM extends shared default and pin presets, cap3 and at-any-time pin schedule; checked-in config is not hosted-run proof. Only34m31s passed from devkit415 landing1:10:06PM ET to manual CM389 creation1:44:37PM ET; documented4-hour scheduling leaves temporal cause unresolved.

    Next actor: agent:01a1a78b-2c93-7c91-af85-11d5396a26d1
    Next action: Supply an existing supported authenticated log read or launch the bounded GUI reader on this same item after worker closeout. Need run timestamps/version/effective manager and pin config plus branch/PR skip reason from Renovate's own logs; no speculative fix. Item remains open. No claims/changes on neighboring tasks, no programme277 edit, no changes to separately staffed373 files or retained PRs/trees/evidence.

    Evidence: /Volumes/Developer-Artifacts/task-evidence/odoo-devkit/dk418-pin-scheduling-1109 (sanitized portal summary, current API-read configs,415/389 comments, Current Status and private lead notifications). No task tree/branch/commit/push/PR. Primary clean at ed59b17. Tests/lint/IDE/review/consumer builds not run because there is no source change. External-comment radar clear.

    Removed: nothing.
    Net lines: 0.
    Session outcome: {"landed_without_rescue": false, "review_findings_acted_on": 0}

    Session: 01a1c29f-319b-7f92-8c82-21b8d65148db

  3. shiny-code-app commented on Nov 10, 2026

    @shiny-code-app
    ContributorAuthor

    Claimed by DK418-MEND-GUI-1109

    Session: 01a1c2c5-f87a-7871-8095-f2e3998e52e2
    Branch: work/dk418-mend-gui-1109
    Claimed at: 2026-11-09T19:06:14-05:00
    Next action: Read existing authenticated Mend jobs in Chrome; no source changes

    Admission: milestone; https://github.com/cbusillo/direction/issues/5

    Work record

  4. shiny-code-app commented on Nov 10, 2026

    @shiny-code-app
    ContributorAuthor

    Released claim 6754920205

    DK418-MEND-GUI-1109 finite read complete at the mandated authentication boundary. Requested the CM repository in existing native Chrome (Agents profile). Mend redirected to its root platform selector: “Choose a platform to access”. No existing authenticated job session was exposed. Browser access host unavailable; native app route worked. No sign-in, OAuth, credentials, account switching, run trigger or permission changes attempted. Task-owned tab closed; existing tabs and all prior artifacts preserved.

    Actual hosted job timestamps, Renovate version, effective pin/custom-manager configuration, run occurrence between the requested events, and branch/PR creation or skip reason remain UNKNOWN. The three-pull-request-limit cause remains an inference. No source investigation or review repeated; no source correction chosen.

    Next actor: agent:01a1c2bb-4ef6-7251-ba16-1d25e4fd4860
    Next action: Review the authentication boundary on this issue and arrange an existing authenticated Mend session before another bounded read. Issue remains open; no source change authorized by this read.

    Private evidence: /Volumes/Developer-Artifacts/task-evidence/odoo-devkit/dk418-mend-gui-1109/portal-observation.txt
    No task branch/worktree/commit/push/PR created. No source/runtime/data changes. Tests, consumer builds, lint and IDE inspection not run because this was a no-change GUI read; model review explicitly excluded by the brief.

    Removed: 0.
    Net lines: 0.
    Session outcome: {"landed_without_rescue": false, "review_findings_acted_on": 0}
    Session: 01a1c2c5-f87a-7871-8095-f2e3998e52e2

    Session: 01a1c2c5-f87a-7871-8095-f2e3998e52e2

  5. shiny-code-app commented on Nov 10, 2026

    @shiny-code-app
    ContributorAuthor

    Waiting for An existing authenticated Mend Developer Portal session for the CM repository job logs. This ends when The recorded authentication boundary is resolved and a bounded read can open the CM hosted job logs using the existing account. An agent rechecks it on 2026-11-10.

  6. shiny-code-app commented on Nov 11, 2026

    @shiny-code-app
    ContributorAuthor

    Nothing here is waiting on a person or event.

  7. shiny-code-app commented on Nov 11, 2026

    @shiny-code-app
    ContributorAuthor

    Claimed by MEND418-1111

    Session: 625b1392-b980-4737-9b2b-412d5ed4366b
    Branch: work/mend418-1111
    Claimed at: 2026-11-11T11:48:05-05:00
    Next action: Read Renovate job logs in the signed-in Mend session via catalog Chrome

    Admission: repeat-stop; #418, https://github.com/cbusillo/direction/issues/172

    Work record

  8. shiny-code-app commented on Nov 11, 2026

    @shiny-code-app
    ContributorAuthor

    Released claim 6801762334

    MEND418-1111 stopped before any Mend page. The catalog Chrome route has no connected browser, so the signed-in Mend session could not be reached.

    What the tools returned at about 11:48 AM ET:

    • tabs_context_mcp: "Browser extension is not connected. Please ensure the Claude browser extension is installed and running ... and that you are logged into claude.ai with the same account as Claude Code."
    • list_connected_browsers: an empty list, twice, a minute apart.

    Chrome is running with the Agents profile active, and the Claude extension is installed in that profile. It is not paired with the catalog's pinned Claude account (the info home). Mend's own sign-in state was never reached, so this is not the Mend login boundary from the last read.

    No tab was opened. Nothing was clicked, signed in, consented, changed or triggered. The extension's login state was not read. No branch, worktree, commit or PR.

    The cause of the missing devkit pin PR is still unknown. The three-PR count is still an inference, and no config change is chosen without the logs.

    What unblocks it: in the Agents Chrome profile, open the Claude extension and sign it in to the same Claude account as the catalog's pinned home. Then list_connected_browsers returns the browser and the log read can run as briefed.

    Next actor: agent:supervisor
    Next action: Ask the Director to connect the Claude extension in the Agents Chrome profile to the pinned Claude account, then relaunch the bounded log read.

    Evidence: /Volumes/Developer-Artifacts/task-evidence/odoo-devkit/mend418-1111/browser-route.txt
    Tests, lint, IDE inspection and model review not run: no source change.

    Removed: nothing.
    Net lines: 0.
    Session outcome: {"landed_without_rescue": false, "review_findings_acted_on": 0}

    Session: 625b1392-b980-4737-9b2b-412d5ed4366b

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions