What happened
Every agent run on this repo logs a 404 error when trying to load the qualityflow agent definition. The error appears in all three review runs triggered by PR #54 (32591507621, 32591974169, 32591991370):
skipping agent qualityflow: load failed: resolving URL-sourced resources:
base agent: fetching https://raw.githubusercontent.com/redhat-community-ai-tools/
qualityflow-fullsend/.../qualityflow.md: fetch: non-200 status code: got 404
The .fullsend/config.yaml references the qualityflow harness YAML at commit b26c947 of redhat-community-ai-tools/qualityflow-fullsend, but the agent definition file (qualityflow.md) referenced within that harness YAML does not exist at that commit. PR #54 deliberately kept this reference (the PR description says it is not covered by CLI fallback), but the reference is non-functional.
What could go better
The qualityflow agent should either resolve successfully or be removed from the config. Currently it fails silently on every run, adding noise to logs and potentially masking other resolution errors. Confidence is high that this is a broken reference — the 404 is a genuine HTTP response from GitHub's raw content service, not an access control issue (the allowed_remote_resources list includes the qualityflow domain).
The root cause is likely one of: (a) the external repo restructured its files after the pinned commit, (b) the agent definition file was never at that path, or (c) the pinned commit predates the addition of qualityflow.md. Investigation with the qualityflow maintainers would confirm which.
Proposed change
In .fullsend/config.yaml, either:
-
Update the qualityflow reference to a commit SHA where qualityflow.md exists in the expected location within the redhat-community-ai-tools/qualityflow-fullsend repo. This requires checking the external repo's commit history to find a valid commit.
-
Remove the qualityflow agent entry and its allowed_remote_resources entry if the qualityflow agent is not actively used in this repo. This eliminates the 404 noise entirely.
Option 2 is simpler and safer if qualityflow is not currently providing value. Option 1 is preferred if the experiment is still active.
Validation criteria
After the fix, agent runs on fullsend-ai/experiments should no longer log skipping agent qualityflow: load failed with a 404 status. Verify by checking the next 3 fullsend workflow runs on the repo — the qualityflow agent should either resolve successfully (option 1) or not appear in the agent resolution log at all (option 2).
Generated by retro agent from #54
What happened
Every agent run on this repo logs a 404 error when trying to load the qualityflow agent definition. The error appears in all three review runs triggered by PR #54 (32591507621, 32591974169, 32591991370):
The
.fullsend/config.yamlreferences the qualityflow harness YAML at commitb26c947ofredhat-community-ai-tools/qualityflow-fullsend, but the agent definition file (qualityflow.md) referenced within that harness YAML does not exist at that commit. PR #54 deliberately kept this reference (the PR description says it is not covered by CLI fallback), but the reference is non-functional.What could go better
The qualityflow agent should either resolve successfully or be removed from the config. Currently it fails silently on every run, adding noise to logs and potentially masking other resolution errors. Confidence is high that this is a broken reference — the 404 is a genuine HTTP response from GitHub's raw content service, not an access control issue (the
allowed_remote_resourceslist includes the qualityflow domain).The root cause is likely one of: (a) the external repo restructured its files after the pinned commit, (b) the agent definition file was never at that path, or (c) the pinned commit predates the addition of
qualityflow.md. Investigation with the qualityflow maintainers would confirm which.Proposed change
In
.fullsend/config.yaml, either:Update the qualityflow reference to a commit SHA where
qualityflow.mdexists in the expected location within theredhat-community-ai-tools/qualityflow-fullsendrepo. This requires checking the external repo's commit history to find a valid commit.Remove the qualityflow agent entry and its
allowed_remote_resourcesentry if the qualityflow agent is not actively used in this repo. This eliminates the 404 noise entirely.Option 2 is simpler and safer if qualityflow is not currently providing value. Option 1 is preferred if the experiment is still active.
Validation criteria
After the fix, agent runs on fullsend-ai/experiments should no longer log
skipping agent qualityflow: load failedwith a 404 status. Verify by checking the next 3 fullsend workflow runs on the repo — the qualityflow agent should either resolve successfully (option 1) or not appear in the agent resolution log at all (option 2).Generated by retro agent from #54