AIML-396: Preparation for v1.0.0 release

[ChrisEdwards]

Why This Change Exists

We're preparing to release v1.0.0 of the Contrast MCP Server. This is a major milestone release that represents months of work consolidating 27 inconsistently-named tools into 13 well-designed tools, fixing critical bugs, and adding significant new capabilities.

Before cutting the release, we need documentation that helps users understand:

1. What changed - A comprehensive changelog documenting breaking changes, bug fixes, and new features
2. What's available - A quick reference of all 13 tools so users can discover capabilities
3. How to release - Updated release documentation now that we're past 1.0

Approach We Chose

This PR focuses purely on documentation updates to prepare for the release:

1. CHANGELOG.md - Comprehensive release notes following Keep a Changelog format
2. README.md updates - Added "What's New" link and "Available Tools" quick reference
3. RELEASING.md updates - Removed outdated pre-1.0 versioning note, added example for MAJOR changes

Outcome of this Change

Users and maintainers now have:

• Complete documentation of all v1.0.0 changes (breaking changes, bug fixes, new features, performance improvements)
• Quick-reference table of all 13 tools organized by category
• Clear path to CHANGELOG for release history
• Updated release process documentation for semantic versioning

---

The Chain of Logic

Step 1: Document the Release (CHANGELOG.md)

The v1.0.0 release includes significant changes that users need to understand before upgrading:

Breaking Changes - Tool consolidation requires users to update their prompts:

• 27 tools → 13 tools with consistent naming
• app_name → appId parameter change
• sessionMetadataName/Value → sessionMetadataFilters JSON

Critical Bug Fixes - These were preventing core functionality:

• Date filtering caused HTTP 400 errors
• Status filtering was silently ignored
• Multi-word keyword search returned 0 results

New Capabilities - JSON metadata filtering, pagination, performance improvements

The CHANGELOG follows Keep a Changelog format with clear sections for each type of change.

Step 2: Make Tools Discoverable (README.md)

Users need to quickly understand what the MCP server can do. Added:

1. "What's New" section - Links to CHANGELOG for release history
2. "Available Tools" section - Table of all 13 tools organized by category:
   • Applications (2 tools)
   • Vulnerabilities (4 tools)
   • Libraries/SCA (2 tools)
   • Protection/ADR (2 tools)
   • Coverage (1 tool)
   • SAST (2 tools)

Step 3: Update Release Process (RELEASING.md)

The old documentation mentioned "pre-1.0 releases use 0.0.X versioning" which is now outdated. Updated to:

• Remove the pre-1.0 note
• Add example for MAJOR version changes (tool renames, parameter changes)

Step 4: Update Manual Test Documentation

Minor update to expected CVE counts in manual test files to reflect current test data.

---

What Changed

File	Change
CHANGELOG.md	NEW - 107-line comprehensive release notes for v1.0.0
README.md	Added "What's New" section with CHANGELOG link
README.md	Added "Available Tools" section with 13 tools in 6 categories
RELEASING.md	Removed pre-1.0 versioning note, added MAJOR change example
manual-tests/*.md	Updated expected CVE counts (72→70, 22→21, 79→77)

Key additions to README.md

## What's New

See [CHANGELOG.md](CHANGELOG.md) for the complete release history...

## Available Tools

The Contrast MCP Server provides 13 tools for security analysis...

### Applications
| Tool | Description |
|------|-------------|
| `search_applications` | Search applications by name, tag, or metadata filters |
| `get_session_metadata` | Get session metadata fields available for an application |
...

---

Test Coverage

This PR contains only documentation changes - no code changes requiring tests.

Verification performed:

• ✅ ls -la CHANGELOG.md - File exists
• ✅ Tool count verified: 13 tools match documentation
• ✅ make format && make check - Passes
• ✅ All links valid (CHANGELOG.md exists at repo root)

[ChrisEdwards]

The changes in this file just update the expectations to match the data in staging. No need to review as its not production code. I manually verified the numers in the contrast ui.

[ChrisEdwards]

Same with this file