chore: lint & update Markdown templates

Author: mobilemind

.github/BRANCH_PROTECTION.md

@@ -9,42 +9,51 @@ This document outlines the recommended branch protection rules and GitHub Action
 ### Recommended Settings:
 
 #### 1. Require Pull Request Reviews
+
 - **Require approvals**: 1 approval minimum
 - **Dismiss stale reviews**: Yes (when new commits are pushed)
 - **Require review from Code Owners**: Optional (if CODEOWNERS is used)
 
 #### 2. Require Status Checks to Pass
+
 **Enable**: Require status checks to pass before merging
 
 **Required status checks** (all must pass):
+
 - `Lint filter list files` (from lint-filters.yml)
 - `Lint JSON files` (from lint-json.yml)
 - `Lint Markdown files` (from lint-markdown.yml)
 - `Lint YAML files` (from lint-yaml.yml)
 
 **Additional settings**:
+
 - ✅ Require branches to be up to date before merging
 - ✅ Do NOT require approval to run workflows on PRs from contributors
   - This allows checks to run automatically without maintainer approval
   - Workflows already have minimal permissions (`contents: read`)
   - No write access or secrets are exposed
 
 #### 3. Require Conversation Resolution
+
 - **Enabled**: Require all conversations to be resolved before merging
 
 #### 4. Require Signed Commits (Optional but Recommended)
+
 - **Enabled**: Require commits to be signed
 - Enhances security by verifying commit authenticity
 
 #### 5. Require Linear History
+
 - **Enabled**: Prevent merge commits
 - Keeps history clean with rebase/squash merges
 
 #### 6. Include Administrators
+
 - **Enabled**: Apply rules to administrators
 - Ensures consistency and prevents accidental bypasses
 
 #### 7. Restrict Pushes
+
 - **Allow force pushes**: No
 - **Allow deletions**: No
 
@@ -64,13 +73,15 @@ All workflows already implement security best practices:
 ### Why `pull_request` is Safe
 
 The workflows use `pull_request` trigger which:
+
 - ✅ Runs in the context of the PR branch (not main)
 - ✅ Does not have access to repository secrets
 - ✅ Only has `contents: read` permission
 - ✅ Cannot modify the repository
 - ✅ Safe to run without approval for external contributors
 
 Using `pull_request` instead of `pull_request_target` means:
+
 - Checks run automatically on all PRs
 - No maintainer approval needed to run checks
 - Malicious PRs cannot access secrets or write to the repo
@@ -117,6 +128,7 @@ Current configuration in `.github/dependabot.yml`:
 ### Step 2: Verify Workflow Security
 
 All workflows already have proper security:
+
 - ✅ Minimal permissions set
 - ✅ Using `pull_request` trigger (safe for external contributors)
 - ✅ No secrets exposed

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,37 +7,52 @@ assignees: ''
 ---
 
 ## Bug Description
+
 <!-- A clear and concise description of what the bug is -->
 
 ## Steps to Reproduce
-1. Go to '...'
-2. Click on '...'
-3. Scroll down to '...'
-4. See error
+
+1. Launch lesson or course…
+2. Take quiz… or Progress through lesson…
+3. Submit item/score/completion
+4. See warning/error… or View results/report in system…
 
 ## Expected Behavior
+
 <!-- A clear and concise description of what you expected to happen -->
 
 ## Actual Behavior
+
 <!-- What actually happened -->
 
 ## Screenshots
+
 <!-- If applicable, add screenshots to help explain your problem -->
 
 ## Environment
+
 <!-- Please complete the following information -->
+
 - **Browser:** [e.g., Chrome, Firefox, Safari]
 - **Browser Version:** [e.g., 120. 0.6099.109]
-- **Operating System:** [e. g., macOS 14.2, Windows 11, Ubuntu 22.04]
-- **Extension Version:** [e.g., 1.0.0]
+- **Operating System:** [e. g., iOS 26, macOS 26, Windows 11, Ubuntu 22.04]
+- **Content Authoring Tool:** [e. g., Adobe Captivate, Articulate Storyline, Lectora, etc]
+- **LMS/LRS:** [e. g., Cornerstone OnDemand, Docebo, SAP SuccessFactors, etc]
 
 ## Filter Lists Used
+
 <!-- Which filter lists are you using? -->
-- [ ] moat-lms-blocker default filters
-- [ ] Custom filters (please describe)
+
+- [ ] SCORM 1.2
+- [ ] SCORM 2004
+- [ ] xAPI
+- [ ] cmi5
+- [ ] AICC
 
 ## Additional Context
+
 <!-- Add any other context about the problem here -->
 
 ## Possible Solution
+
 <!-- Optional:  Suggest a fix or reason for the bug -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,16 +7,21 @@ assignees: ''
 ---
 
 ## Feature Description
+
 <!-- A clear and concise description of the feature you'd like -->
 
 ## Problem it Solves
+
 <!-- Describe the problem this feature would solve -->
 
 ## Proposed Solution
+
 <!-- Describe how you envision this feature working -->
 
 ## Alternatives Considered
+
 <!-- Describe any alternative solutions or features you've considered -->
 
 ## Additional Context
-<!-- Add any other context, mockups, or examples about the feature request
+
+<!-- Add any other context, mockups, or examples about the feature request, or tools or systems it works with -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +1,9 @@
 ## Description
+
 <!-- Provide a brief description of the changes in this PR -->
 
 ## Type of Change
+
 <!-- Mark the relevant option with an "x" -->
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
@@ -13,24 +15,28 @@
 - [ ] Test update
 
 ## Related Issues
+
 <!-- Link to related issues using #issue_number -->
 Closes #
 
 ## Changes Made
+
 <!-- List the specific changes made in this PR -->
 
 - 
 - 
 - 
 
 ## Testing
+
 <!-- Describe the testing you've done -->
 
 - [ ] I have tested these changes locally
 - [ ] All existing tests pass
 - [ ] I have added tests for new functionality
 
 ## Checklist
+
 <!-- Mark completed items with an "x" -->
 
 - [ ] My code follows the project's style guidelines
@@ -41,7 +47,9 @@ Closes #
 - [ ] I have checked my code and corrected any misspellings
 
 ## Screenshots (if applicable)
+
 <!-- Add screenshots to help explain your changes -->
 
 ## Additional Notes
+
 <!-- Any additional information that reviewers should know -->