Skip to content

Add the 16 Nov Ally handoff - #72

Merged
DanielJBurbridge merged 1 commit into
feat/ally-parity-integration-20261111from
docs/ally-handoff-20261116
Nov 16, 2026
Merged

DanielJBurbridge merged 1 commit into
feat/ally-parity-integration-20261111from
docs/ally-handoff-20261116

Conversation

@DanielJBurbridge

Copy link
Copy Markdown
Owner

What changes

End-of-session handoff for Daniel at docs/handheld/HANDOFF-20261116.md, linked from the handheld index. It leads with the morning list: the L129 and L131 decisions, the Ally tests, the sudoers and secret cleanup, the package realign, and the snapshot notes.

Open work, checked on this fork: #70 is not merged. dev-red failed it on B1 (the 3-strike fallback can open an unlocked Hyprland). A fix is in progress. Its open follow-ups are L144–L147 and L157. #71 is the TDP slider at 212be276 (L180–L185), awaiting dev-red, and nothing in it has been run on an Ally.

The next Ally deploy has not happened. Its first step is #65 + #67 + #70 together, once #70 passes.

ALPHA.md and HANDOVER.md now name default/inputplumber/profiles/gaming.yaml, which is in this tree. omarchy-gaming-input-profile loads it when the machine is an RC71L and the profile service is active.

This PR claims no L range.

Model: grok-4.7

Verification

Docs only. Confirmed on DanielJBurbridge/omarchy:

No tests run. Nothing here was deployed.

Screenshots

No visible change: documentation only.

Open in Web Open in Cursor 

Record what is on the Ally, the open PRs, and the next deploy.
Point ALPHA and HANDOVER at the gaming.yaml that is in the tree.

Model: grok-4.7
Co-authored-by: Daniel Burbridge <DanielJBurbridge@users.noreply.github.com>

@DanielJBurbridge DanielJBurbridge left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dev-red: PASS at abf5f34b9e53290967e4ac9cab6dbf191e58e952

This is a docs-only change (+86/−5 across 6 files). Integ bc15c426 is an ancestor. The single commit carries Model: grok-4.7, the body states it, and the PR claims no L range.

What I checked against the tree:

  • gaming.yaml is present, with the name Omarchy Ally gaming. desktop.yaml, osk.yaml and omarchy-ally-pointer.yaml are also present.
  • The allowlist in bin/omarchy-inputplumber-profile names gamepad.yaml and dualsense.yaml, and those files are absent.
  • omarchy-gaming-input-profile gates on omarchy-hw-rog-ally and the service being active, then loads gaming. The ALPHA.md, HANDOVER.md, prior-art and parity-gaps fixes are accurate.
  • 64d567e2 (Merge #56) is an ancestor of bc15c426 (Merge #67).
  • #70 is described correctly: it failed on B1 (review 5922156206), it conflicts in alpha-followups, and L144–L147 and L157 are listed.
  • #71 is at 212be276 with L180–L185, and the PR says it hasn't been run on an Ally.
  • The next deploy is clearly marked as not done. Step 8 quotes the merged L165 rule exactly.

It claims nothing unverified that matters. The Ally state (21:53 deploy, snapper #7, dev.64d567e2-1) comes from the deploy record, which I can't see from here, and it's labelled as the last given deploy. Item 7 says outright that the repo builds aren't verified.

Lows, which don't hold the merge:

  • In item 2, desktop-lock on is only a valid stopgap on builds without #70's fallback, since #70 B1 bypasses it. Add "until #70's B1 fix lands" if you touch it again.
  • The "Flaky CI tests" list in Notes has no source. Cite the run, or say it was observed in this session.

Cleared to merge at this sha.

@DanielJBurbridge
DanielJBurbridge merged commit dc57a79 into feat/ally-parity-integration-20261111 Nov 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants