Contract-integration note: bridgelet-product-audit/integration-notes/freighter-api-version-pinning.md
Purpose:
Document the coupling between this package's pinned version and the actual browser extension users install independently.
This file should cover:
- Note the currently pinned version in frontend/package.json as a factual record.
- Discuss the general risk of a browser-extension-facing API package drifting from what a user's installed extension version actually implements.
- Cross-reference the corresponding checklist entry on dependency version review.
Scope: documentation-only addition to a new, standalone folder. No changes to frontend/ or mobile/ are needed to close this issue.
Part of the bridgelet-product-audit/ knowledge-base initiative (25/100).
Contract-integration note:
bridgelet-product-audit/integration-notes/freighter-api-version-pinning.mdPurpose:
Document the coupling between this package's pinned version and the actual browser extension users install independently.
This file should cover:
Scope: documentation-only addition to a new, standalone folder. No changes to frontend/ or mobile/ are needed to close this issue.
Part of the bridgelet-product-audit/ knowledge-base initiative (25/100).