redhat-et / redhat-et/ProtoBot

Build the local Worker and Triage fixture loop

Open
#69 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

blocked component:job-site
Dominant language
Go
Stars
5
Forks
6
Avg merge
23h 24m
Merged PRs (30d)
66

Description

Scope

Build a deterministic fixture pipeline for Worker A tests and Worker B implementation patches: import path-restricted patches, merge in a private integration repository, run the fixture tests, classify failures, and route sanitized feedback.

This is a control-plane and test-fixture milestone, not a claim that the full agentic Job Site is complete. Real model execution and mutation campaigns follow after the fixture loop is trustworthy.

Dependencies

  • Projection isolation fixtures.
  • Job Site sandbox contract.
  • Validation/WMS contract for work-item state transitions.

Acceptance criteria

  • Tests, implementation, both-fault, and specification-gap outcomes are represented.
  • Worker feedback excludes peer source, assertions, expected/actual values, raw logs, and raw Inspector findings.
  • Retry limits and terminal escalation are deterministic.
  • Every cycle produces auditable fixture evidence and stable status transitions.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the projection isolation fixtures, Job Site sandbox contract, and Validation/WMS contract named under Dependencies. Run the existing fixture tests and trace how patches, integration results, failure classifications, feedback, retries, and status transitions are represented. Done means all four outcomes, sanitized feedback, deterministic retry escalation, auditable cycle evidence, and stable transitions are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devtools, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.