Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/elements/content-sharing/hooks/useSharingService.ts`:
- Around line 95-97: The invite-success path dereferences currentUser
(currentUser.id) without a null check; update the logic where the object with
currentUser, isCurrentUserOwner, and ownerEmailDomain is built (the block
referencing currentUser and ownerId) to guard currentUser first — compute
isCurrentUserOwner only if currentUser exists (e.g., currentUser &&
currentUser.id === ownerId or optional chaining), and only append to
collaborators or access any currentUser properties when currentUser is non-null;
ensure the invite callback in useSharingService.ts skips collaborator mutations
or uses a safe fallback when currentUser is null.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/constants.js`:
- Line 174: The file contains TypeScript-only syntax (e.g., declare var
__VERSION__: string and exports like FIELD_LOGIN: 'login' = 'login') inside a
.js file causing Biome parse errors; either convert the file to TypeScript by
renaming src/constants.js to src/constants.ts and update all imports/usages
accordingly, or remove all TypeScript type annotations and declare statements
(replace patterns like "declare var __VERSION__: string;" and "export const
FIELD_LOGIN: 'login' = 'login';" with plain JS equivalents such as simple
const/exports) so the file is valid JavaScript; locate symbols like FIELD_LOGIN
and the declare __VERSION__ to ensure all TS syntax is handled consistently
across the file.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/elements/content-sharing/utils/__mocks__/ContentSharingV2Mocks.js`:
- Line 97: DEFAULT_USER_API_RESPONSE pairs the owner's id ('789') with the wrong
login (collabUser2.login); change the login property to mockOwner.login (or
mockOwnerEmail) so the entry with id '789' matches the owner's email; update the
mock object in ContentSharingV2Mocks.js (look for DEFAULT_USER_API_RESPONSE and
the login: collabUser2.login line) to use mockOwner.login to keep owner identity
consistent for domain-based collaborator gating tests.