fix(webapp): scope development branches to each member

[carderne]

Summary

Allow each organization member to use the same development branch name without colliding with another member's environment. Fixes #4320.

Fix

Development branches now use the existing member-scoped project, slug, and organization-member key for upserts. Preview branches retain their project-wide shortcode behavior.

New development branches receive distinct shortcodes while keeping their readable, member-scoped slugs. Existing branches continue to resolve through the member-scoped key, so this requires no migration or backfill.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e9abdda

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Development branch upserts now generate member-scoped shortcodes using the branch slug and parent environment shortcode, require an organization member, and use an orgMemberId-based composite lookup key. Non-development branches retain their existing behavior. Tests cover concurrent creation by different members, shared slugs, distinct ownership, and idempotent retries.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers summary and fix, but it misses required template sections like Closes #issue, Checklist, Testing, Changelog, and Screenshots.	Add the missing template sections, including the issue link, checklist, testing steps, changelog, and screenshots placeholders.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The branch upsert changes let different members reuse the same dev branch name, matching #4320's collision fix.
Out of Scope Changes check	✅ Passed	The added test and changelog note are tied to the member-scoped dev branch fix, with no clear unrelated code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly summarizes the main change: scoping development branches to individual members.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/tri-12255-bug-cannot-use-dev-branch-name-that-is-in-use-by-another

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.