Stable and nightly release labels describe source included in the verified server or desktop release. They do not verify App Store or Google Play delivery. Native rollout gaps remain in the per-item limits.
30 items are proposed for closure. No item was closed. Read the cited evidence and the release label before acting.
Audit finding. The current web composer has an Attach files button beside Send with no mobile-width hiding rule. Its native file input accepts selected files through addComposerAttachments, and image classification keeps PNG and HEIC selections on the image path. This supplies the mobile-friendly picker explicitly requested, without relying on Android clipboard image support, and the change is included in the verified stable release.
Recommendation. Close: fixed. Close as fixed by the web attachment picker and ask users on old servers to update.
Confidence high. Release: In stable source.
Independent closure check. The body explicitly accepts either clipboard support or a mobile-friendly picker. Current ChatComposer renders a native multiple-file input and an Attach files button in the compact action group without a mobile hiding class. Selected PNG/JPEG/HEIC files follow the image attachment path and no clipboard API is required. The picker requires the current server attachment capability, so the recommendation must tell old-server users to update. Merged 8236 is in stable 0.0.37. No Android browser runtime check was performed.
Limits. Source and existing tests were inspected; no live Android Chrome session was run.
Audit finding. Merged PR 8480 adds Refresh models to the mobile model picker on iOS and Android. It calls serverEnvironment.refreshProviders with the selected environmentId, disables repeated taps while pending, and shows a failure alert; successful refreshes update the provider catalog. Focused tests cover the target environment, duplicate taps, and retry after failure.
Recommendation. Close: fixed. Close the issue and point users to Refresh models in the mobile model picker.
Confidence high. Release: Release not verified.
Independent closure check. The request names possible locations, not a required Settings-only entry point. Both iOS and Android model pickers now expose an environment-scoped refresh action that invokes the general serverRefreshProviders command, so it refreshes Cursor and other providers rather than only OpenCode. The button disables pending duplicate taps, successful discovery updates the catalog, and failure displays an alert. Source is fixed, but release should be unknown for the mobile client. An ancestor of desktop v0.0.37 does not prove App Store or Play Store publication.
Limits. Native iOS/Android publication was not verified; implementation is in main and source tag v0.0.37.
Audit finding. Main now mounts ComposerCommandPopover in NewTaskDraftScreen and uses the same useComposerCommandMenu hook as ThreadComposer. The hook receives the selected provider and checkout with hasThread false, so first-message skill and file choices work while thread-only commands stay hidden. The merged fix includes focused tests and recorded iPhone interaction checks.
Recommendation. Close: fixed. Close as fixed on main by the merged new-task composer-menu change.
Confidence high. Release: Release not verified.
Independent closure check. The entire issue and comment concern first-message menus in the React Native app, not only the separate Swift work. Pinned NewTaskDraftScreen now mounts ComposerCommandPopover, passes draft selection and provider catalog through the shared hook, and inserts selected commands, skills, and file links into the unsent prompt. It supplies the selected environment and checkout with hasThread=false. Merged 8587 is in main and the 0.0.37 source tag. Actual App Store and Play Store delivery is not verified.
Limits. The fix is an ancestor of v0.0.37, but mobile App Store and Play Store distribution was not verified.
Audit finding. The server now persists inactivity and pull-request settlement through thread.auto-settle instead of leaving it as client-only display state. That state uses the existing activity wake event, whose projector stamps unsettledAt, and both web and mobile sort by that stamp. The server-side settlement merge is on main but is not in the inspected stable or nightly releases.
Recommendation. Close: fixed. Close as fixed on main and note that the server-side settlement change is not yet released.
Confidence high. Release: Main only.
Independent closure check. The report specifically identifies client-derived auto-settlement as the missing reason for a wake timestamp. Pinned main now dispatches thread.auto-settle from the environment server for inactivity and pull-request rules. That command produces the normal persisted settled state. New activity emits thread.unsettled, both projectors stamp unsettledAt, and web/mobile use the shared max(createdAt,unsettledAt) sort key. Ordinary active-thread activity still does not move the row. The server change is in main only, after the latest collected nightly.
Audit finding. The reporter withdrew the original models --json diagnosis, and a later comment reproduced a database lock by running the inventory commands together. The merged catalog change replaces those production CLI calls with provider.list, app.agents, and app.skills on a managed OpenCode server. The current provider test covers that HTTP discovery path, and the merge is an ancestor of stable v0.0.36 and v0.0.37.
Recommendation. Close: fixed. Close as fixed by the HTTP inventory change released in v0.0.36.
Confidence high. Release: In stable source.
Independent closure check. The full issue discussion corrects the unsupported-flag theory and identifies concurrent inventory subprocesses as the reproducible failure. Pinned main uses one managed server and HTTP inventory for local discovery, and HTTP inventory for configured servers. The old CLI loader has no production caller. Merged 8480 is an ancestor of stable 0.0.36 and 0.0.37, and no later comment reports failure after that replacement.
Audit finding. The attached screenshot shows the popup's inner content wider than its anchored shell. The merged containment fix adds min-w-0 and overflow-hidden to both the project popup shell and the shared inner combobox, while project labels already truncate. This source fix matches the pictured defect and is included in v0.0.37.
Recommendation. Close: fixed. Close as fixed in v0.0.37.
Confidence high. Release: In stable source.
Independent closure check. I read the full report and viewed its image. The project name, selected row, gear, and search underline extend beyond the popup background, which is the exact intrinsic-width overflow fixed by merged 8627. Pinned main makes both the outer project popup and inner flex item shrink and clip overflow, while labels already truncate. There is no later discussion or separate failure scope. The fix is in stable 0.0.37.
Audit finding. The screenshot matches the searchable-combobox overflow repaired by merged PR 8627. Current Sidebar constrains the anchored popup, and the shared combobox now lets its inner content shrink and clips overflow. The fix is included in v0.0.37, while the later linked menu proposal closed without merging.
Recommendation. Close: fixed. Close as fixed in v0.0.37.
Confidence high. Release: In stable source.
Independent closure check. I read the entire report and timeline and viewed the attached image. The image shows searchable project-popup content extending past its glass background on stable 0.0.36. Pinned main constrains the outer sidebar popup and lets the shared inner flex item shrink while clipping overflow, directly removing the displayed geometry defect. The fix merged after 0.0.36 and is in stable 0.0.37. The only linked later PR closed without merging, and no later reproduction is present.
Limits. The audit inspected the report image and source, not a packaged Windows runtime.
Audit finding. Merged PR #6504 already adds a manual-check animation latch, restarts the icon key, and releases the latch on animation iteration after checking finishes. It also keeps the check icon visible until the latched rotation ends and respects reduced motion. This covers the original short-response jitter without this older icon component.
Recommendation. Close: fixed. Close this PR as covered by merged PR #6504.
Confidence high. Release: In stable source. PR readiness: Close or archive.
Independent closure check. The full diff makes each manual update check restart the icon and finish its current rotation after checking ends. Full review discussion adds repeated-check restart and status-driven checks, both preserved by pinned main. Main uses a presentation latch, increments the icon key for every manual check, and releases the latch on animationiteration. The merged replacement also keeps the icon visible through state changes and honors reduced motion. It is in stable 0.0.36 and 0.0.37.
Audit finding. Merged PR #8746 now strips quotes before deduplication in both the shared server PATH merge and the desktop PATH merge. This covers the original malformed-entry failure while preserving quoted directory contents and leaving POSIX unchanged. The fix commit is an ancestor of stable v0.0.37.
Recommendation. Close: fixed. Close this PR as covered by merged PR #8746.
Confidence high. Release: In stable source. PR readiness: Close or archive.
Independent closure check. The full diff strips every quote from emitted Windows PATH entries in both shared server and desktop merges, not just comparison keys. Pinned main has that same sanitation before deduplication in both functions. It skips empty sanitized entries, preserves quoted directory contents, and leaves POSIX entries unchanged. The discussion adds no separate scope. The replacement is in stable 0.0.37.
Audit finding. Merged PR #8748 reverses the same baseline merge order as this PR and updates baseline, profile-loaded, and profile-fallback tests. Pinned main now keeps the shell and inherited PATH ahead of npm, Volta, pnpm, and Scoop fallback directories. The fix is in the latest published nightly but is not an ancestor of stable v0.0.37.
Recommendation. Close: fixed. Close this PR as covered by merged PR #8748.
Confidence high. Release: In nightly source. PR readiness: Close or archive.
- Source: packages/shared/src/shell.ts:729. Known CLI directories are appended after the merged shell PATH.
- Merged pr: PR #8748. Landed the same precedence change and focused tests.
- Check: PR #7687. Head 479917a. Required checks absent: Check, Test, Mobile Native Static Analysis, Release Smoke. GitHub reports conflicts with main.
Independent closure check. The sole production change reverses the baseline Windows PATH merge so known CLI directories follow the shell and inherited entries. Pinned main has the same merge order, and baseline, profile-loaded, and profile-fallback tests preserve it. The full body and discussion contain no extra behavior. The merged replacement is in the latest collected nightly, but not stable 0.0.37.
Limits. Required CI is absent on the current head: Check, Test, Mobile Native Static Analysis, Release Smoke.
Audit finding. Main now uses shared read-image classification and renders signed image assets inside expanded work-log rows on both clients. The merged replacement also handles persisted attachment paths and preserves the reviewed single-line and case-insensitive read-title rules. This covers the full preview scope and is in the latest nightly, but not the latest stable release.
Recommendation. Close: fixed. Close this PR as covered by the merged viewed-image work-log implementation.
Confidence high. Release: In nightly source. PR readiness: Close or archive.
Independent closure check. The complete diff and full discussion cover lazy expanded image previews on web and mobile, the shared read classifier, CR/LF rejection, Cursor title casing, and keyboard activation. Pinned main now renders signed workspace or attachment image assets in both expanded work logs and uses one shared classifier. The web shared image handler handles Enter/Space and stops their propagation, preserving the original keyboard fix without the old row guard. Merged 8936 is in the latest collected nightly but not stable 0.0.37. Mobile store delivery is not established by the desktop nightly tag.
Audit finding. The entire diff adds parent-first abort followed by child enumeration and child aborts. Main now does that recursively, limits SDK concurrency, handles failures, and waits for child cleanup before completing interruption. The merged fix is newer than the latest collected stable and nightly releases.
Recommendation. Close: fixed. Close this PR as covered by the merged recursive child-session stop fix.
Confidence high. Release: Main only. PR readiness: Close or archive.
Independent closure check. The entire current diff and the full discussion concern stopping surviving OpenCode child sessions after the parent abort. Pinned main stops the parent first, walks every descendant with bounded SDK concurrency, and keeps Stop pending until cleanup ends. Its tests include children created during the parent abort and the next-turn gate. The merged replacement is in main but not in stable 0.0.37 or the latest collected nightly.
Audit finding. Merged PR 8605 changed protocol input to store fragments, scan each new chunk once and join only at a line boundary or EOF. Main includes large fragmented-record, CRLF, UTF-8 and malformed-final-line tests. This covers the one-file PR's material behavior without depending on Stream.splitLines.
Recommendation. Close: fixed. Close this PR as handled by merged PR 8605.
Confidence high. Release: In stable source. PR readiness: Close or archive.
Independent closure check. The full one-file diff replaces repeated whole-buffer scans with a stream line splitter. Pinned main instead retains fragments and scans each arriving chunk once, covering the same performance mechanism. The one review finding requests fragmented, coalesced, and EOF coverage, all present in the merged replacement tests. The replacement is in stable 0.0.37.
Limits. GitHub reports a conflict with main. Any passing checks apply to the existing head, not a rebased result.
Audit finding. The August 28 comment identifies the same early diff snapshot and follow-up-prompt workaround as the active detailed report. The reactor still captures a ready checkpoint from the first placeholder and skips a second capture at turn completion. Keep the detailed reproduction and current Windows report together under the active issue.
Recommendation. Close: duplicate. Close this as a duplicate of issue 1434 and preserve the August 28 Windows reproduction there.
Confidence high. Release: Not applicable.
Independent closure check. Both full discussions describe the same early turn diff snapshot and later edits appearing only after a follow-up prompt. The August 28 Windows reproduction from 932 is already copied verbatim into active issue 1434, which also has the fuller 18-file reproduction and an explicit cross-link. Pinned checkpoint code still captures a real snapshot from the first placeholder and then skips completion capture, so only duplicate closure is valid.
Audit finding. The older open issue describes the same cached Working state and every cleanup action failing because the owning environment is unavailable. Both require a local dismissal path that does not claim to stop a process on the offline machine. Current settle and delete actions still use environment RPC, and the newer unreachable-state proposal is still open.
Recommendation. Close: duplicate. Close as a duplicate of issue 4852 and retain this reproduction and its linked implementation there.
Confidence high. Release: Not applicable.
Independent closure check. Both complete reports describe cached Working threads on an unreachable environment, RPC-dependent cleanup failing, and the need for local dismissal plus an honest unavailable state. Open issue 4852 already covers the missing local recovery path and has a later unreachable-machine reproduction. The new T3 Connect power-loss reproduction adds useful detail, not a different failing mechanism. Preserve it and the explicit warning that local dismissal does not stop the remote process on the retained issue. Main cleanup still uses remote commands.
Audit finding. This is the same removed-endpoint 404 already tracked by the open Bitbucket write-action report. Merge and comment both call viewerPermissionsOf, which reaches the same getRepositoryPermission helper that only tolerates 410. Keep the new workspace-endpoint proposal with the older issue rather than maintaining separate reports for two actions blocked by one gate.
Recommendation. Close: duplicate. Preserve the workspace-endpoint proposal on issue 8328 and close this as its duplicate.
Confidence high. Release: Not applicable.
Independent closure check. Full issue bodies identify the identical Bitbucket HTTP 404 from the retired repository-permission endpoint. The retained issue 8328 explicitly covers every write action, not only merge, and a new comment on its linked PR also reproduces comment posting. Comment and merge share viewerPermissionsOf and the same 410-only helper. Preserve the new supported-endpoint proposal and link 9035 on issue 8328 before closing this duplicate. The defect is not fixed in main.
Audit finding. Main still fails a session after the first 15-second foreground probe timeout, so this is not fixed. The complete replacement diff in PR 8522 carries the same two-timeout policy, success reset, and unchanged mobile behavior, while preserving the newer immediate-reconnect marker in main. That PR explicitly identifies this branch as the source approach and is an active replacement.
Recommendation. Close: duplicate. Close this PR as replaced by PR 8522 and keep the replacement open for review.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. Both full diffs tolerate the first desktop/web foreground probe timeout, reconnect on a second consecutive timeout, reset after success, and leave explicit mobile probes and definite failures unchanged. Replacement 8522 is open, explicitly identifies 5198 as its source approach, and preserves main's newer wakeProbeFailed immediate-reconnect behavior. Full discussions add no separate scope. Main still fails on the first timeout, so this is duplicate cleanup only.
Limits. Required checks absent from the canonical latest-commit rollup: Check, Test, Mobile Native Static Analysis, Release Smoke.
Audit finding. Parent openCodexThread still resumes without excludeTurns, even though child subscriptions already pass it. This remains a real gap after the input-buffer fix. Open PR 8629 covers the same parent-resume behavior and preserves the field through the generated request encoder, so it is the specific replacement for this raw-request implementation.
Recommendation. Close: duplicate. Close this PR as a duplicate of PR 8629 and keep the parent-resume fix open there.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. Both complete diffs implement metadata-only parent thread resume with excludeTurns=true and preserve recoverable fallback to thread/start. Replacement 8629 preserves the field in generated request schemas instead of using a raw request plus response decoder, and tests the encoded field and runtime payload. It is open and covers the same material change. Full discussions add user reproduction evidence but no distinct requirement. This is duplicate closure only. The parent resume defect remains unfixed in main.
Limits. Latest-head required check results are absent for Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. Main still starts a full Grok ACP session during its health check. The later Grok probe PR explicitly rebases this same CLI model/auth implementation and preserves the skills discovery that main gained afterward. Close this older branch as a duplicate of that active replacement, while keeping the replacement open to fix its reasoning-capability regression.
Recommendation. Close: duplicate. Close as a duplicate of #8884.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. I read the complete original diff, every normalized replacement difference, and both full discussions. Replacement 8884 explicitly rebases the same grok models parser, CLI-only status probe, auth detection, fallback models, and warning behavior, while retaining skill discovery added to main later. No unique behavior from 7747 is missing. The replacement is still open and must fix its reasoning-capability regression before merge. Main still starts ACP during health checks, so neither branch is a landed fix.
Limits. Required checks have no results on this head: Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. PR 8727 explicitly replaces this branch and preserves its navigation implementation across all three clients. Both diffs were read, including the successor fixes for mobile POP_TO source, reload Forward state, cold-start Back, and Android overflow. Main still lacks the feature, so archive this duplicate without calling it fixed or released.
Recommendation. Close: duplicate. Close this PR as superseded by PR 8727.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
- Source: apps/web/src/router.ts:5. Pinned main source.
- Pr: PR #8727. Active successor explicitly preserves this PR and completes the current integration.
- Comment: Discussion comment. Original mobile POP_TO source finding is corrected in the successor diff.
Independent closure check. I read the original complete diff, all original and successor discussions, and every normalized diff difference in successor 8727. The successor explicitly preserves the original work and retains Back/Forward controls, history state, shortcuts, palette entries, web/desktop routing, mobile home/thread/settings coverage, and native keyboard commands. Its generic Android header replaces the original Settings-only insertion, while iOS inherits the shared header pair. It fixes the original POP_TO source error and adds reload-forward, cold-start replacement, and Android overflow handling. No unique material behavior remains in 7808. Main still lacks this feature, and the successor still needs maintainer review, including its narrow-sidebar finding.
Audit finding. Main still has the immediate connector restart loop. This patch and the active rapid-exit PR change the same supervisor for the same failure, but the latter adds stable-uptime reset and deterministic configuration-preemption coverage with passing current-head required checks. Keep one implementation by using the rapid-exit PR as the active replacement.
Recommendation. Close: duplicate. Close this duplicate in favor of PR 8788.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. The full diff adds capped exponential restart delays and releases the reconcile lock during the wait. Full discussions and replacement 8788 cover the identical immediate-exit process loop in ManagedEndpointRuntime. The replacement uses an immediate first retry, then bounded exponential delay with stable-uptime and explicit-config reset, and guards stale supervisors after the wait. It preserves responsive configuration changes. Different delay constants are implementation choices, not extra functionality missing from the replacement. Main still restarts immediately, so this is duplicate cleanup only.
Limits. Required current-head checks are absent: Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. Main only bypasses HTTP 410 from the retired permission endpoint, so the 404 failure remains. This patch widens the bypass, while the active workspace-endpoint PR removes the retired request and keeps real permission decoding. Both cover the same preflight for merges and comments, so the supported-endpoint change is a complete replacement for this workaround.
Recommendation. Close: duplicate. Close this workaround in favor of PR 9035.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. The entire diff widens the retired Bitbucket permission-endpoint fallback to HTTP 404 and adds one test. I read replacement 9035 and both full discussions. The replacement stops calling that retired endpoint, uses the workspace-scoped effective-permission endpoint, preserves repository filtering and decoding, and retains authentication failures. It covers the same merge/comment preflight problem and is open. Close this workaround only in favor of that active replacement, not as fixed or merge-ready.
Limits. Required current-head checks are absent: Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. The full functional change tracks a successful-save revision and skips the redundant close write. Active PR #8630 covers that behavior in persistLatest and also blocks editor changes after disposal, so it is a complete replacement for this narrower fix. Main still needs the fix, and this closure is only a duplicate recommendation.
Recommendation. Close: duplicate. Move the useful flush-order test cases to PR #8630 and close this duplicate.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. Both complete diffs track the revision from the last successful save and suppress the redundant close write. Replacement 8630 checks that revision inside persistLatest, so it covers saved-buffer close behavior, pending debounce flushes, retry after a completed failed write, and newer edits during an in-flight save. It also ignores post-disposal callbacks. The bodies and full discussions add no missing production scope. Main still lacks the guard. Retain the useful flush-order test cases with the replacement.
Audit finding. Main still scans all persisted provider bindings, so the performance fix remains needed. This complete production diff and the later lookup PR both derive the same deduplicated active-session thread IDs and preserve the same decoration path. The later PR has current passing CI and bot approval, making it the active replacement while this PR can close as a duplicate, not as fixed.
Recommendation. Close: duplicate. Close as a duplicate of #8909.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. Both complete production diffs derive the same deduplicated thread IDs from live adapter sessions and read bindings only for those IDs. Both preserve the same active-session decoration and binding-error fallback. The test approaches differ, but replacement 8909 verifies that the historical scan is never called and that only the active thread is looked up. Full discussions add no separate scope. The replacement is open, and main still scans all persisted threads.
Limits. Required checks have no results on this head: Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. The current diff contains only an interrupt test and a test-double hook, despite a body that describes production changes. Main already has runtime cancellation cleanup, but the reported durable session staying running is still real because ingestion does not apply turn.aborted. The active durable-abort PR covers that remaining defect with message correlation and ingestion tests, so this test-only branch is a duplicate rather than a landed fix.
Recommendation. Close: duplicate. Close this test-only PR in favor of the active durable-abort PR and keep the underlying issue open.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. The current diff is tests only, and main already covers its runtime interruption and next-turn behavior. The body still reports a durable session running after Stop on a build newer than merged 8480, so this must not be called fixed. I read replacement 8939 in full. It adds turn.aborted to canonical thread.session.set, clears activeTurnId, writes interrupted/error state, finalizes output, and tests the exact persisted mismatch. Close this PR only as a duplicate of that active replacement, with issue 8895 left open. This is not a merge-readiness finding for 8939.
Audit finding. This fixed-delay patch addresses the same connector exit loop as the active rapid-exit PR. Both leave configuration changes responsive, while the replacement adds stable-uptime reset and tested preemption. The final discussion explicitly identifies this overlap, and neither patch has landed.
Recommendation. Close: duplicate. Close this duplicate in favor of PR 8788.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. The full diff adds a fixed restart delay and releases the reconcile lock during the wait. Full discussions and replacement 8788 cover the identical immediate-exit process loop in ManagedEndpointRuntime. The replacement uses an immediate first retry, then bounded exponential delay with stable-uptime and explicit-config reset, and guards stale supervisors after the wait. It preserves responsive configuration changes. Different delay constants are implementation choices, not extra functionality missing from the replacement. Main still restarts immediately, so this is duplicate cleanup only.
Audit finding. I read the full 739-line diff and full discussion. The shared per-environment policy goal is now handled by merged 8600, including streamed server settings, web/desktop controls, and mobile rendering of durable settlement state. However, 5290 deliberately keeps client-derived settlement and lets policy changes reclassify existing rows, while main persists settlement and does not reopen settled rows after a rule change. Close as obsolete after the accepted server-owned design, not as behavior-identical fixed code. The replacement is main-only.
Recommendation. Close: obsolete. Close as superseded by server-owned settlement. Do not describe the old immediate-reclassification behavior as shipped.
Confidence high. Release: Main only. PR readiness: Close or archive.
Independent closure check. I read the full 739-line diff and full discussion. The shared per-environment policy goal is now handled by merged 8600, including streamed server settings, web/desktop controls, and mobile rendering of durable settlement state. However, 5290 deliberately keeps client-derived settlement and lets policy changes reclassify existing rows, while main persists settlement and does not reopen settled rows after a rule change. Close as obsolete after the accepted server-owned design, not as behavior-identical fixed code. The replacement is main-only.
Audit finding. The patch redirects focus from a MenuRadioItem gear to its role=menu ancestor. Main replaced that menu with a searchable Combobox and an input in the popup in the merged project-filter change, so the old MenuPopup auto-focus path and the patch target no longer exist.
Recommendation. Close: obsolete. Close this menu-specific patch as superseded by the searchable project filter.
Confidence high. Release: In stable source. PR readiness: Close or archive.
Independent closure check. The full diff only redirects open-time focus from a project gear to its Menu ancestor. The full discussion adds no other implementation scope. Pinned main replaced that MenuPopup with a searchable Combobox whose initial focus belongs to its input, so the old Menu focus path and the patched ancestor no longer exist. The replacement merged to main and is in stable 0.0.36 and 0.0.37. This does not close the broader gear accessibility requests.
Audit finding. GitHub reports zero changed files and the complete diff is empty. The branch first kept wildcard bind addresses, then commit 7897f1b restored the existing external-interface lookup after review. Main still has that lookup, so this empty PR can be archived without claiming that the Docker pairing report is fixed.
Recommendation. Close: obsolete. Close the empty PR and leave issue 8384 open for a concrete advertised-host solution.
Confidence high. Release: Not applicable. PR readiness: Close or archive.
Independent closure check. Fresh GitHub metadata reports zero changed files, zero additions and deletions, and a fresh full diff is empty at current head 503b4bc9c76ee9d17a6550fb9f3c272a57e0691f. The full discussion and commit 7897f1b show that the original wildcard-URL change was reverted after review. This PR has no remaining implementation. Archive it without closing or claiming a fix for issue 8384, since main still chooses an external interface for a wildcard bind.
Limits. Required current-head checks are absent: Test, Check, Mobile Native Static Analysis, Release Smoke.
Audit finding. The diff only serializes loadInventoryFromCli and adds a test that calls that helper directly. Main has no production callers of this helper since HTTP inventory replaced it in the merged shared-server change. Applying this PR would not change current provider discovery, though the old helper remains in source.
Recommendation. Close: obsolete. Close this PR as obsolete after linking the HTTP inventory replacement.
Confidence high. Release: In stable source. PR readiness: Close or archive.
Independent closure check. Both changed production blocks only serialize loadInventoryFromCli. The full diff adds no other behavior, and the full discussion identifies the same CLI lock mechanism as issue 8386. Repository-wide caller search finds no production caller of that helper after the HTTP catalog replacement, so the patch no longer changes provider discovery. The replacement is in stable 0.0.36 and 0.0.37.
Every assessed issue and PR appears in a detailed volume. Each row includes its finding, next action, confidence, release status, evidence, and limits. PR rows also show the captured head, target branch, draft state, size, checks, and reviews.
Issue volumes follow number order. PR volumes follow readiness order, then any explicit priority order, then number. The number endpoints do not imply that every number between them is in that volume.
These PRs were in the initial inventory. They remain in the detailed ledger but are not counted as current open PRs or closure recommendations.
Scope includes every open issue and PR from all authors, including drafts. The first inventory had 570 issues and 924 PRs. One PR merged and one new PR opened while the audit ran, for 1,495 distinct items.
All investigation agents inherited the current model. No model override or other model service was used.
Each item was checked against its body, discussion, actual code, relevant history, and related work. The report records any source or review limit instead of treating missing evidence as a fix.
Every actionable closure had an independent check of its complete material scope. Open replacement PRs were never counted as landed fixes.
The final main change was checked separately against all potentially affected inventory items. Current heads and discussions were refreshed before the publication snapshot.
Canonical PR checks come from the pull request commit, not the fork branch reference. Passing checks do not replace source review.
Safe-merge labels use the exact reviewed head, current checks, full relevant source and discussion review, and a clean private merge simulation. The synthetic merge trees were not built or executed.
The audit was read-only. It did not close items, post comments, change repository files, or touch live application data.
This is a source and history audit, not a live Windows, macOS, iOS, Android, or browser reproduction. A few isolated Git and Ghostty probes support specific findings.
All 925 PR bodies were read. Complete diffs were reviewed for 776 PRs and complete discussions for 883. The other 149 diffs and 42 long discussions have explicit review limits. Every closure and safe-merge recommendation has full-scope independent verification.
Large PRs with incomplete full-diff or historical-discussion review are marked in their records. They are not recommended for closure or safe merge on incomplete review.
The release field describes source included in the verified server or desktop release. It does not prove App Store or Google Play delivery.
Older related references that GitHub could not resolve are omitted from verified dependencies. They were not used as fix evidence.
This is a point-in-time report. Check and review collection spans 2026-09-01T11:48:58.045413+00:00 to 2026-09-01T11:55:45.772422+00:00. The publication snapshot was frozen at 2026-09-01T11:57:41.491617+00:00.
Private paths, token-like strings, or private model labels were omitted where detected. Raw issue bodies and private prompts are not included.
All authors and drafts included. No open item was omitted from the inventory.
Check collection ran from 2026-09-01T11:48:58.045413+00:00 to 2026-09-01T11:55:45.772422+00:00.
All investigation agents used the inherited current model. No model override or other model service was used.