chore: release 1.1.0

[MarkAlex1234]

Summary

Bumps every manifest and the pinned npx launchers (plugin, Gemini extension, action.yml) to 1.1.0, and cuts the changelog section. Highlights:

• the GitHub Action check mode
• the error-guide site
• the plugin folder with icon and listing links

After merge, v1.1.0 is tagged. release.yml publishes to npm (OIDC), lists the version in the MCP Registry, and builds the GitHub release with the signed tarball. The repository variable RELEASE_AS_DRAFT=true leaves that release as a draft, so it can be published with "Publish this Action to the GitHub Marketplace" ticked. v1 then moves to v1.1.0, so uses: continuous-actions/go-tokenless@v1 resolves.

Evidence

yarn check: 86/86 tests pass. The manifest tests check that all versions and pins match.

Merge danger

Door: one-way once tagged (npm versions are immutable).

Blast radius: release only.

[claude]

Release bump to 1.1.0 looks consistent. package.json, server.json (both fields), the plugin manifest, the Gemini extension and the action.yml npx pin all moved together, and no stale 1.0.0 pins remain outside test fixtures. The changelog section matches the PR description. I did not run the build or tests. No blocking issues.