[Fleet Monitor] combsmith/worldchest — .github/workflows/feature-ideation.yml #17

Activity

1. don-petry

   added

   dev-leadRequires dev-lead attentionRequires dev-lead attention

   fleet-trackerTracked by the Actions Fleet MonitorTracked by the Actions Fleet Monitor

   health-checkAutomated health check resultAutomated health check result

   on Oct 22, 2026
2. don-petry commented on Oct 22, 2026

   

   don-petry

   on Oct 22, 2026

   ContributorAuthor

   More actions

   Dev-Lead Implementation Plan

   Issue: #17 — [Fleet Monitor] combsmith/worldchest — .github/workflows/feature-ideation.yml

   Scope

   Root-caused the one failed run. The defect is in the central reusable workflow, not this repo, so I'm making no change to worldchest. The fix is already merged upstream and is waiting to be promoted to the stable channel.

   Root cause

   • Failed run: 39638934543 (workflow_dispatch from the redispatch bridge, 2026-10-21). Job ideate / Gather Project Signals, step Install Python jsonschema:

     ERROR: Could not open requirements file: [Errno 2] No such file or directory: '.feature-ideation-tooling/scripts/feature-ideation-requirements.txt'
     

   • The stub pins feature-ideation-reusable.yml@feature-ideation/v1-stable (364427f). At that commit the reusable defaults tooling_ref: 'v1'. The v1 tag (6432e9a, a rename-only patch of d3d768d from 2026-05-13) predates scripts/feature-ideation-requirements.txt, so the pip step fails for every repo that uses the default.
   • The other run (the discussion event that triggered the redispatch) succeeded, which gives the 50% rate (1 of 2).

   Upstream status

   • Tracked in feature-ideation v1-next: pip step fails — tooling_ref default 'v1' skews from reusable (blocks .github-private, will break fleet on promotion) .github#839. It was fixed by fix(feature-ideation): source tooling from the reusable's own commit (#839) .github#1368 (c2bc153, merged 2026-10-22 04:57Z): tooling_ref now defaults to '', which sources the tooling from the reusable's own commit.
   • Channel positions right now: feature-ideation/v1-next = c2bc153 (has the fix), v1-ring1 = bc27529, v1-stable = 364427f (still has the bug).
   • What has to happen: promote the fix to stable (cut-release.sh feature-ideation <version> --channel stable, through ring1 per the ring model). This repo recovers automatically on its next run after that, with no stub change.

   Implementation Checklist

   • None. .github/workflows/feature-ideation.yml is an org-managed thin-caller stub (AGENTS.md: "do not hand-edit"). Its header allows changing only project_context and the cron. Adding a repo-local tooling_ref: override would be stub drift, and the fleet stub sync would revert it.

   Tests to Write

   • None. There is no behavioural change in this repo (TDD exception: no code or config change).

   Test Command

   bash .dev-lead/scripts/dev-lead-lint.sh (repo has no test suite yet, per AGENTS.md)

   Suggested follow-up

   Keep this issue open until feature-ideation/v1-stable includes c2bc153, then confirm with a manual workflow_dispatch of Feature Ideation here.
3. don-petry commented on Oct 25, 2026

   

   don-petry

   on Oct 25, 2026

   ContributorAuthor

   More actions

   ✅ Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-10-22 (3 days) — the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.
4. don-petry

   closed this as completedon Oct 25, 2026