Problem
The project create/edit UI currently only lets users configure setup.sh commands. Projects can also have a run.sh script, and the backend already has script discovery support for run.sh, but there is no project form field for entering or updating those commands.
Current UI references:
client/src/pages/ProjectSetup.tsx stores and submits setupCommands only.
client/src/pages/EditProject.tsx edits setupCommands only.
client/src/api.ts exposes project create/update payloads with setupCommands only.
Related backend reference:
server/lib/project-scripts.ts already checks for run.sh when resolving project scripts.
Expected behavior
Add project form support for run.sh commands alongside setup.sh:
- The create project form should include a field for run commands.
- The edit project form should load, update, and clear run commands.
- Project create/update API payloads should include the run commands field.
- Server-side project persistence should write
.coding-orchestrator/run.sh when commands are provided and remove it when cleared.
- UI labels/help text should make the difference between setup commands and run commands clear.
Acceptance criteria
- Creating a project with run commands creates
.coding-orchestrator/run.sh.
- Editing a project can add, update, and clear
.coding-orchestrator/run.sh.
- Existing
setup.sh behavior still works.
- TypeScript types are updated without broad or unsafe types.
- Relevant tests are added or updated for create/update behavior if test coverage exists for project persistence/routes.
Problem
The project create/edit UI currently only lets users configure
setup.shcommands. Projects can also have arun.shscript, and the backend already has script discovery support forrun.sh, but there is no project form field for entering or updating those commands.Current UI references:
client/src/pages/ProjectSetup.tsxstores and submitssetupCommandsonly.client/src/pages/EditProject.tsxeditssetupCommandsonly.client/src/api.tsexposes project create/update payloads withsetupCommandsonly.Related backend reference:
server/lib/project-scripts.tsalready checks forrun.shwhen resolving project scripts.Expected behavior
Add project form support for
run.shcommands alongsidesetup.sh:.coding-orchestrator/run.shwhen commands are provided and remove it when cleared.Acceptance criteria
.coding-orchestrator/run.sh..coding-orchestrator/run.sh.setup.shbehavior still works.