fix: reconcile v2.2 integration contracts

[maziyarpanahi]

Pull Request

Description

Reconciles the cross-PR contracts exposed only after the v2.2 milestone branches were combined. This keeps generated schemas, public compatibility shims, offline-network policy, test expectations, and the dependency lock in sync with the merged source tree.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• Test addition/improvement

Changes Made

• Refresh the generated MCP tool schema and combined dependency lock.
• Restore explicit FHIR bulk exports, service error/signing compatibility, and opt-in network allowlisting.
• Remove stale CLI aliases and update golden-fixture, grounding, and public-orchestrator tests for the merged APIs.

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this change with different models/inputs

Validation: 12,086 passed, 105 skipped in the full Python suite; 76 focused tests passed; strict MkDocs build passed; make format, make lint, make format-check, and uv lock --check passed.

Documentation

• I have updated the documentation accordingly
• I have added docstrings to new functions/classes
• I have updated the CHANGELOG.md

No documentation or changelog change is required for this integration-only repair.

Code Quality

• I ran make format, make lint, and make format-check
• For Swift/OpenMedKit changes, I ran make format-swift and make lint-swift
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

Dependencies

• I have not added any new dependencies
• OR I have added new dependencies and they are justified because: ____

The lockfile only catches up with the already-merged fhir extra.

Checklist

• I have read the contributing guidelines
• My commits have clear, descriptive messages
• I have squashed/organized my commits appropriately

Related Issues

Related to the v2.2 milestone integration audit; no standalone issue is closed by this PR.

Screenshots/Examples

Not applicable.

[maziyarpanahi]

Merged after exact-head validation at c84dab4. Validation: full Python suite (12,086 passed, 105 skipped), 76 focused integration tests, canonical Ruff format/lint/format-check gates, uv lock check, strict MkDocs build, and diff checks. The resulting master tree matches the validated candidate tree exactly.