Merged Reproducible-Bug PR Bonus Policy

OpenCoven is in beta. This bonus rewards useful testing that produces focused, maintainable fixes—not raw issue volume.

Maximum bonus from this category: 10 points per submitted entry.

Eligible repositories

A PR may qualify when merged into:

• https://github.com/OpenCoven/coven
• https://github.com/OpenCoven/coven-cave
• https://github.com/OpenCoven/coven-runtimes
• another OpenCoven repository explicitly approved in the Hackathon Discord

Required timing

To qualify:

1. the bug must be discovered or materially reproduced during the Hackathon;
2. the issue or PR must be opened before the project submission deadline;
3. the issue or PR must identify the Hackathon team;
4. the PR must be merged before judges lock scores.

A later announcement date does not permit new PRs after the submission deadline. It may provide maintainers more time to review PRs already open.

Required bug report

A reproducible report should contain:

• environment and operating system;
• OpenCoven component and version or commit;
• exact steps to reproduce;
• expected behavior;
• actual behavior;
• sanitized logs, screenshots, or minimal reproduction where useful;
• frequency or conditions;
• impact;
• confirmation that secrets and private session data were removed.

“Sometimes it breaks” is not a reproducible report.

Required fix quality

The PR must:

• fix a real defect, not manufacture one;
• reference the issue or include equivalent reproduction detail;
• remain focused on one concern;
• follow the target repository’s contribution guide and PR template;
• include signed-off commits when required;
• pass required CI;
• add or update a regression test when practical;
• update documentation when behavior changes;
• avoid unrelated formatting or refactoring;
• contain no secrets or private data.

For larger or design-heavy changes, open an issue first and align with maintainers.

Point bands

Points are assigned by the judges after considering maintainer feedback.

1 point — small fix

Examples:

• incorrect command, path, or documented behavior blocking a real path;
• narrow UI or state bug;
• focused low-impact regression;
• typo only when it changes executable behavior or materially misleads setup.

A cosmetic spelling correction alone normally earns no bonus.

2 points — standard functional fix

Examples:

• command or API behavior fails under reproducible conditions;
• session, workflow, or UI functionality behaves incorrectly;
• a regression test demonstrates the failure and fix;
• ordinary cross-platform or configuration defect.

3 points — substantial fix

Examples:

• session reliability or lifecycle defect;
• data-integrity or state-loss risk;
• meaningful cross-platform failure;
• high-impact regression affecting common workflows;
• difficult defect with strong reproduction and regression coverage.

A 3-point classification requires more than a large diff. Impact, diagnosis, focus, and verification matter.

Maximum and attribution

• Maximum: 10 points per Hackathon entry.
• Multiple team members may contribute PRs; points belong to the submitted team.
• A person cannot claim the same PR for multiple entries.
• Co-authored PRs are divided or assigned by judge determination based on documented contribution.
• Duplicate PRs receive no points after the first accepted fix.
• A chain of tiny PRs that should have been one change may be scored as one fix.
• Reverts, superseded fixes, or merges that do not resolve the reported bug may receive zero points.

No double counting

The same code change cannot receive both:

• merged reproducible-bug points; and
• new OpenCoven capability points.

A fix incidentally adding a small helper remains a bug fix. A feature addressing a missing capability is not converted into a bug to earn both bonuses.

Maintainer control

A PR earns no bonus merely because it was opened.

Maintainers retain complete control over:

• whether the report is valid;
• whether the proposed approach fits the repository;
• whether the PR is merged;
• what follow-up changes are required;
• whether an issue is a bug, enhancement, duplicate, security issue, or out of scope.

The Hackathon does not create a right to merge.

Security vulnerabilities

Do not publicly disclose a suspected security vulnerability.

Use the target repository’s private security-reporting path. A responsibly reported and fixed vulnerability may receive discretionary equivalent credit only after maintainers confirm that scoring will not expose sensitive information. Public proof is not required when it would create risk.

Anti-gaming

Zero points and possible disqualification may result from:

• fabricated reproduction steps;
• intentional creation of a defect;
• coordinated duplicate reports;
• splitting one fix into unnecessary PRs;
• unsafe public disclosure;
• alternate accounts used to inflate activity;
• claiming another contributor’s work;
• misrepresenting maintainer comments or merge status.

Recommended PR marker

Add this line to the PR description:

OpenCoven Beta Hackathon 2026 contribution
Team: <team name>
Submission repository: <URL>

Do not add labels or repeatedly mention maintainers unless the repository requests it.