docs: add stable 0.92.0 changelog

[Leeeon233]

Risk: 🟢 low | Confidence: high — two localized changelog entries; Chinese copy confirmed and bilingual release metadata validated.

Related issue

Refs #439

Problem / pressure

The next stable client release needs matching Chinese and English public notes, including attribution for merged community contributions.

Summary

Add site-docs/content/changelog/{zh,en}/20260907.mdx for candidate 0.92.0. Chinese copy follows the confirmed concise format; English conveys the same changes. Both end with the contributor credits. The version remains subject to Release Please's final output.

Frozen public base: 4fa35d7f76ef4ffc83ecfbffe27a328cec6039e3. Only these two documents change; product and recursive submodule source stays fixed.

Before / after

Before: no 0.92.0 public entry. After: matching 2026-09-07 entries describing live session creation cards, Skills search, HTML downloads, and agent/chat/file preview improvements.

Included public PRs and contributor attribution

#439 #447 #148 #367 #286 #442 #440 #428 #409 #410 #416 #402 #386 #88 #213 #342 #360 #372 #431 #437 #413 #401

Thanks to @audichuang, @slashdevcorpse, @tommy0103, @Pleasurecruise, @hasak21, @specter119, @Astro-Han, @wibus-wee, and @zxch3n. The changelog keeps the credits together at the end.

Test plan

• Prettier passed for both MDX files.
• Production Electron changelog loader accepted exact version 0.92.0, date 2026-09-07, unique entries for English and Chinese, nonempty bodies, and size limits.
• Checked that both languages contain the same contributor handles and three feature / nine improvement bullets.
• Diff whitespace and two-file scope checked; no recursive gitlinks change.
• Product source was already verified; this documentation-only change uses focused release-note validation without repeating product tests or a site build.

Context handoff

Instructions for reviewing agents

• Review focus: Compare the two new entries for equivalent meaning, exact version/date, and complete contributor credits.
• Decisions to challenge: Keep task-time display and in-app attachment retention claims within the actual merged fixes' scope.
• Plausible failures / evidence gaps: Release Please may choose a different final version, requiring a metadata correction before release.

Authoring context

• User goal / directives: Publish concise bilingual stable notes and acknowledge public contributions.
• Constraints / non-goals: Limit the diff to the two changelog files; preserve all product source and submodule pins.
• Risk-bearing decisions: 0.92.0 is a candidate derived from the feature range since 0.91.1 and remains subject to the generated release output.
• Destructive or irreversible behavior: This adds public documents only and does not publish application artifacts or change stored user data.
• Deliberately not done or tested: No product or site rebuild for a text-only addition; release-note parsing and formatting directly validate the changed contract.
• Unknowns / confidence: Copy and metadata are verified; only the final generated release version remains provisional.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-07T02:11:01.509929Z	02fc97c	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.