What/Why/How?

join --prefix-components-with-info-prop can leave invalid discriminator mapping refs when a schema name contains the same substring as the prefix (#1451).
The join ref-rewrite logic used name.includes(componentsPrefix), which incorrectly treated names like CreateSomethingRequest as already prefixed when prefix is Something.
This change updates the discriminator mapping rewrite check to only skip refs that already start with the real prefix format (<prefix>_), and adds a regression unit test to cover this case.

Reference

• Join does not add component prefix to discriminator mapping if the name of the schema coincidentally contains the prefix. #1451

Testing

• Ran unit tests for join command:
  • npm run unit -- packages/cli/src/__tests__/commands/join.test.ts --coverage=false
• Verified regression behavior explicitly:
  • test fails with old includes(...) logic
  • test passes with updated startsWith(prefix + '_') logic

Screenshots (optional)

N/A

Check yourself

• Code changed? - Tested with Redoc/Realm/Reunite (internal)
• All new/updated code is covered by tests
• New package installed? - Tested in different environments (browser/node)
• Documentation update considered

Security

• The security impact of the change has been considered
• Code follows company security practices and guidelines