Feature/osa package with ai tooling guards (#1)

* - Add scripts to validate safety of ai tooling
- mise to 22
- yarn to 4.10.x

* Mass migrate to better folder structure to organize apps zsh js code

* use commander cli and swap to full cli

* add linter

* Fix test pipelines

* Fix release

* downgrade to v4 checkout in case error

* remove validate syntax unnecessary complication

* fix bad path

* move pipeline run of tests to top level

* remove redundant code

* fix/remove unnecessary pipeline steps

* fix gitigore for yarn install state

* add base tsconfig

* improve documentation

* improve the cli to identify issues quickly

* - fix testing with 95% coverage threshold

* make ci run test:coverage

Author: FrederickEngelhardt

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,44 @@
 ---
 name: Bug Report
-about: Report an issue with OSA setup
+about: Report an issue with OSA snippets
 title: "[BUG] "
 labels: bug
-assignees: ''
-
+assignees: ""
 ---
 
 ## Environment
+
 - **Platform**: macOS / Linux / WSL
 - **Shell**: zsh version (output of `zsh --version`)
 - **OSA version**: (output of `git describe --tags`)
 - **Running in VM**: Yes / No (e.g., VMware, VirtualBox, Parallels, etc.)
-- **VM Type** (if applicable): _
+- **VM Type** (if applicable): \_
 
 ## Reproduction Steps
-1. 
-2. 
-3. 
+
+1.
+2.
+3.
 
 ## Expected Behavior
-_
+
+\_
 
 ## Actual Behavior
-_
+
+\_
 
 ## Error Output
+
 ```
 (paste any error messages or logs here)
 ```
 
 ## Configuration Used
+
 - Config file: (e.g., `configs/minimal.json`)
-- Or describe custom setup: _
+- Or describe custom setup: \_
 
 ## Additional Context
-_
+
+\_

.github/copilot-instructions.md

@@ -5,33 +5,43 @@ If there are conflicting or ambigious rules, mention them immediately in any ses
 ## Rules
 
 1. Quality
-    - Clean code
-    - Proper error handling
-    - Documentation of functions and modules but not changes per prompt
 
-2. Conventions 
-    - Use consistent naming conventions for scripts and files
+   - Clean code
+   - Proper error handling
+   - Documentation of functions and modules but not changes per prompt
+
+2. Conventions
+
+   - Use consistent naming conventions for scripts and files
 
 3. Patterns
-    - Prevent recursive scripts from deleting important and unrelated files
-    - Protect against security issues
-    - Prevent infinite loops
-    - Avoid hardcoding values
-    - Ensure script performance
-    - Bail on malformed paths
-
-3. Testing
-    - Add tests for any cli changes
-    - Test inputs and outputs
-    - Ensure full branching, statements, and path coverage
-
-4. Files
-    - Always use .zsh extension for shell files
-    - Update the README.md if modifications/updates/changes are added to osa-cli tool scope which change/add/remove usage/description/args/options of the cli we need the cli doc to always match the actual implementation.
-
-
-5. Prompting/Responses
-    - Do not create or generate or modify files documenting changes made in prompt.
-    - Do not add comments indicating changes were made in response to a prompt.
-    - Avoid mentioning the use of AI or Copilot in code comments or documentation.
-    - Write code that is understandable and legible for humans
+
+   - Prevent recursive scripts from deleting important and unrelated files
+   - Protect against security issues
+   - Prevent infinite loops
+   - Avoid hardcoding values
+   - Ensure script performance
+   - Bail on malformed paths
+
+4. Testing
+
+   - Add tests for any cli changes
+   - Test inputs and outputs
+   - Ensure full branching, statements, and path coverage
+
+5. Files
+
+   - Always use .zsh extension for shell files
+   - Update the README.md if modifications/updates/changes are added to osa-cli tool scope which change/add/remove usage/description/args/options of the cli we need the cli doc to always match the actual implementation.
+
+6. Prompting/Responses
+   - Do not create or generate or modify files documenting changes made in prompt.
+   - Do not add comments indicating changes were made in response to a prompt.
+   - Avoid mentioning the use of AI or Copilot in code comments or documentation.
+   - Write code that is understandable and legible for humans
+
+## Setup
+
+    - this repo uses yarn for commands related to javascript/typescript code
+    - this repo requires tests and coverage to be 100%.
+    - this repo uses bats to run bash/zsh tests