Repository navigation
app-control: Electron and mobile capture #7562
Description
Parent
Refs #7555. Source: PLAN Phase 0, topic poteto-review. Thread: Electron and mobile capture
(deferred).
Depends on
- none (parked: opens on the reopen trigger below, not on an edge)
Reopen trigger
A consumer needs Electron or mobile capture.
Outcome
When reopened: /app-control:drive capture supports an Electron or mobile surface, researched live.
Decisions
- Deferred: Electron and mobile capture wait for a consumer (D14). Origin: ours.
- Options on record: per-surface adapter pages (electron, android, ios), superseded by live research
(D66).
Key interfaces
From the design's contracts: "Capture: --kind trace|cpu|heap|screenshot|aria|video|logs;
--attach always attended."
Done when
- The trigger has fired and is cited in a comment.
- Slices are filed under this item.
Out of scope
- Browser capture, which the app-control thread owns.
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.
Size: Large
Complexity: High
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is a parked item to extend
/app-control:drive captureto an Electron or mobile surface, researched live. It opens only when a consumer needs it (D14). Browser capture is out of scope.Nothing else is missing. The first done-when item needs a comment that cites the trigger firing, and none is on the issue yet. The work spans several surfaces (Electron, Android, iOS), so it is split into slices once the trigger fires.
No likely duplicates found among the open issues. #10518 and #9507 touch app-control but ask for different things.
Automated triage, applied by the lanes App.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).
kyle-sexton commentedon Oct 26, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.kyle-sexton commentedon Nov 1, 2026
Cordoned under the After zero milestone, still open. Issue Triage session reading (2026-11-01).
The "Size large: split pending" park does not fit this issue: there is no decided scope to split yet. The design record defers Electron and mobile capture "until a consumer needs it" (D14), and the stack-specific design comes from live research once the item reopens (D66). No comment here shows a consumer has appeared; the two related app-control issues intake named, #10518 and #9507, are closed and neither is an Electron or mobile consumer.
It stays open as deferred work rather than closing, and leaves the issue lane:
status: readyandwork-class: structuralcome off,status: confirmedholds it. When a consumer needs Electron or mobile capture, the research and split start here.