From 0b3aee5887b4ce2f3a15fd84142ccba24101c97d Mon Sep 17 00:00:00 2001
From: Yitz Willroth <yitzwillroth@gmail.com>
Date: Sun, 21 Sep 2025 08:40:31 -0400
Subject: [PATCH 1/3] Remove .junie

---
 .junie/guidelines.md | 40 ----------------------------------------
 1 file changed, 40 deletions(-)
 delete mode 100644 .junie/guidelines.md

diff --git a/.junie/guidelines.md b/.junie/guidelines.md
deleted file mode 100644
index 95f8e00..0000000
--- a/.junie/guidelines.md
+++ /dev/null
@@ -1,40 +0,0 @@
-## Conventions
-- You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, naming.
-
-## Verification Scripts
-- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.
-
-## Application Structure & Architecture
-- Stick to the existing directory structure. Do not create new base folders without approval.
-- Do not change the application's dependencies without approval.
-
-## Replies
-- Be concise in your explanations. Focus on what's important rather than details obvious to an experienced developer.
-
-## Documentation Files
-- You must only create documentation files if explicitly requested by the user.
-
-## Pest
-
-### Testing
-- If you need to verify a feature is working, write or update a `Unit` or `Feature` test.
-- Every change must be programmatically tested. Write a new test or update an existing test, then run the affected tests to make sure they pass.
-
-### Pest Tests
-- All tests must be written using Pest.
-- You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files. These are core to the application.
-- Tests should test all of the happy paths, failure paths, and weird paths.
-- Tests live in the `tests/Feature` and `tests/Unit` directories.
-- Pest tests look and behave like this:
-```php
-it('is true', function () {
-    expect(true)->toBeTrue();
-});
-```
-
-### Running Tests
-- Run the minimal number of tests using an appropriate filter before finalizing code edits.
-- To run all tests: `vendor/bin/pest`.
-- To run all tests in a file: `vendor/bin/pest tests/Feature/ExampleTest.php`.
-- To filter on a particular test name: `vendor/bin/pest --filter=testName` (recommended after making a change to a related file).
-- When the tests relating to your changes are passing, run the entire test suite.

From 8102ecdae2b4749ebb066163f73fbc5c8e8ca7cc Mon Sep 17 00:00:00 2001
From: Yitz Willroth <yitzwillroth@gmail.com>
Date: Sun, 21 Sep 2025 08:42:46 -0400
Subject: [PATCH 2/3] Add /.junie to .gitignore

---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index d304c48..f745b03 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,3 +5,4 @@
 /.phpunit.cache
 .claude
 .DS_Store
+/.junie

From 8a82139eaf82d6e3d2fd78ce252454e3fa9bde85 Mon Sep 17 00:00:00 2001
From: Taylor Otwell <taylor@laravel.com>
Date: Sun, 21 Sep 2025 10:08:28 -0500
Subject: [PATCH 3/3] Update .gitignore

---
 .gitignore | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitignore b/.gitignore
index f745b03..ea7d59f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,7 +2,7 @@
 /vendor
 /composer.lock
 /phpunit.xml
+/.junie
 /.phpunit.cache
 .claude
 .DS_Store
-/.junie