fix: close filesystem authority startup race

[NWYLZW]

Summary

• Fix the macOS filesystem asset-authority startup race: a trusted local request arriving during recovery is retained until the authority is ready, then handled with its original bounded input.
• Requests that time out or encounter terminal recovery failure are closed fail-closed and cleaned up.

Root cause and fix

The local authority endpoint began accepting connections before recovery completed, so an initial asset operation could lose the startup race. The broker now retains only verified local pending connections during that narrow readiness window, enforces a bounded buffer, and either starts their session after recovery or closes them on timeout or recovery failure.

Changelog

• changelog/1.0.0-rc.5/fs-authority-native.md

Screenshots

Not applicable — no user-interface surface changed.

Validation

• pnpm -C packages/fs-authority-native test:native — 23 passed.
• pnpm dprint check — passed.
• pnpm exec eslint . — passed.
• pnpm typecheck — passed.
• Hosted CI must pass the real arm64 packaged authority smoke and macOS installer required gate before merge.

Review Scope

• Risk: high
• Applicable profiles: Desktop and dual-runtime paths; native authority startup concurrency.
• Evidence: independent review rounds: the initial review’s sole P3 cleanup finding was resolved; the final incremental review found P0–P3: none; targeted tests cover readiness, timeout cleanup, and terminal recovery failure.
• Rule exceptions: none.

Experience Review

• 已判断是否需要沉淀经验
• 如需要，已运行 $post-task-experience-review
• reviewer PASS / NOT APPLICABLE 后才进入 merge

Experience Review Result: PASS. The accepted cleanup feedback reinforces existing fail-closed authority, readiness, and resource-lifecycle review requirements; it does not establish a new stable rule, so no rules change is proposed.

Policy Conflict Review

Not applicable — no workflow, permission, or release-rule documentation changed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
oneworks-dev	Ignored	Preview	Aug 30, 2026 5:40pm

[github-actions]

Experience Review

Before merge, make sure the PR body contains this completed checklist:

## Experience Review
- [x] 已判断是否需要沉淀经验
- [x] 如需要，已运行 `$post-task-experience-review`
- [x] reviewer `PASS` / `NOT APPLICABLE` 后才进入 merge

Checklist to confirm:

• Decide whether this PR produced reusable project experience.
• If experience should be captured, run $post-task-experience-review.
• Merge only after the independent reviewer reports PASS or NOT APPLICABLE for the Experience Review Result.
• For workflow, permission, or release-rule documentation changes, also add this checked section to the PR body after an independent read-only conflict review:

## Policy Conflict Review
- [x] Independent read-only reviewer checked workflow, permission, and release-rule conflicts and reported PASS