fix(sites): stop reading the framework start command

[HarshMN2345]

What

The UI is unchanged. This removes the code that read startCommand off a framework adapter — a field the SDK never declared and the API no longer sends — plus a bug where a start command survived a framework change.

Pairs with appwrite/appwrite#13194, which stops listFrameworks shipping the internal command. No SDK regeneration needed: Models.FrameworkAdapter already declares exactly key, installCommand, buildCommand, outputDirectory, fallbackFile, which is what the endpoint now returns.

The dead reads

src/lib/stores/sites.ts declared:

export type FrameworkAdapterWithStartCommand = Models.FrameworkAdapter & {
    startCommand?: string;
};

Every create flow cast the adapter to that type and used adapter.startCommand to prefill the input and fill the placeholder. Once the API stops sending it, all of those resolve to undefined — the prefill silently does nothing and Reset restores a value that does not exist. Gone, along with the cast.

The bug

Changing framework or adapter kept the previous framework's start command in state, and update() submitted it against the new runtime. Previously startCommand = data.startCommand masked this by resetting the field from adapter data; removing that read exposed it.

• cleared when the framework or adapter changes, restored from the site when switching back to its original adapter
• submitted only for the ssr adapter, matching the fallbackFile line beside it

Not included

The earlier revision of this PR hid the field in the create flows and moved it under an Advanced section in settings. Dropped per Eldad — the UI stays exactly as it is.

Verification

npm run check — 0 errors, 87 warnings (all pre-existing). Prettier clean.

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Our Discord community has grown to 24K developers, and counting

[greptile-apps]

Greptile Summary

The PR removes unsupported framework start-command defaults from site creation and moves the stored command into an advanced settings section.

• Removes start-command inputs and payload fields from all site-creation paths.
• Removes the unsupported framework-adapter type extension.
• Clears or conditionally submits stored start commands when framework and adapter settings change.

Confidence Score: 4/5

The PR is not yet safe to merge because adapter transitions after a framework change can restore and submit the previous framework's incompatible start command.

The attempted fix clears the command on the initial framework change, but the later adapter-change branch restores site.startCommand solely by matching the original adapter key, leaving the previously reported stale-command failure reachable.

Files Needing Attention: src/routes/(console)/project-[region]-[project]/sites/site-[site]/settings/updateBuildSettings.svelte

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/sites/site-[site]/settings/updateBuildSettings.svelte	Moves the SSR start command under Advanced and attempts to clear stale values, but a framework change followed by adapter transitions can restore the original command.
src/routes/(console)/project-[region]-[project]/sites/create-site/configuration.svelte	Removes the unsupported start-command field and adapter cast from the shared creation configuration.
src/routes/(console)/project-[region]-[project]/sites/create-site/deploy/+page.svelte	Removes start-command URL handling, rendering, defaults, and create payload submission.
src/routes/(console)/project-[region]-[project]/sites/create-site/manual/+page.svelte	Stops reading and submitting adapter start commands during manual site creation.
src/routes/(console)/project-[region]-[project]/sites/create-site/repositories/repository-[repository]/+page.svelte	Stops reading and submitting adapter start commands during repository-backed creation.
src/lib/stores/sites.ts	Removes the unsupported FrameworkAdapterWithStartCommand type extension.

Prompt To Fix All With AI

### Issue 1
src/routes/(console)/project-[region]-[project]/sites/site-[site]/settings/updateBuildSettings.svelte:114
**Old start command gets restored**

When an SSR site is changed to another framework and its adapter is then changed away from and back to SSR, this branch restores `site.startCommand` solely because the adapter key matches the original adapter. The subsequent update submits the old framework's command for the newly selected framework, causing deployments to use an incompatible entrypoint.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (3): Last reviewed commit: "Clear the start command when the framewo..." | Re-trigger Greptile}

[greptile-apps]

Old start command gets restored

When an SSR site is changed to another framework and its adapter is then changed away from and back to SSR, this branch restores site.startCommand solely because the adapter key matches the original adapter. The subsequent update submits the old framework's command for the newly selected framework, causing deployments to use an incompatible entrypoint.

Knowledge Base Used: Functions and Sites

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/routes/(console)/project-[region]-[project]/sites/site-[site]/settings/updateBuildSettings.svelte
Line: 114

Comment:
**Old start command gets restored**

When an SSR site is changed to another framework and its adapter is then changed away from and back to SSR, this branch restores `site.startCommand` solely because the adapter key matches the original adapter. The subsequent update submits the old framework's command for the newly selected framework, causing deployments to use an incompatible entrypoint.

**Knowledge Base Used:** [Functions and Sites](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/console/-/docs/project-functions-sites.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.