Skip to content

app-control: Electron and mobile capture #7562

Description

@kyle-sexton

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

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: structural
    Basis: automated intake triage; the lanes App applied this class.

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none

    Understood: this is a parked item to add Electron or mobile (Android, iOS) surfaces to /app-control:drive capture, with the approach researched live. It opens only when a consumer needs it. The first done-when item is a comment citing that trigger, and the second is filing slices under this item.

    No consumer has been cited yet, so the trigger hasn't fired. Nothing else is missing. The outcome is clear, and the work needs splitting per surface once it opens. I found no likely duplicates among the open issues.

    Automated triage, applied by the lanes App.

  3. changed the issue type fromtoon Oct 16, 2026
  4. changed the issue type fromtoon Oct 16, 2026
  5. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  6. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor

    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 (or status: needs-decision) and say why in a comment.

  7. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.
    status: needs-decisionAwaiting a human or maintainer judgment call.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Oct 24, 2026
  8. melodic-automation-lanes commented on Oct 24, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane: a Feature needs an open parent issue a listed human filed that awaits no decision; Size large is not one of small, medium. A recorded decision does not change these rules (.github/actions/resolve-config/admission-rules.json); a person who wants it worked adds agent-ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-specNeeds a Brief or plan before anyone can build it.priority: mediumReal value, no hard deadline; normal backlog flow.status: needs-decisionAwaiting a human or maintainer judgment call.work-class: structuralRefactors, migrations, contract changes; cross-cutting and hard to reverse.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions