Add issue and pull request templates, and a contributing section - #4
Merged
Conversation
The contribution policy existed in blueclaw's README and nowhere here, so this repository asked for nothing and said nothing about what it would accept. The bug form asks for the event ledger first. It is the record of what the loop did rather than what it said afterwards, and cmd/bluecollar prints it now, so there is no longer a reason for a report to arrive without one. It also asks which model answered and through what: the loop requests structured output and weak models fail that differently from strong ones, which is most of the difference between a bug here and a bug in the caller. The second form is for arguing with a decision. The guarantees of this loop are test names, so it asks the reporter to point at one.
eastriverlee
added a commit
that referenced
this pull request
Aug 5, 2026
#4) The contribution policy existed in blueclaw's README and nowhere here, so this repository asked for nothing and said nothing about what it would accept. The bug form asks for the event ledger first. It is the record of what the loop did rather than what it said afterwards, and cmd/bluecollar prints it now, so there is no longer a reason for a report to arrive without one. It also asks which model answered and through what: the loop requests structured output and weak models fail that differently from strong ones, which is most of the difference between a bug here and a bug in the caller. The second form is for arguing with a decision. The guarantees of this loop are test names, so it asks the reporter to point at one.
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
1 participant
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.
This repository asked for nothing and said nothing about what it would accept.
The contribution policy lived in blueclaw's README and had no counterpart here.
Templates
Bug report asks for the event ledger first — the record of what the loop
did rather than what it said afterwards.
cmd/bluecollarprints it to stderrnow, so a report no longer has a reason to arrive without one.
It also asks which model answered and through what. The loop requests structured
output, and weak models fail that differently from strong ones; that distinction
is most of the difference between a bug here and a bug in the caller.
Design question or disagreement asks the reporter to point at a test name,
since the guarantees of this loop are test names.
Contact links state the closed-until-alpha pull request policy so it does not
arrive as a public issue. Blank issues stay enabled. There is no
SECURITY.mdin this repository, so nothing links to one.
PULL_REQUEST_TEMPLATE.mdasks for the test that fails without the change.Contributing section
Mirrors blueclaw's, with one difference: it says a decision you disagree with is
the most useful issue, which is what a pre-alpha library published for its design
actually wants.
Checks
All three YAML forms parse. Documentation and templates only — no code.