feat(claude): show SDK prompt suggestions as ghost text in the composer - #8524

💭 I'm looking at the diff to check for Effect service convention violations, scanning through the changed files across mobile, server orchestration, provider adapters, and web components. This appears to be a feature addition for prompt suggestions rather than an Effect service refactor, so the conventions may not strictly apply here—but I still want to verify how Effect, Stream, Fiber, and Random are imported in the ClaudeAdapter test to make sure they're consolidated from "effect" properly.

1. git_tools — ^import",

2. browse_code — apps/web/src/lib/promptSuggestion.ts

💭 That helper looks fine on its own. Now I'm checking the imports in the touched Effect service files like ClaudeAdapter.ts and ProviderRuntimeIngestion.ts to see if the diff needs to add any there, and verifying the test file consolidates its imports from "effect".

3. browse_code — apps/server/src/provider/Layers/ClaudeAdapter.test.ts

4. browse_code — packages/contracts/src/providerRuntime.ts

💭 The ClaudeAdapter.ts changes look consistent with existing patterns, just adding a mutable session field and an Effect.fn handler without introducing new services or errors. I'm now checking whether ChatComposer.tsx and ComposerPromptEditor.tsx follow the repo's import conventions, since they're plain React rather than Effect services. The mutable field on the context isn't wrapped in an Effect Ref, so I want to check ClaudeSessionContext for other mutable fields to see if that's the established pattern here.

5. browse_code — apps/server/src/provider/Layers/ClaudeAdapter.ts

💭 The other changes look fine too - the ingestion function addition is a straightforward pure function case, and the React components don't introduce any Effect runtime concerns. I don't see any runPromise or Layer.succeed additions in the diff, so this review comes back clean.