Skip to content

Add verification policy for bug fixes and refactoring#57

Merged
cubenoy22 merged 1 commit into
mainfrom
docs/verification-policy
Jul 6, 2026
Merged

Add verification policy for bug fixes and refactoring#57
cubenoy22 merged 1 commit into
mainfrom
docs/verification-policy

Conversation

@Lihi-AI

@Lihi-AI Lihi-AI commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

Codifies the maintainer's verification policy in AGENTS.md so every agent and contributor works to the same bar:

  • Bug fixes: demonstrated red→green, with the pre-fix failure evidence recorded in the PR.
  • Refactoring: behavior-preserving under pinned results (characterization tests first where coverage is missing), verified in both testing and testing-asan.
  • OS-dependent behavior: verified with the platform unit-test targets (LokaTestsMacOS / LokaTestsWin32) or by driving the affected example flow on that platform; for Classic targets, test executables in Mini vMac / real hardware, with Flow-driven scenario automation as the intended long-term harness.
  • If a discriminating test is impossible in the current fixture, the PR must say so and name the tracked follow-up.

Note: this commit is unsigned (ssh-agent not reloaded after restart); squash-merge covers it per the signing policy.

🤖 Generated with Claude Code

Bug fixes require demonstrated red->green with recorded pre-fix
failure evidence; refactors require pinned before/after results in
both test presets; OS-dependent behavior is verified with the
platform unit-test targets or example flows, with Classic-target
test executables and Flow-driven scenario automation as the
long-term harness.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Lihi-AI Lihi-AI force-pushed the docs/verification-policy branch from c136dd9 to a18bd93 Compare July 6, 2026 15:22
@cubenoy22 cubenoy22 requested a review from Copilot July 6, 2026 15:37
@cubenoy22 cubenoy22 merged commit b7d0080 into main Jul 6, 2026
1 check passed
@cubenoy22 cubenoy22 deleted the docs/verification-policy branch July 6, 2026 15:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Codifies a repository-wide verification bar for bug fixes and refactoring by documenting it in AGENTS.md, so contributors follow consistent evidence and platform-validation expectations.

Changes:

  • Added an explicit “Verification Policy For Bug Fixes And Refactoring” section covering red→green expectations, behavior-preserving refactors, and platform/Classic validation.
  • Documented what to do when headless tests cannot discriminate a change and when tests are infeasible (require explicit PR note + tracked follow-up).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread AGENTS.md
- If a design or implementation path looks fragile, hard to reason about, or likely to cause intermittent bugs, prefer a small refactor toward a simpler structure first. If no clear low-risk refactor is apparent, stop and call it out to the user before building further on top of it.

## Verification Policy For Bug Fixes And Refactoring
- Bug fixes must demonstrate red->green: add or extend a test that fails (or hard-fails under ASan) on the pre-fix code, confirm that failure, then land the fix that turns it green. Record the pre-fix failure evidence in the PR.
Comment thread AGENTS.md

## Verification Policy For Bug Fixes And Refactoring
- Bug fixes must demonstrate red->green: add or extend a test that fails (or hard-fails under ASan) on the pre-fix code, confirm that failure, then land the fix that turns it green. Record the pre-fix failure evidence in the PR.
- Refactoring must be behavior-preserving under pinned results: add characterization tests first where coverage is missing, then show identical results before and after the change in both the `testing` and `testing-asan` presets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants