feat(dashboard-api): implement upsertProjectLimits

[ben-fornefeld]

The first /v1/management handler to leave 501, now that project_limits (#3429) gives it somewhere to write.

What it does

Stores a project's effective limits exactly as sent. This side does no arithmetic — the caller owns plans and add-ons and has already resolved them. That's the point of the push, and it's what lets team_limits prefer this row over the tier it would otherwise compute from.

Contract: two missing dimensions

tiers gained default_free_disk_size_mb and max_disk_size_mb, and the view exposes both — but AdminControlPlaneProjectLimits carried only seven fields, so an override could never have set the other two.

Both added, required like the rest: a partial override has no meaning against a table whose columns are all NOT NULL.

This is a breaking contract change for the caller, and deliberately so — belt's exhaustruct rule is scoped to these generated types precisely to make a new field a build failure rather than a silently-zero payload.

Errors are distinguished, not collapsed

Failure	Status	Why
Foreign key violation	404	The team is the row's only FK, so it means the project is unknown here — not that the payload was bad
Check violation	400	The caller sent a combination the column set refuses. Currently free disk above the ceiling, which the request schema can't express
Anything else	500	Ours

Adds dberrors.IsCheckViolation alongside the existing helpers.

Cache invalidation, and a bug it uncovered

The team cache carries limits, so without invalidating it the write is invisible until the entry expires.

Review found InvalidateTeamCache was itself incomplete: it cleared team-<id> and the API-key hashes but not the per-member entries ValidateAuthProviderTeam populates — which hold a full Team including limits, and gate sandbox creation on the browser-session path. It now sweeps all three key kinds via a new GetTeamMemberIDs.

That was already a bug for the other caller: admin_kill_team_sandboxes invalidates after blocking a team and left the same entries stale.

The handler logs rather than fails: the row is already committed, and returning an error would invite a retry that can't improve on a stale cache.

Tests

Driven through the handler, asserting through team_limits rather than the table — so the two are proven wired together rather than assumed. Idempotency is covered because the caller retries.

The 404, the 400 and the cache invalidation are each mutation-verified: removing the FK mapping, the check mapping, or the invalidation call fails exactly the intended test.

Verification

packages/db and dashboard-api build, vet, test and lint clean. Codegen idempotent.

Also: finishing the management rename

#3361 moved these routes from /admin/v1 to /v1/management but touched only the path keys. The surface has carried three names for one concept ever since:

Layer	Was	Now
Paths	/v1/management/*	unchanged
Schemas	AdminControlPlane*	Management*
operationIds	upsertProject	managementUpsertProject
Handler methods	UpsertProject	ManagementUpsertProject
Tag	workspace-admin	control-plane-management
Handler files	one workspace_admin.go	one management_*.go per operation
Scheme	AdminJWTAuth	unchanged

AdminJWTAuth stays — it names a credential, not the surface, and sits beside AdminApiKeyAuth, which is a different scheme entirely. That adjacency is also why Admin on the schemas had become actively misleading rather than merely stale.

Folded in here rather than deferred because six more handlers are about to be written against these types, and the caller's call sites are about to multiply. It only gets more expensive.

The operationId prefix matters on a shared ServerInterface: without it these seven sit in the same namespace as the dashboard's own operations, and UpsertProject says nothing about which surface it answers on.

Breaks the caller on its next spec sync — seven method names and four type names in controlplanes/management.go. All mechanical, all compile failures, same coordination as the two required fields above.

Handler files are now one per operation, matching the rest of the directory (admin_users_delete.go, template_get.go, teams_list.go) rather than the single scaffolded file the seven arrived in. A PR implementing one handler touches one file, and the surface is legible from ls. sendNotImplemented moved to utils_management.go and loses a caller with each handler that lands.

---

Also drops six int64 conversions in packages/auth/pkg/types/teams.go that became redundant when #3429 widened TeamLimit. They were failing lint on main — after that change I checked db and dashboard-api but not the package that consumes the type.

[cursor]

PR Summary

Medium Risk
Changes affect enforced sandbox limits and auth cache freshness across API key and session paths; the limits contract and generated client names are breaking for the caller.

Overview
This PR implements PUT /v1/management/projects/{teamID}/limits, the first management route that persists data instead of returning 501. The handler stores caller-supplied absolute limits in project_limits (including newly required default_free_disk_size_mb and max_disk_size_mb), maps FK failures to 404 and CHECK violations to 400, and calls InvalidateTeamCache after a successful write so cached team limits update immediately. Auth InvalidateTeamCache is extended to drop per-member browser-session cache entries via GetTeamMemberIDs, not only team-id and API-key hashes. The OpenAPI surface is aligned under Management* types and management* operationIds (breaking for the control-plane client on spec sync); other management operations remain stubs. Handler layout is split one file per operation with shared sendNotImplemented.

^{Reviewed by Cursor Bugbot for commit feaa416. Bugbot is set up for automated code reviews on this repo. Configure here.}

[codecov]

❌ 6 Tests Failed:

Tests completed	Failed	Passed	Skipped
3585	6	3579	7

View the top 1 failed test(s) by shortest run time

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestCommandKillNextApp

Stack Traces | 278s run time

=== RUN   TestCommandKillNextApp
=== PAUSE TestCommandKillNextApp
=== CONT  TestCommandKillNextApp
    process_test.go:30: Build failed: {<nil> An internal error occurred. Please try again or contact support with the build ID. <nil>}
--- FAIL: TestCommandKillNextApp (278.03s)

View the full list of 5 ❄️ flaky test(s)

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestListDir

Flake rate in main: 21.68% (Passed 112 times, Failed 31 times)

Stack Traces | 0.53s run time

=== RUN   TestListDir
=== PAUSE TestListDir
=== CONT  TestListDir
--- FAIL: TestListDir (0.53s)
Executing command cat in sandbox ip2lge3gxxfpoe6jkeu4c (user: root)

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestListDir/depth_0_lists_only_root_directory

Flake rate in main: 25.93% (Passed 20 times, Failed 7 times)

Stack Traces | 0.02s run time

=== RUN   TestListDir/depth_0_lists_only_root_directory
=== PAUSE TestListDir/depth_0_lists_only_root_directory
=== CONT  TestListDir/depth_0_lists_only_root_directory
    filesystem_test.go:96: 
        	Error Trace:	.../tests/envd/filesystem_test.go:96
        	Error:      	Received unexpected error:
        	            	unavailable: 502 Bad Gateway
        	Test:       	TestListDir/depth_0_lists_only_root_directory
--- FAIL: TestListDir/depth_0_lists_only_root_directory (0.02s)

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestListDir/depth_1_lists_root_directory

Flake rate in main: 17.27% (Passed 91 times, Failed 19 times)

Stack Traces | 0.01s run time

=== RUN   TestListDir/depth_1_lists_root_directory
=== PAUSE TestListDir/depth_1_lists_root_directory
=== CONT  TestListDir/depth_1_lists_root_directory
    filesystem_test.go:96: 
        	Error Trace:	.../tests/envd/filesystem_test.go:96
        	Error:      	Received unexpected error:
        	            	unavailable: 502 Bad Gateway
        	Test:       	TestListDir/depth_1_lists_root_directory
--- FAIL: TestListDir/depth_1_lists_root_directory (0.01s)

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory)

Flake rate in main: 50.00% (Passed 1 times, Failed 1 times)

Stack Traces | 0.01s run time

=== RUN   TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory)
=== PAUSE TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory)
=== CONT  TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory)
    filesystem_test.go:96: 
        	Error Trace:	.../tests/envd/filesystem_test.go:96
        	Error:      	Received unexpected error:
        	            	unavailable: 502 Bad Gateway
        	Test:       	TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory)
--- FAIL: TestListDir/depth_2_lists_first_level_of_subdirectories_(in_this_case_the_root_directory) (0.01s)

github.com/e2b-dev/infra/tests/integration/internal/tests/envd::TestListDir/depth_3_lists_all_directories_and_files

Flake rate in main: 19.40% (Passed 54 times, Failed 13 times)

Stack Traces | 0.01s run time

=== RUN   TestListDir/depth_3_lists_all_directories_and_files
=== PAUSE TestListDir/depth_3_lists_all_directories_and_files
=== CONT  TestListDir/depth_3_lists_all_directories_and_files
    filesystem_test.go:96: 
        	Error Trace:	.../tests/envd/filesystem_test.go:96
        	Error:      	Received unexpected error:
        	            	unavailable: 502 Bad Gateway
        	Test:       	TestListDir/depth_3_lists_all_directories_and_files
--- FAIL: TestListDir/depth_3_lists_all_directories_and_files (0.01s)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: da55e1e3c1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".