Affected area
GitHub / code review
Problem or workflow pressure
External pull requests and their prerequisite issues do not consistently provide enough public context for maintainers to assess provenance, scope, design risk, or review cost. Large uncoordinated diffs create disproportionate review pressure, while an empty issue can otherwise bypass a mandatory Issue reference.
Desired outcome
Require structured Issue and PR context, warn when Bug or Feature issues bypass their forms, give invalid PR bodies a finite correction window, and close oversized external changes that lack prior issue discussion.
Proposed solution
Keep pure format checkers, GitHub status policies, and workflows separate. Require full Lody Issue URLs and public Context handoffs in external PRs; warn non-owner Issue authors with a self-healing status label; enforce a 200-line additions-plus-deletions boundary for external PRs without an Issue reference.
Alternatives or workarounds
Manual maintainer triage is inconsistent and does not give contributors immediate, actionable feedback.
Trade-offs or non-goals
Do not infer whether maintainers approved a linked design. Issue violations are warnings only, while expired PR-body violations and oversized unreferenced PRs may close the PR without deleting its branch.
Additional context
The policy implementation is tracked in #91.
Before submitting
Affected area
GitHub / code review
Problem or workflow pressure
External pull requests and their prerequisite issues do not consistently provide enough public context for maintainers to assess provenance, scope, design risk, or review cost. Large uncoordinated diffs create disproportionate review pressure, while an empty issue can otherwise bypass a mandatory Issue reference.
Desired outcome
Require structured Issue and PR context, warn when Bug or Feature issues bypass their forms, give invalid PR bodies a finite correction window, and close oversized external changes that lack prior issue discussion.
Proposed solution
Keep pure format checkers, GitHub status policies, and workflows separate. Require full Lody Issue URLs and public Context handoffs in external PRs; warn non-owner Issue authors with a self-healing status label; enforce a 200-line additions-plus-deletions boundary for external PRs without an Issue reference.
Alternatives or workarounds
Manual maintainer triage is inconsistent and does not give contributors immediate, actionable feedback.
Trade-offs or non-goals
Do not infer whether maintainers approved a linked design. Issue violations are warnings only, while expired PR-body violations and oversized unreferenced PRs may close the PR without deleting its branch.
Additional context
The policy implementation is tracked in #91.
Before submitting