Reduce AI smell in public docs, issues, and release notes

[Akotz89]

Problem

Some public-facing text reads like chat-derived AI output: broad claims, explanatory overreach, dramatic phrasing, and implementation storytelling that may distract from trust in the tool.

Acceptance criteria

• Review README, CHANGELOG, issue templates, release notes, and SECURITY.md for AI-sounding phrasing.
• Replace exaggerated or narrative language with concise operator-facing statements.
• Keep the AI-agent use case because it is core to the project, but avoid visible "AI wrote this" texture.
• Remove stale chat/session references unless they are converted into neutral regression-test context.
• Ensure the first viewport of the README explains what the tool does, who it is for, and the risk boundary without hype.

Verification

• Public docs still explain the value proposition clearly.
• A new reader can distinguish verified behavior from planned behavior.

[Akotz89]

Tracked in Linear: OPE-120 under the Shellfix Stabilization project.

[Akotz89]

Implemented in PR #27: #27

Evidence:

• CI passed: https://github.com/Akotz89/shellfix/actions/runs/26192621187/job/77064545247
• Local smoke passed: powershell -NoProfile -ExecutionPolicy Bypass -File ./test-ci-smoke.ps1 -ShimPath ./shim/out/powershell.exe -WslDistro Ubuntu-24.04 (5/5)
• Diff hygiene passed: git diff --check and git diff --cached --check
• GitHub labels reconciled: docs removed; documentation retained

Release impact: no runtime release required; documentation/process-only change.