fix(organization): drop the redundant id input from org update/delete tools

[Tyagiquamar]

Problem

ORGANIZATION_UPDATE took id as the org to update but never checked it against ctx.organization?.id (the path-resolved, membership-verified org). A caller authenticated against org A could pass input.id for org B and reach boundAuth.organization.update with an org they may have zero membership in. As with ORGANIZATION_DELETE before #6501, Better Auth's own updateOrganization re-checks permission for the target org, so this is not a live bypass today — but it left the tool one vendored-dependency behavior away from one.

Fix

Per review, the parameter is gone rather than guarded: both ORGANIZATION_UPDATE and ORGANIZATION_DELETE drop id from their input schemas and take the org from requireOrganization(ctx), which is already resolved from the URL path — so there is nothing left to compare and nothing to spoof. tools-rest.ts parses with a non-strict z.object, so any agent still sending id keeps working and just gets it stripped. The shared tool-io.ts types and the settings UI's ORGANIZATION_DELETE call were updated to match.

Testing

• bun test apps/api/src/tools/organization/update.test.ts apps/api/src/tools/organization/delete.test.ts → 6 pass, 0 fail (cases now assert the update targets the org resolved from the request context).
• tsc --noEmit on packages/shared, apps/api, apps/web → exit 0.
• biome format on touched files → clean.

---

Summary by cubic

Drops the id input from ORGANIZATION_UPDATE and ORGANIZATION_DELETE, so the target organization always comes from the URL-resolved request context instead of client-supplied input. ORGANIZATION_DELETE is now idempotent: deleting an already archived organization returns success without updating it.

• The organization is now taken via requireOrganization(ctx), leaving no id to compare or spoof.
• Clients that still send id keep working because tools-rest parses non-strictly and strips the field.
• The settings UI's delete call and shared tool-io types were updated to match.

^{Written for commit 91969ab. Summary will update on new commits.}

[viktormarinho]

@Tyagiquamar instead of checking id, I would drop it from the input schema entirely and take the org from requireOrganization(ctx). It is already resolved from the URL path, so the param can only ever carry the value the server knows, and then there is nothing left to compare. Nothing in the repo passes it today (the settings UI calls the Better Auth client directly) and tools-rest.ts parses with a non-strict z.object, so any agent still sending id keeps working and just gets it stripped. delete.ts has the same redundant id.

[Tyagiquamar]

Done in 10aa5a3 — much cleaner this way, thanks. Both tools now drop id from the input schema and take the org from requireOrganization(ctx); ORGANIZATION_DELETE had the same redundant param and got the same treatment, including the shared tool-io.ts types and the settings UI caller (studio.call("ORGANIZATION_DELETE", {})). Verified locally: bun test on both tool files (6 pass), tsc --noEmit on shared/api/web, biome format clean.

[Tyagiquamar]

Small correction to my note above: the guard this PR originally added landed upstream independently via #6537, so I rebased onto current main and squashed — the change is now 074cddc (same content: both tools drop id and use requireOrganization(ctx), with the shared types and settings UI caller updated). Diff is conflict-free again.

[Tyagiquamar]

Merged the latest main: the already-archived no-op guard is adopted in ORGANIZATION_DELETE, and ORGANIZATION_UPDATE keeps merging into existing metadata so unrelated keys are preserved. Both tools still take the organization from requireOrganization(ctx) with the id input dropped. The organization tool tests pass after the merge.