Repository navigation
allow fx workflow dispatches - #982
Merged
aaronjmars merged 2 commits intoAug 28, 2026
Merged
Conversation
Co-Authored-By: Svector-anu <Svector-anu@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
add
fxto theworkflow_dispatchharness choices and register a focused regression test.why
fx is already integrated through the adapter, resolver, installer, dashboard, and standardized harness contract. the manual workflow-dispatch choice list was missed when fx was added, so
gh workflow run aeon.yml -f skill=narrative-tracker -f harness=fxfailed with http 422 before aeon executed any code.this is not an fx implementation or authentication change. it only makes the existing harness selectable through manual github actions dispatches.
fix
fxto.github/workflows/aeon.ymlscripts/tests/test_workflow_harness_choices.sh.github/workflows/ci-tests.ymlverification
mutation test with only the
fxoption removed:after restoring the option:
node scripts/validate-config.js— cleannode --test scripts/validate-config.test.js— 14/14 passedbash scripts/tests/test_resolve_harness.sh— all passedbash scripts/tests/test_generate_harnesses_json.sh— all passedgit diff --check— cleanreal github actions proof on the fork: run 33167164883 was accepted, logged
INPUT_HARNESS: fx, resolvedHarness: fx, and installed fx 0.0.6.the run then stopped at the existing credential gate because the test fork has neither
AI_GATEWAY_API_KEYnorVERCEL_OIDC_TOKEN. this pr does not change credentials, authentication, schedules, models, or the default harness.