Chore: prepare 0.4.14 release

[ivory-code]

Summary

Prepare QAMap 0.4.14 by synchronizing package and plugin versions, documenting the merged QA improvements, recording the completed release gates, and updating the post-release roadmap.

Behavioral Contract

No new analyzer behavior is introduced by this release-preparation PR. The 0.4.14 package exposes the already merged delivery-integrity, runtime-activation, intent-isolation, removed-UI, and stable agent-context behavior under one synchronized version.

The release documentation keeps static QA recommendations and generated drafts separate from executed product QA. npm publication, Git tagging, the GitHub Release, and any OpenAI directory replacement remain post-merge actions.

Evidence

Closes #208.

Release evidence:

• 382/382 unit and integration tests passed
• 33/33 static recommendation contracts passed
• 10/10 context identity and reuse checks passed
• 3/3 execution contracts passed and caught all three seeded regressions
• coverage reached 90.30% lines, 87.06% branches, and 95.80% functions
• plugin metadata validation and isolated package smoke passed
• the 0.4.14 package preview contains 195 files

Checks

• Focused regression test
• pnpm test
• pnpm bench:ci for inference, routing, trace, or output
• pnpm bench:execution for E2E compiler or execution fixtures
• pnpm scan for scanner, security, or repository policy
• pnpm plugin:check and pnpm plugin:smoke for plugin changes
• Documentation links and commands verified

Public OSS Check

• No private repository, source, path, customer data, credential, or internal smoke output is included.
• Shared inference has unrelated positive and negative coverage, or this is not applicable.
• User-facing commands and claims match actual behavior.

Review Notes

The full pnpm release:check gate passed end to end. The focused contributor-documentation regression passed 7/7 after the final copy update, plugin submission metadata still reports version 0.4.14, and a final package dry run passed.

QAMap's static self-analysis remained not-run and selected only the general repository test command for this release diff. The stronger release verdict therefore comes from the repository-owned release gate above.