[WIP] Fix changelog entries for version 3.3.1 and missing links

[Copilot]

• Fix CHANGELOG.md: rename [3.3.2] to [3.3.1]
• Fix CHANGELOG.md: add missing version comparison links (3.3.2, 3.3.0, 3.2.2, 3.2.1, 3.2.0, 3.1.0)
• Fix CONTRIBUTING.md: use approximate counts (~57, ~69, ~23)
• Fix CONTRIBUTING.md: clarify enum string literal matching for compliance framework
• Fix pbt-generator.ts: fix fast-check import to use default import
• Fix pbt-generator.ts: remove unnecessary import hypothesis line
• Fix test-generator.ts: make REQ- regex match IDs without middle letter group
• Fix visualization.ts: reference CHARACTER_LIMIT constant in truncation message
• Fix visualization.ts: extract buildDiagramTitle helper function
• Fix visualization.ts: improve rationale fallback message
• Fix visualization.ts: add guard before accessing acceptanceCriteria[0]
• Fix visualization.ts: extract CRITICAL_REQ_THRESHOLD and HIGH_REQ_THRESHOLD constants

Original prompt

Please apply the following diffs and create a pull request.
Once the PR is ready, give it a title based on the messages of the fixes being applied.

[{"message":"Version 3.3.2 is listed but version 3.3.1 is missing from the changelog. There should be an entry for version 3.3.1 between 3.3.2 and 3.3.0, or the version number should be corrected to 3.3.1 if that intermediate release didn't exist.","fixFiles":[{"filePath":"CHANGELOG.md","diff":"diff --git a/CHANGELOG.md b/CHANGELOG.md\n--- a/CHANGELOG.md\n+++ b/CHANGELOG.md\n@@ -5,7 +5,7 @@\n The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),\n and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).\n \n-## [3.3.2] - 2026-04-14\n+## [3.3.1] - 2026-04-14\n \n ### Security & Code Quality\n \n"}]},{"message":"The version comparison links at the bottom are incomplete. Links for versions 3.3.2, 3.3.0, 3.2.2, 3.2.1, 3.2.0, and 3.1.0 are missing. Add comparison links following the same pattern as existing entries to maintain changelog navigation consistency.","fixFiles":[{"filePath":"CHANGELOG.md","diff":"diff --git a/CHANGELOG.md b/CHANGELOG.md\n--- a/CHANGELOG.md\n+++ b/CHANGELOG.md\n@@ -417,6 +417,12 @@\n - Zod schema validation on all tool inputs\n - Published to npm (`specky-sdd`), GitHub Container Registry, and GitHub Releases\n \n+[3.3.2]: https://github.com/paulasilvatech/specky/compare/v3.3.0...v3.3.2\n+[3.3.0]: https://github.com/paulasilvatech/specky/compare/v3.2.2...v3.3.0\n+[3.2.2]: https://github.com/paulasilvatech/specky/compare/v3.2.1...v3.2.2\n+[3.2.1]: https://github.com/paulasilvatech/specky/compare/v3.2.0...v3.2.1\n+[3.2.0]: https://github.com/paulasilvatech/specky/compare/v3.1.0...v3.2.0\n+[3.1.0]: https://github.com/paulasilvatech/specky/compare/v3.0.0...v3.1.0\n [3.0.0]: https://github.com/paulasilvatech/specky/compare/v2.3.1...v3.0.0\n [2.3.1]: https://github.com/paulasilvatech/specky/compare/v2.3.0...v2.3.1\n [2.3.0]: https://github.com/paulasilvatech/specky/compare/v2.2.0...v2.3.0\n"}]},{"message":"The documentation claims specific counts (57 tools, 69 source files, 23 templates) which may become outdated as the codebase evolves. Consider using dynamic values or removing exact counts to reduce maintenance burden, or add a note indicating these are approximate values as of a specific version.","fixFiles":[{"filePath":"CONTRIBUTING.md","diff":"diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md\n--- a/CONTRIBUTING.md\n+++ b/CONTRIBUTING.md\n@@ -22,7 +22,7 @@\n \n ## Architecture Overview\n \n-Specky v3.3.0 is an MCP server that exposes **57 tools** organized into a 10-phase Spec-Driven Development pipeline. The codebase comprises **69 source files**, **23 templates**, and is structured as follows:\n+As of Specky v3.3.0, Specky is an MCP server that exposes **~57 tools** organized into a 10-phase Spec-Driven Development pipeline. The codebase comprises approximately **~69 source files** and **~23 templates**, and is structured as follows:\n \n ```\n src/\n"}]},{"message":"The example shows 'fedramp' added to the ComplianceFramework type, but the subsequent steps only add FEDRAMP controls to the compliance engine. The documentation should clarify that the enum update in the schema (Step 3) requires the exact string value to match what's added to the type definition.","fixFiles":[{"filePath":"CONTRIBUTING.md","diff":"diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md\n--- a/CONTRIBUTING.md\n+++ b/CONTRIBUTING.md\n@@ -332,7 +332,7 @@\n    ],\n    ```\n \n-3. Update the `complianceCheckInputSchema` in `src/schemas/quality.ts` to include the new framework in its enum.\n+3. Update the `complianceCheckInputSchema` in `src/schemas/quality.ts` to include the new framework in its enum, using the exact same string literal as the `ComplianceFramework` type and `FRAMEWORKS` key (for example, `\"fedramp\"`).\n \n 4. Add a `compliance.md` template section if needed, or the existing template will handle it generically.\n \n"}]},{"message":"The import statement uses named import syntax `{ fc }` but fast-check's default export is `fc`. This should be `import fc from \"fast-check\";` to correctly import the default export.","fixFiles":[{"filePath":"src/services/pbt-generator.ts","diff":"diff --git a/src/services/pbt-generator.ts b/src/services/pbt-generator.ts\n--- a/src/services/pbt-generator.ts\n+++ b/src/services/pbt-generator.ts\n@@ -458,7 +458,7 @@\n       ].join(\"\\n\");\n \n       const imports = [\n-        `import { fc } from \"fast-check\";`,\n+        `import fc from \"fast-check\";`,\n         `import { describe, it, expect } from \"vitest\";`,\n       ].join(\"\\n\");\n \n"}]},{"message":"The Python import statement for hypothesis is unnecessary since the module is not used directly in the generated code. Only the decorators and strategies from hypothesis are needed, which are already imported on lines 483-484.","fixFiles":[{"filePath":"src/services/pbt-generator.ts","diff":"diff --...