docs: finalize contributing guide

Author: BrycensRanch

.github/CONTRIBUTING.md

@@ -130,7 +130,9 @@ Just as in the **subject**, use the imperative, present tense: "change"; not "ch
 
 The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**, **Fixes**, or **Relates to**.
 
-> Breaking Changes are intended to be highlighted in the CHANGELOG as changes that will require community users to modify their code after updating to a version that contains this commit.
+> Breaking Changes are intended to be highlighted in the CHANGELOG as MAJOR. The major version is increased IF:
+> - A release contains major UI/functionality updates (e.g., new interface design) that significantly change the user workflow.
+> - Breaking changes to the CLI (e.g., removing/renaming flags, changing output formats) that require users to update their scripts.
 
 ##### Sample Commit messages
 
@@ -167,6 +169,7 @@ One of the major benefits of this approach is that it will **automatically relea
 - The master branch should always have working code that is tested. _Use Pull Requests to work on bigger features or bug fixes and merge them when you are ready._
 - Every bugfix, feature, and change should have one commit associated with it. _Do not mix multiple bugs, features, etc., into one huge commit message. Keep your commit size small and commit often._
 - Your commit messages must follow the [conventional commit rules](https://www.conventionalcommits.org/). Additionally, the Angular flavor is accepted as well.
+- While the version is v0.x.y, breaking changes will result in an increase of the Minor version. The Major version will remain 0 until the initial stable release (v1.0.0).
 
 #### Versioning Rules
 
@@ -208,7 +211,7 @@ The version bump is automatically determined based on your commit messages. Here
 Okay, so here's the thing:
 
 - **No GitHub issues generated by AI.** \
-It won't be merged if it was written by a chatbot. Only open issues if you truly comprehend the feature or bug you're describing.
+It won't be reviewed if it was written by a chatbot. Only open issues if you truly comprehend the feature or bug you're describing.
 
 - **No "vibe coding".** \
 Just because "it works on your machine" doesn't mean you should submit the code. It doesn't belong here if you can't explain what it does or why.

README.md

@@ -91,12 +91,12 @@ SnapX is packaged on:
 
 Additionally, you can download nightly builds from [here](https://nightly.link/SnapXL/SnapX/workflows/build/develop?preview).
 
-## Building & Contributions
+## Building & Contributing
 
 Contributions are welcome.
 See [BUILDING.md](./.github/BUILDING.md) for build instructions.
 
-The documentation for contributing is a work in progress, but here is a [rough draft](./.github/CONTRIBUTING.md).
+The documentation for contributing can be found [here](./.github/CONTRIBUTING.md).
 
 ## Donators 💖