fix(docs): resolve markdown lint and link errors

- auto-fix blanks-around-lists and blanks-around-fences violations
- add LICENSE.md and ISSUE_TEMPLATE.md to lint ignores
- fix line length and emphasis-as-heading in README
- update Azure CLI URL to learn.microsoft.com

📝 - Generated by Copilot

# Conflicts:
#	.github/ISSUE_TEMPLATE.md
#	README.md

Author: WilliamBerryiii

.github/copilot-instructions.md

@@ -13,20 +13,24 @@ Items in **HIGHEST PRIORITY** sections from attached instructions files override
 **Artifacts:** Do not create or modify tests, scripts, or one-off markdown docs unless explicitly requested.
 
 **Comment policy:** Never include thought processes, step-by-step reasoning, or narrative comments in code.
+
 * Keep comments brief and factual; describe **behavior/intent, invariants, edge cases**.
 * Remove or update comments that contradict the current behavior. Do not restate obvious functionality.
 * Do NOT add temporal or plan-phase markers (e.g. "Phase 1 cleanup", "... after migration", dates, or task references) to code files. When editing or updating any code files, always remove or replace these types of comments.
 
 **Conventions and Styling:** Always follow conventions and styling in this codebase FIRST for all changes, edits, updates, and new files.
+
 * Conventions and styling are in instruction files and must be read in with the `read_file` tool if not already added as an `<attachment>`.
 
 **Proactive fixes:** Always fix problems and errors you encounter, even if unrelated to the original request. Prefer root-cause, constructive fixes over symptom-only patches.
+
 * Always correct all incorrect or problematic conventions, styling, and redundant and/or misleading comments.
 
 **Deleting files and folders:** Use `rm` with the run_in_terminal tool when needing to delete files or folders.
 
 **Edit tools:** Never use `insert_edit_into_file` tool when other edit and file modification tools are available.
 
 **Memory and tracking work**: Always track work in Beads instead of Markdown.
+
 * All upcoming work, tracked work, issues, plans, todos, phases, tasks, and memory must always use the mcp_beads tools.
 * Don't ever use git commands for anything related to the mcp_beads tools and beads in general, its at the user's discretion when to use git commands and tools.

.github/instructions/commit-message.instructions.md

@@ -38,7 +38,6 @@ Scopes MUST be one of the following:
 - `(src)`
 - `(deploy)`
 
-
 ## Description
 
 - Description MUST be short and LESS THAN 100 bytes
@@ -62,7 +61,7 @@ For larger changes only:
 
 - Footer MUST start with a blank line
 - Must include an emoji that represents the change
-- Must end with ` - Generated by Copilot`
+- Must end with `- Generated by Copilot`
 
 ## Example Complete Commit Message - Large
 

.markdownlint-cli2.jsonc

@@ -2,7 +2,8 @@
   "ignores": [
     "**/node_modules/**",
     ".copilot-tracking/**",
-    "venv/**"
+    "venv/**",
+    "LICENSE.md"
   ],
   "config": {
     "default": true,

LICENSE.md

@@ -18,4 +18,4 @@
     AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-    SOFTWARE
+    SOFTWARE