Skip to content

id: Phase 13 F13.6 native client shells on the shell contract #788

Open

Description

@dezren39

What and why

A reference native client shell (Bevy or Qt) implementing the shell contract for what a terminal cannot do (3D, audio, native widgets), plus a decision record on the long-term interface (the WIT/component-model decision from F12.8).

Source

Current status

Not started. Only the web (pkgs/id/web/src/world.ts) and SSH presenters exist; no native client code in the repo.

Acceptance criteria

  • The native shell renders the same world and emits the same input events as the terminal shell, with no host change
  • It passes the F13.1 conformance check
  • A decision record documents which native framework is the reference and whether WIT changes the contract

Size

XL

Prerequisites

Activity

  1. developing-today commented on Oct 24, 2026

    @developing-today
    Contributor
  2. added
    kind/featureNew feature or capability request
    priority/lowNice to have; do when convenient
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    source/humanFiled directly by a human
    on Oct 26, 2026
  3. dezren39 commented on Oct 26, 2026

    @dezren39
    MemberAuthor

    Intake review

    Fleet monitor intake pass (protocol §5).

    Related: Phase 13 sibling set — #785 (F13.3), #786 (F13.4), #787 (F13.5), #788 (F13.6), #789 (F13.7), #790 (F13.8); this issue is F13.6 native client shells on the shell contract. It is a forward roadmap/spec item, not a reported fixed bug; nothing in the issue or its comments indicates it has been implemented.

    Notes / risks: acceptance criteria were already present in the body; none appended. Phase-13 items are large, interdependent platform work (effort/l, priority/low as roadmap items): the set should be sequenced deliberately rather than picked up piecemeal by a worker, and earlier-phase dependencies should be confirmed before implementation starts.

    Suggested approach: keep in the Phase 13 backlog until its phase dependencies land; when scheduled, split into a design pass plus implementation slices rather than a single change.

    Labels normalized by the monitor.

  4. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Oct 28, 2026
  5. 258 remaining items

  6. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: repo queue worker, lane code-o (repo-worker-code)
    • Session / ID: cron repo-queue-worker-shift-o run 2026-11-06 10:12 CST; task 9341
    • Found via: queue claim · task 9341
    • Task: task 9341 for issue id: Phase 13 F13.6 native client shells on the shell contract #788 (small_fix: F13.6 Bevy shell contract-parity vertical slice). Fresh check: issue id: Phase 13 F13.6 native client shells on the shell contract #788 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Execution-lane assignment returned opencode — handed off to the opencode claimant, which launches the bound opencode session; this lane does not work it directly.
    • Expectation: claimant session drives task 9341 to a terminal state. ⚠️ Attempts 32/32 — AT CAP: this task has cycled handoff→park→reclaim since 2026-11-04 without a claimant launch. If the claimant does not launch on this cycle, the task cannot be claimed again and the work needs manual re-queue or a cap raise.
    • Links: task 9341 · issue id: Phase 13 F13.6 native client shells on the shell contract #788
  7. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 6, 2026
  8. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  9. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked

  10. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    work/assignedQueue worker lifecycle state
    on Nov 6, 2026
  11. dezren39 commented on Nov 7, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 9341; monitor run 2026-11-07 02:12 CST
    • Found via: monitor reconciliation (claim/label divergence)
    • Task: Claim evaporated — task 9341 is queued and unclaimed in repo-health-code-pilot while this issue still carried claimed/assigned labels. Labels reset to the truth: queue/queued + status/needs-triage. Checkpoint stage at evaporation: verified.
    • Expectation: the next lane to claim task 9341 resumes from that checkpoint; do not restart from scratch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/lLarge: multi-day or open-ended; expect staged check-insenhancementNew feature or requestkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmode/onlineFully doable remotely: design, config, code, cloudpriority/lowNice to have; do when convenientqueue/blockedQueue or user escalation statequeue/queuedHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanstatus/blockedQueue or user escalation statestatus/needs-triageNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions