fix(contracts): reject project script ids that cannot form keybinding commands - #7947

💭 This looks like a schema change rather than an Effect service change, so I'm checking whether it fits existing conventions in keybindings.ts and orchestration.ts. There's a new ProjectScriptId schema constant added and referenced across files, but nothing that raises circular import or service-pattern concerns—just a backend validation addition covered by new tests.

1. browse_code — packages/contracts/src/keybindings.ts

2. browse_code — packages/contracts/src/orchestration.ts

💭 This looks more like a schema/validation change than an Effect service change, so most conventions don't strictly apply—the ProjectScriptId export and stricter validation replacing TrimmedNonEmptyString seem fine, backed by added tests. I'm checking whether there's any circular import concern with keybindings.ts. There's a potential real-world issue if script ids elsewhere are generated as UUIDs, since tightening the schema could reject existing persisted data—but that's outside the scope of Effect service conventions I'm checking, and tests were added for the behavior change, so I'll note it as an aside rather than a blocking concern and lean toward concluding things look clear.

3. git_tools — randomUUID|scriptId|ProjectScript\b

💭 I don't see any Effect service convention issues in this diff, so everything looks clear. I'll format the final response as JSON with a summary stating "All clear."