Skip to content

[Fleet Monitor] petry-projects/.github-private β€” .github/workflows/feature-ideation.ymlΒ #1827

Closed

Description

@don-petry

🟠 DEGRADED: petry-projects/.github-private / .github/workflows/feature-ideation.yml

Metric Value
Failure Rate 50% (1 / 2 runs)
Status DEGRADED
p50 Duration 23s
p95 Duration 23s
Successful Runs 1
Cancelled Runs 0

Workflow: .github/workflows/feature-ideation.yml

Last updated by Fleet Monitor run on 2026-09-16.
Threshold: failure rate > 10% over the monitored window.

Activity

  1. added
    health-checkAutomated health check report
    dev-leadFor dev-lead agent pickup
    fleet-trackerTracked by the Actions Fleet Monitor
    on Sep 16, 2026
  2. don-petry commented on Sep 16, 2026

    @don-petry
    CollaboratorAuthor

    Dev-Lead Implementation Plan

    Issue: #1827 β€” [Fleet Monitor] petry-projects/.github-private β€” .github/workflows/feature-ideation.yml

    Root cause

    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_ref is 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)

    Test Command

    bats tests/test_feature_ideation.bats

  3. don-petry commented on Sep 16, 2026

    @don-petry
    CollaboratorAuthor

    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_ref is 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)
    

    Files touched (this workspace, not yet pushed)

    • .github/workflows/feature-ideation.yml: forward tooling_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.

  4. don-petry commented on Sep 16, 2026

    @don-petry
    CollaboratorAuthor

    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.

    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.

  5. added a commit that references this issue on Sep 16, 2026
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

    dev-leadFor dev-lead agent pickupfleet-trackerTracked by the Actions Fleet Monitorhealth-checkAutomated health check report

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions