Close out PR #96 with maintainer-requested desktop evidence

[nisavid]

Destination

agent-sh/computer-use-linux PR #96 reaches a truthful terminal disposition after the maintainer receives faithful GNOME Shell Wayland and extension-disabled pointer-fallback evidence, and the upstream branch is confirmed current with nothing else queued. The host Plasma session remains active and the bare-metal root remains free of GNOME desktop packages.

Notes

• This map carries execution, review, publication, deterministic cleanup, and closeout through the destination.
• Use resuming-reviewed-prs, pr-review-orchestration, wizard, checkpointing-and-publishing-git-work, and the canonical reviewable-PR publisher where their gates apply.
• Keep all map and child issues in nisavid/computer-use-linux; never project them into the upstream issue tracker.
• Preserve two lanes: nisavid/pr96-maintainer-followup carries fork governance plus a patch-identical product projection for validation, while nisavid/sunset-correctness-export remains the upstream-destined product-only branch. Mirror only separable product fixes between them.
• Run the extension-disabled fallback matrix before enabling the GNOME extension. Use deterministic labelled targets and event receipts; invisible-click attestation is not evidence.
• Use a disposable Fedora 44 GNOME 50 KVM guest with two virtual heads. Keep guest packages inside the guest. Domain and volume lifecycle mutations require explicit operator authorization.

Decisions so far

• Authorize the disposable GNOME guest lifecycle — Creation of the named domain and prefixed default-pool volumes is authorized; deletion remains separately gated.
• Provision an observable two-head GNOME Wayland guest — Fedora 44, GNOME Shell 50.4 Wayland, two compositor-visible 1024×768 heads, SSH automation, and the event-capturing GTK fixture are ready; host state is unchanged.
• Validate the extension-disabled pointer fallbacks — The portal mapped both monitors accurately and rejected the off-screen request without replay; ydotool preserved the generic diagnostic while its observable receipt demonstrated the documented acceleration-sensitive landing limitation. Five focused caller-contract tests passed.
• Validate GNOME Wayland exact-window targeting — Fedora 44 and GNOME 50.4 produced exact normal, minimized, second-monitor, and fullscreen targeting with four GTK receipts; a closed target was rejected in 14.1 ms without changing focus.
• Decide whether GNOME X11 coverage is cheap enough — No. Fedora 44 is GNOME-Wayland-only; faithful X11 coverage needs a different guest and lifecycle, so the optional xdotool path is deliberately omitted.
• Reconcile PR #96 and publish final-shape evidence — Both remotes and product lanes are clean and current; no product fix was needed. The canonical PR body now carries the GNOME evidence, and the explicit full-review signal is posted.

Current gate

• Drive the full maintainer review to terminal disposition — PR fix(windowing/input): harden window targeting and pointer reporting agent-sh/computer-use-linux#96 is clean, mergeable, fully checked, and thread-free at 39efa804; a 15-minute watch found no response newer than the explicit full-review signal. The upstream maintainer owns the pending approval and merge actuation.

Not yet specified

• Product fixes, if any, exposed by live validation.
• Findings or follow-up requested during the maintainer's full review.

Out of scope

• Logging out of the current Plasma session or installing GNOME on the bare-metal root.
• Creating upstream Issues or adding fork governance files to upstream PR fix(windowing/input): harden window targeting and pointer reporting agent-sh/computer-use-linux#96.
• Treating unobservable pointer injection as evidence.
• Adding permanent cross-compositor test infrastructure to PR fix(windowing/input): harden window targeting and pointer reporting agent-sh/computer-use-linux#96.
• Publishing an independent fork release.

[coderabbitai]

🔗 Related PRs

#1 - docs(agents/setup): configure engineering workflows [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[nisavid]

The map destination is complete. Upstream PR #96 was approved and squash-merged as a8f2f303; its tree exactly matches the reviewed commit 39efa804.

All child work is resolved, including the final-review ticket #9. The disposable GNOME guest, its three volumes, the task-only fork branches, and stale temporary worktree registrations have been removed under explicit cleanup authorization. The host Plasma session and bare-metal package set were not changed.

Nothing remains queued for this map, so I am closing it.