Update documentation with new test requirements and planning improvements

- Added requirement to run and pass all tests before committing in `build.md` with guidance on crafting commit messages.
- Enhanced `plan.md` with a task to organize hook tests into separate files for better maintainability.

Author: jensenbox

docs/build.md

@@ -9,5 +9,6 @@ For each task, use the following workflow - execute each in order and show the r
  * run the relevant code to ensure it works as expected
  * run the application without any arguments and correct any errors and warnings you find iteratively until it works without error. Also, ensure running the test suite returns without errors or warnings.
  * run the application with the "run" argument and correct any errors and warnings you find iteratively until it works without error.
- * commit and push all files
+ * run all tests and correct any errors and warnings you find iteratively until all tests pass.
+ * commit and push all files - craft a good commit message.
 Only implement the first on the list and stop.

docs/plan.md

@@ -67,3 +67,4 @@ Tasks:
 - [ ] Lets remove the `rh` executable and rename it to `rustyhook` - we will use a shell alias to make `rustyhook` available as `rh`. We can add that alias as part of the installation process - perhaps in the completion scripts.
 - [ ] emulate all known pre-commit hooks for use with native execution - all known hooks at https://github.com/pre-commit/pre-commit-hooks
 - [ ] Add code coverage to the project and emit statistics on the coverage of the tests. Ideally the output should be in a format that can be used by codecov.io
+- [ ] Break up the hook tests into individual files per hook test - this should help adding more as it will keep things very tidy upon changes.