chore(deps): bump Astryx core to 0.5.0

[testikun]

Summary

• Upgrade @astryxdesign/core from 0.4.5 to 0.5.0 across the root, UI, and Desktop packages.
• Upgrade @astryxdesign/theme-neutral to 0.5.0 so its strict peer dependency matches the new core version.
• Regenerate the versioned patch-package patch as @astryxdesign/core@0.5.0.
• Drop the two patch hunks now provided upstream (Kbd.js and useHotkeys.js).
• Update third-party notices and patch documentation.

Fixes#3753

Verification

• Clean npm ci applies the 0.5.0 patch successfully.
• @maka/ui tests: 227 passed.
• Desktop typecheck passed.
• Desktop main-process tests: 1,475 passed.
• npm run format:check passed.
• npm run lint passed.
• npm run check:third-party-notices passed.
• npm run check:stale passed.
• Desktop build passed.

Manual CJK IME interaction was not run in the automated environment; the affected UI package and Desktop suites pass.

简体中文摘要

本 PR 将 @astryxdesign/core 从 0.4.5 升级到 0.5.0，并同步升级具有严格 peer 依赖的 theme-neutral。重新生成了 0.5.0 版本 patch，删除已经被上游吸收的 Kbd.js 和 useHotkeys.js 两个 hunk，同时更新 lockfile、许可证清单和 patch 文档。

干净安装、UI 测试、Desktop 类型检查、Desktop 主进程测试、构建、lint、format 和 stale/许可证检查均已通过。

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex assisted with the dependency-upgrade analysis, patch regeneration, affected-file updates, regression verification, and PR preparation. The commit includes the Generated-by: OpenAI Codex trailer; the human contributor remains responsible for review and submission.

[Astro-Han]

Hi, Could you include the tools used in the commit?

[Astro-Han]

Also CI need fixing.

[Astro-Han]

I reviewed this head and found no blocking issues.

The bump to Astryx 0.5.0 correctly converges the two upstream-absorbed hunks and regenerates the remaining 5 hunks against the new dist, with THIRD_PARTY_NOTICES in sync. No new business logic.

Minor note: patch still carries 5 hunks (+36/-71 net reduction) — a maintained holding cost to be re-checked on next upstream bump (already documented).

No P0-P2.

简体中文

该头未发现阻断，剩余补丁持有成本可接受。

[Astro-Han]

I verified this rebased head.

The only change vs 11744146 is a LICENSE line updating the patch filename to 0.5.0.patch, matching the prior patch rename. No runtime changes beyond the previously reviewed Astryx 0.5.0 convergence. Previous P3 holding-cost note remains.

No P0-P2.

简体中文

该头为 LICENSE 同步重整，无新增阻断。

[Astro-Han]

Got a CI error need fixing:
Error: Generated Astryx theme is stale: maka.css, maka.js. Run "npm run astryx:theme" and commit the result.

[Astro-Han]

Update on cd90e76d07:

Only astryx-theme/maka.{css,js} refreshed vs 26b5365. No runtime changes beyond prior Astryx convergence.

No P0-P2.

简体中文

该头为主题产物刷新，无新增阻断。

[Astro-Han]

Update on 30d55520b4:

Only aria-current="page" → "true" test sync vs cd90e76d. No runtime changes beyond prior Astryx convergence.

No P0-P2.

简体中文

该头为测试断言同步，无新增阻断。

[testikun]

Follow-up fix pushed in 4340c6669.

Astryx 0.5.0 no longer exposed the nested DialogHeader title as the native dialog accessible name in the Storybook smoke environment. RemoteProjectDirectoryDialog now supplies an explicit aria-label using the same localized title, keeping the production dialog named across Astryx versions.

Local verification: Storybook build plus all 194 Storybook smoke stories pass; repository typecheck, format check, and lint pass. The Windows release check also passes on the new head.

简体中文

为远程项目目录对话框增加显式 aria-label，修复 Astryx 0.5.0 下 Storybook 无障碍审计找不到 Build Host 对话框名称的问题。

Generated-by: OpenAI Codex

[testikun]

Follow-up fix pushed in bdffa4f3c.

The failing Storybook story used a fixed 100ms wait after the optimistic checkbox flip. Under CI load, the persisted setting/readback can settle after that deadline even though the implementation is correct, producing a false failure. The story now polls for the confirmed persisted true state for a bounded 1s window and reopens the menu when Astryx closes it during the update.

Local verification: Storybook build plus all 194 smoke stories pass; typecheck, format check, and lint pass.

简体中文

该失败是 Storybook 故事固定等待 100ms 导致的竞态，不是业务逻辑失败。现在改为有界轮询持久化状态，兼容 CI 负载和菜单异步关闭。

Generated-by: OpenAI Codex

[Astro-Han]

One P1 inline on LICENSE; that is the only thing I would hold the merge for.

The rest of the bump verified clean: the aria-currentpage → true test updates track a deliberate upstream a11y correction in dist/TabList/Tab.js (and SideNavItem still emits page, so sidebar.css's selectors are correctly untouched), the aria-label fix is genuinely local because RemoteProjectDirectoryDialog is the only one of fourteen Dialog call sites that renders its DialogHeader conditionally, dropping the Kbd.js and useHotkeys.js patch hunks is safe because 0.5.0 carries both blank-UA-CH fixes verbatim, and the story change from a fixed 100ms wait to polling is a legitimate flake fix.

AI use: drafted with Claude Code (Opus 5); I verified every claim in it against the 0.4.5 and 0.5.0 package sources and the repo at bdffa4f3c before posting.

[Astro-Han]

P1 — LICENSE now misattributes the regenerated theme artifacts.

This PR bumps @astryxdesign/theme-neutral to 0.5.0 and regenerates maka.css and maka.js — the output really did change (#e33f4a → #c9303a for the error color, three places in each file). This line still says the redistributed artifacts are "generated theme artifacts based on Astryx theme-neutral v0.4.5", so after merge LICENSE attributes shipped generated material to a version it was not generated from. The line below was updated to @astryxdesign+core+0.5.0.patch, so the paragraph was edited and the version in this sentence was simply missed.

Please also check Theme revision: 110987b4505dc44119b94bed53d92b9840088a61 on line 233. If that pins the upstream commit the theme was generated from, it is stale for the same reason — I cannot tell which release that sha belongs to.

Worth noting why this is easy to miss rather than treating it as carelessness: this paragraph hand-carries three separate version facts — the core patch filename, the theme-neutral version, and the theme revision sha — whose real authorities live in package.json, the patches/ filename, and the upstream repository. Nothing binds the prose to any of them, and neither check:third-party-notices nor check:stale reads it, which is why CI is green here. The 0.4.0 → 0.4.5 bump updated this paragraph; this one updated a third of it. As long as the copy is synced by hand it will keep drifting.

Blocking only because LICENSE ships in the release and an incubating release vote reads it.

---

Automated review notice: This comment was posted by an automated review agent operated by Astro-Han. It is not an independent human review and does not replace one.

[testikun]

Fixed in 03774d58b, rebased onto the latest apache/main (2b4c0deaa).

• Updated the LICENSE attribution from theme-neutral v0.4.5 to v0.5.0.
• Updated Theme revision to ea888ef33283ea44e37817d36bc8e84a0568bc30, the commit behind Astryx tag v0.5.0.

The change is limited to these two LICENSE lines; all generated artifacts and runtime code are unchanged. The focused legal inventory test passes, and the repository ASF-source check is blocked locally only by the available Node runtime lacking stripTypeScriptTypes; CI remains authoritative.

简体中文：已修复 LICENSE 中过期的主题版本和 revision SHA，并基于最新主干重放后推送。

[Astro-Han]

I reviewed this head and found no blocking issues.

Bumps Astryx core 0.5.0 with regenerated theme artifacts and aligned a11y/story fixes; hosted test/audit/package/owner all SUCCESS.

No P0-P3.

简体中文

该头无阻断。

---

Automated review notice: This comment was posted by an automated review agent operated by Astro-Han. It is not an independent human review and does not replace one.

[Astro-Han]

Verified the fix in 03774d58b. Both facts are now correct, and the revision line was worse than I flagged: I resolved both shas against facebook/astryx, and the old 110987b4505d is chore: version packages for v0.4.0 — it was already pointing a release behind the prose that claimed v0.4.5. The new ea888ef33283 is release: v0.5.0 (#5435), so this is the first time the revision and the version in this paragraph actually agree. All five checks are green.

AI use: reviewed with Claude Code (Opus 5); I verified the diff, both upstream commits, and CI state myself before approving.