chore: prepare v1.1.1 release

[mohanagy]

Summary

• set the package and lockfile version to 1.1.1
• finalize the v1.1.1 changelog entry for [Compatibility] Preserve valid tool schemas across redaction and Claude proxying #397 and release tracker [Release] Publish v1.1.1 Claude Desktop compatibility patch #399
• update current-release installation and compatibility references
• pin the v1.1.0 protocol-evidence documentation contracts to the release where [Security] Bind stateless profile context to trusted per-chat authentication claims #376 and [Profiles] Implement opaque cross-instance stateless profile-context handles #377 landed

Exact base

This branch was rebased onto merged development commit 014e78027d99736cd1d502a08d2d71e16e2b7f15 after #398 passed exact-head CI and CodeRabbit review.

Security impact

No production security boundary is weakened. The candidate includes #398's reviewed schema-key redaction hardening: configured secrets, bearer values, and recognized provider tokens are redacted when they occur as JSON Schema object keys as well as values. The release-only commit changes version metadata, documentation, and historical release-contract assertions.

Validation commands and results

• npm run check:test-fixture — passed
• npm test — 1,948 passed, 34 skipped, 0 failed
• npm run typecheck — passed
• npm run lint — passed
• npm run build — passed
• npm run test:package — 31 passed
• npm run test:inspector — Inspector 2.1.0 interoperability passed
• npm run check:pack — 57-file package contract passed
• npm audit signatures — 280 verified registry signatures and 74 verified attestations

Publication boundary

This PR targets development. It does not publish and must not trigger a workstation npm publish. After this exact release metadata is merged, the only promotion PR will be development → main, followed by the protected exact-main GitHub Release workflow.

Tracks #399.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3055f1d4-b4ba-42c7-9e2a-8e154d744524

📥 Commits

Reviewing files that changed from the base of the PR and between 014e780 and caa8d64.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• CHANGELOG.md
• README.md
• docs/mcp-compatibility.md
• docs/presets-and-clients.md
• docs/whats-new-in-0.5.md
• package.json
• tests/authenticated-request-context-docs-contract.test.ts
• tests/profile-context-handle-docs-contract.test.ts
• tests/release-version.test.ts

---

📝 Walkthrough

Walkthrough

The package version is updated to 1.1.1. Release documentation and changelog entries use the new version. Contract tests distinguish the fixed 1.1.0 protocol release from the 1.1.1 package release.

Changes

1.1.1 Release Preparation

Layer / File(s)	Summary
Release metadata and documentation package.json, CHANGELOG.md, README.md, docs/*.md	The package version, installation commands, compatibility baseline, and release changelog are updated to 1.1.1.
Protocol release contract validation tests/authenticated-request-context-docs-contract.test.ts, tests/profile-context-handle-docs-contract.test.ts	The contract tests validate the fixed 1.1.0 protocol release instead of deriving the release from package.json.
1.1.1 release artifact validation tests/release-version.test.ts	Release tests now validate the 1.1.1 changelog entry and Claude Desktop tool-catalog compatibility details.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• mohanagy/miftah#394: Prepares a successive release with overlapping changelog contract tests and package documentation updates.
• mohanagy/miftah#104: Prepares a compatible patch release with related version, documentation, and release-artifact test changes.
• mohanagy/miftah#162: Strengthens release validation in tests/release-version.test.ts.

Suggested labels: documentation, area:mcp

Poem

I’m a rabbit with a release note bright,
Hopping from 1.1.0 to 1.1.1 tonight.
The docs line up, the tests agree,
Claude’s catalog now checks with glee.
Squeak, ship, and verify! 🐇

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Docstring Coverage	❌ Error	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the primary change: preparation of the v1.1.1 release.
Description check	✅ Passed	The description covers the summary, security impact, validation results, publication boundary, and issue tracking for the release preparation.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/399-v1.1.1

---

_{Comment @coderabbitai help to get the list of available commands.}

[mohanagy]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.