You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reusable feature-ideation-reusable.yml checks out its Python tooling from petry-projects/.github at inputs.tooling_ref, which defaults to the v1
release tag. This repo rides the next ring (the stub pins the reusable at @feature-ideation/v1-next), but the tooling still resolves to the lagging v1 tag β which predates scripts/feature-ideation-requirements.txt. The
"Install Python jsonschema" step then dies with Could not open requirements file: '.feature-ideation-tooling/scripts/feature-ideation-requirements.txt',
failing every schedule/dispatch run (discussion runs pass because they only hit
the redispatch bridge). Confirmed: the file exists at feature-ideation/v1-next
and main, but 404s at v1.
Fix
Forward tooling_ref: feature-ideation/v1-next from the stub so the tooling is
sourced from the same ring the reusable is pinned to (lockstep). This is safe
w.r.t. the channel-skew guardrail: tooling_refis declared in workflow_call.inputs at the pinned @feature-ideation/v1-next commit, so this
is not an undeclared-input forward. It is a static literal (not a dispatch
input), so it does not go through the prep job and does not trip the #571 inputs.*-in-with: guard.
Implementation Checklist
.github/workflows/feature-ideation.yml β add tooling_ref: feature-ideation/v1-next to the ideate job's reusable with: block, with an explanatory comment
Tests to Write
tests/test_feature_ideation.bats β assert the stub forwards tooling_ref pinned to the same feature-ideation/v1-next channel as the reusable (regression guard for the stale-v1 tooling default)
Dev-Lead: Progress (in progress β not yet durable)
Provisional. Nothing is pushed yet; the automation posts the authoritative
completion record (with PR number + head SHA) after the push. Treat the notes
below as intent, not delivered results.
Root cause (confirmed)
Every schedule/dispatch run died at the reusable's "Install Python jsonschema"
step with Could not open requirements file: '.feature-ideation-tooling/scripts/feature-ideation-requirements.txt'.
The reusable checks out its tooling from petry-projects/.github at inputs.tooling_ref, which defaults to the v1 release tag. This repo rides
the next ring (reusable pinned @feature-ideation/v1-next), but the v1 tag
lags and predates that requirements file β so tooling and workflow drifted apart.
Verified: the file 404s at v1 but exists at feature-ideation/v1-next and main.
(discussion-event runs passed because they only hit the redispatch bridge.)
Plan Execution (intended)
Forward tooling_ref: feature-ideation/v1-next from the ideate job's reusable with: block so tooling rides the same ring as the reusable (lockstep).
Added a regression test in tests/test_feature_ideation.bats.
Guardrail check
tooling_refis declared in workflow_call.inputs at the pinned @feature-ideation/v1-next commit β confirmed by validate-caller-inputs.sh
(forwarded inputs β declared). So this is not a channel-skew (#1052)
forward. It is a static literal (no inputs.*), so it does not need prep-job
routing and does not trip the #571 guard.
Local check output (provisional β not the pushed run)
bats tests/test_feature_ideation.bats β 16/16 ok
.dev-lead/scripts/dev-lead-lint.sh β all checks passed
validate-caller-inputs.sh (VCI_RESOLVE_CROSS_REPO=1) β feature-ideation.yml OK
test_reusable_pin_compliance.py β PASS (14 canonical pins)
tests/test_feature_ideation.bats: regression test asserting the forward.
Notes
Cannot exercise the live GitHub Actions run from this workspace; correctness is
verified statically (the requirements file's presence at the pinned ref was
confirmed via the GitHub API). No unrelated files touched.
The implementation for issue #1827 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
Review happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks β not asserted here. If a later stage fails, this claim is retracted in place.
Activity
don-petry commentedon Sep 16, 2026
Dev-Lead Implementation Plan
Issue: #1827 β [Fleet Monitor] petry-projects/.github-private β .github/workflows/feature-ideation.yml
Root cause
The reusable
feature-ideation-reusable.ymlchecks out its Python tooling frompetry-projects/.githubatinputs.tooling_ref, which defaults to thev1release tag. This repo rides the
nextring (the stub pins the reusable at@feature-ideation/v1-next), but the tooling still resolves to the laggingv1tag β which predatesscripts/feature-ideation-requirements.txt. The"Install Python jsonschema" step then dies with
Could not open requirements file: '.feature-ideation-tooling/scripts/feature-ideation-requirements.txt',failing every schedule/dispatch run (discussion runs pass because they only hit
the redispatch bridge). Confirmed: the file exists at
feature-ideation/v1-nextand
main, but 404s atv1.Fix
Forward
tooling_ref: feature-ideation/v1-nextfrom the stub so the tooling issourced from the same ring the reusable is pinned to (lockstep). This is safe
w.r.t. the channel-skew guardrail:
tooling_refis declared inworkflow_call.inputsat the pinned@feature-ideation/v1-nextcommit, so thisis not an undeclared-input forward. It is a static literal (not a dispatch
input), so it does not go through the
prepjob and does not trip the #571inputs.*-in-with:guard.Implementation Checklist
.github/workflows/feature-ideation.ymlβ addtooling_ref: feature-ideation/v1-nextto theideatejob's reusablewith:block, with an explanatory commentTests to Write
tests/test_feature_ideation.batsβ assert the stub forwardstooling_refpinned to the samefeature-ideation/v1-nextchannel as the reusable (regression guard for the stale-v1tooling default)Test Command
bats tests/test_feature_ideation.batsdon-petry commentedon Sep 16, 2026
Dev-Lead: Progress (in progress β not yet durable)
Root cause (confirmed)
Every schedule/dispatch run died at the reusable's "Install Python jsonschema"
step with
Could not open requirements file: '.feature-ideation-tooling/scripts/feature-ideation-requirements.txt'.The reusable checks out its tooling from
petry-projects/.githubatinputs.tooling_ref, which defaults to thev1release tag. This repo ridesthe
nextring (reusable pinned@feature-ideation/v1-next), but thev1taglags and predates that requirements file β so tooling and workflow drifted apart.
Verified: the file 404s at
v1but exists atfeature-ideation/v1-nextandmain.(discussion-event runs passed because they only hit the redispatch bridge.)
Plan Execution (intended)
tooling_ref: feature-ideation/v1-nextfrom theideatejob's reusablewith:block so tooling rides the same ring as the reusable (lockstep).tests/test_feature_ideation.bats.Guardrail check
tooling_refis declared inworkflow_call.inputsat the pinned@feature-ideation/v1-nextcommit β confirmed byvalidate-caller-inputs.sh(
forwarded inputs β declared). So this is not a channel-skew (#1052)forward. It is a static literal (no
inputs.*), so it does not needprep-jobrouting and does not trip the #571 guard.
Local check output (provisional β not the pushed run)
Files touched (this workspace, not yet pushed)
.github/workflows/feature-ideation.yml: forwardtooling_ref: feature-ideation/v1-next.tests/test_feature_ideation.bats: regression test asserting the forward.Notes
Cannot exercise the live GitHub Actions run from this workspace; correctness is
verified statically (the requirements file's presence at the pinned ref was
confirmed via the GitHub API). No unrelated files touched.
don-petry commentedon Sep 16, 2026
Dev-Lead: Implementation Complete β PR #1828
The implementation for issue #1827 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
955032f9bfddea44ae1dc92672ef781bb35abeacReview happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks β not asserted here. If a later stage fails, this claim is retracted in place.
feat: implement issue #1827 β [Fleet Monitor] petry-projects/.github-β¦