Skip to content

Bug-hunt loop state #29

Description

@REPPL

This issue is the persistent state for an autonomous, scheduled bug-hunt loop running against this repository. Each scheduled run is exactly one round.

Protocol

Each round:

  1. Reads this issue's comments for loop state (only comments by the repo owner or collaborators count; LOOP-STOPPED in a trusted comment halts the loop permanently).
  2. Verifies a green baseline (make build, gofmt -l ., go vet ./..., go test ./..., go test -race ./internal/..., and the full eval suite with FERRY_BIN set). A red baseline the round did not cause stops the round.
  3. Hunts tracked files across four dimensions: code bugs, docs vs functionality, infrastructure, and internal doc consistency. Every finding needs file:line evidence.
  4. Adversarially reviews each candidate finding; only findings that survive refutation are fixed.
  5. Fixes confirmed findings on a bughunt/round-N branch, with tests, and opens one PR per round.
  6. Auto-merges only if CI is fully green and two independent adversarial reviewers both return SHIP; otherwise the PR is left open with an explanatory comment.
  7. Posts one round record comment here: Round N — findings: X substantive, Y nitpick, Z refuted; nitpicks-only: yes|no; PR #M merged|open (<reason>)|none.

After three consecutive nitpick-only rounds, the loop posts LOOP-STOPPED and ends.

Consecutive nitpick-only rounds: 0

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions