[okJiang]

Summary

Use one exact Agent Service revision and one OpenAPI fingerprint for the whole SDK. Remove the four feature-specific revision exports and eight duplicate package fields, together with their repeated runner checks. Update the installed-package checks, frozen-contract readers, documentation and release summary to use the shared values.

TIDB_LINK_REVISION / tidbLinkRevision + tidbLinkOpenApiSha256

Cleanup 3 of 4, based on merged #11. The selected service revision, OpenAPI bytes and supported workflows do not change.

Public behavior verified

• Typechecking, all 123 SDK/installed-consumer tests, 11 contract checks and package-content checks pass.
• Installed consumers verify the shared values and absence of the retired exports and package fields.
• The service runner still rejects the wrong checkout and validates the exact clean revision and actual OpenAPI hash.
• The existing local controlled-service suite verifies the unified declaration; this does not certify a currently deployed URL.
• The release workflow parses, and its compatibility-summary step produces the expected revision and fingerprint without publishing.
• Documentation names the replacement values; no production credentials are included.

Evidence

Before: four feature groups repeated the same service identity and fingerprint. After: the same immutable contract and service evidence is checked against one shared declaration. Existing coverage is retained, and packed-consumer assertions now reject the removed fields.

Merge Danger

Door: two-way. Blast Radius: compatibility metadata.

Callers of the removed Provisioning, Realtime, Lifecycle or Text revision constants must use TIDB_LINK_REVISION; package readers use tidbLinkRevision and tidbLinkOpenApiSha256. A public npm lookup returned 404, which does not rule out private or Git consumers. No compatibility aliases, npm publication, release tags or service changes are included.