chore: strict markdownlint, deep-link fixes, and editor guardrails

[iplaycomputer]

chore: strict markdownlint, deep-link fixes, and editor guardrails

Summary

Enforce a strict markdownlint baseline, standardize deep-link anchors across Scenarios → KB/Lab, and align editor behavior to minimize visual churn. Formatting-only; no procedure changes.

Linked Artifacts (relative paths)

• Ticket(s)
  • account-locked-out.md
  • cannot-print-to-shared-printer.md
  • computer-running-slow-lagging.md
  • outlook-disconnected-password-prompts.md
• KB
  • account-lockout-reset.md
  • printer-queue-clearing.md
  • workstation-performance-triage.md
  • outlook-reconnect-after-update.md
• Lab
  • print-queue-stuck.md
  • resource-spike-triage.md
  • mailhog-connectivity.md
• Scenario
  • account-lockout-reset.md
  • printer-queue-clearing.md
  • workstation-performance-triage.md
  • outlook-reconnect-after-update.md

Also touched (templates/docs)

• .markdownlint.jsonc
• .markdownlint-cli2.jsonc
• .markdownlintignore
• CONTRIBUTING.md
• 000.scenario-template.md
• 000.lab-template.md
• 000.ticket-template.md
• README.md
• README.md

Checklists

• Content

  • Uses the correct template (copied from 000.*-template.md)
  • Clear, reproducible steps and plain language
  • Relative links resolve inside the repo
  • Avoid duplication across modules (KB = productized steps; Lab = full commands + Verification; Scenario = flow/success, links only)
  • Deep link to sections where applicable (KB → #resolution-steps, Lab → #verification)

• Metadata

  • Owner set; Last Reviewed and Next Review Due (KB/Lab)
  • Escalation Path filled (Ticket)
  • Metrics block added if useful (see docs/METRICS.md)

• Quality

  • Verification steps included (expected outputs / pass-fail)
  • Anchors exist and resolve (KB “Resolution Steps”, Lab “Verification”)
  • Scenario (if present) ties Ticket → KB → Lab and defines success criteria

Labs (if included)

• Dedicated “Verification” section with expected outputs
• Images pinned if using containers; HTTP services include a simple healthcheck when applicable
• Assets stored under labs/<lab>/assets/

KBs (if included)

• Brief (1–2 lines) verification; link to related Lab for full commands

Scenarios (if included)

• Uses deep links to KB “Resolution Steps” and Lab “Verification” (no step duplication)

Notes

Changes

• Set strict markdownlint baseline; disabled only:
  • MD013 (line length), MD025 (multiple top-level headings), MD033 (inline HTML),
  • MD009 (trailing spaces), MD041 (first line heading), MD051 (link fragments)
  • MD029 style set to “ordered” to reduce renumbering churn
• Added repo-level config/parity:
  • .markdownlint-cli2.jsonc with glob/ignore config (ignores .github/**/*.md and README.md)
  • .markdownlint.jsonc rules as above; .markdownlintignore to match editor behavior
• Structural fixes across docs:
  • Normalized spacing around headings/lists/fences (MD022/MD031/MD032)
  • Converted bold-only pseudo-headings to real headings where present (MD036)
  • Replaced bare URLs with angle-bracketed links (MD034) where needed
• Deep-link alignment:
  • Scenarios link to KB “Resolution Steps” and Lab “Verification” anchors
  • Removed duplicated steps across modules
• Contributor experience:
  • CONTRIBUTING.md: added “Local Lint (Optional)” and a pre-commit hook tip
  • README excluded from lint to avoid emoji/formatting churn

Rationale

• Anchor stability and consistent formatting reduce merge noise and broken links.
• Editor parity and scoped ignores prevent unnecessary diffs and preserve readability.

How to Verify (for reviewers)

• Local: run markdownlint (or use the provided local command in CONTRIBUTING). Expect 0 errors.
• Manual: open each Scenario and click the KB/Lab deep links; confirm anchors jump to “Resolution Steps” and “Verification.”
• Confirm no procedural content changes—only formatting/structure.