Skip to content

E7 follow-up — scheduling-context Squadron selector (board #146) #38

Closed as not planned

Description

@Jacksondr5

Posted by an AI agent on Jackson's behalf

Admitted to the dogfood queue by Jackson (board ask #33, 2026-09-01). Give the scheduling flow a truthful Squadron selector as part of the scheduling-context milestone — composes with DV5's scheduled-cohort return (see docs/j5/product/dogfood-v0.md). Board finding #146 carries the E7-era measurement.

Activity

  1. added
    dogfood-queueReserved J5-native dogfood work — not staffable in Traycer
    on Aug 31, 2026
  2. Jacksondr5 commented on Sep 29, 2026

    @Jacksondr5
    OwnerAuthor

    Posted by an AI agent on Jackson's behalf.

    Heads-up: this issue cites product/dogfood-v0.md and the DV5 override. That plan is being removed in favor of issues (#354). This issue is now the record of the gap, still measured against Squadron AC7 (every picker offers Squadrons).

  3. Jacksondr5 commented on Oct 8, 2026

    @Jacksondr5
    OwnerAuthor

    Closing: Squadrons are retired and their behaviour is folded into projects (#412; merged in #454, #455, #456, #457, #482, #483, #484 and #489). A thread's home is now its project, so the Squadron this issue is about no longer exists. If part of this still applies to projects, reopen it or file it in those terms.

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

    dogfood-queueReserved J5-native dogfood work — not staffable in Traycer

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions