v4.130.2

Fix

• SDK / CLI deploy preflight: a refusal names the real reason when the project's tier is not the wallet's. Since 4.130.1 the preflight checks function limits against the tier of the organization that owns the project. When that tier differed from the wallet's own, the refusal's hint still said the limits came from the static fallback because tier status exposed no function caps, and suggested refreshing tier status. It now says the project's organization is on its tier and names the wallet's own organization's tier (or that it has none).