fix(web): restore the Archive action in the default sidebar thread menu - #6526

💭 I'm examining the diff to understand what changed in the React components and hooks, looking for any Effect service patterns or conventions like settlePromise or atom commands that might be involved. I'm checking whether the React code follows Effect service conventions, specifically looking at useThreadActions to see if archiveThread exists and whether confirmThreadArchive is available in the client settings—though those are compile-time concerns rather than convention violations. The real focus is on whether there are any Effect-related issues like improper ManagedRuntime usage. I'm noticing a conflict between the customer's request for a plain text response and the system's requirement for JSON output. The validation checks passed with no issues, so I should return a success state. I'll resolve this by using JSON format while making the summary field say "All clear" to honor the customer's intent.