Skip to content

[PM seat] repo:mobile — ⏳ vacant #160

Open

Description

@objectstack-fleet

repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

Current PM

⏳ vacant. This is an on-demand seat; summon it with pm-dispatch mobile.

  • Previous seat: os-justin, session session_01QSeKYnW1Xf6HDSWz1eGAqv. Seated 2026-11-02, left 2026-11-05 on the maintainer's 「你可以下班了」. check-handover exited 0.
  • Charter: .claude/skills/pm-dispatch/references/lanes/mobile.md (objectstack). The landing-ruling amendment is pm-dispatch lanes/mobile.md: record the maintainer ruling that the mobile seat lands non-governed PRs through the merge queue objectstack#29429 (domain:skills).
  • Patrol: none (按需席). Mailbox: none.
  • Landing: SUSPENDED. The guard of the ruling on this post (comment 6578710331, term 4) has tripped. EXPO_TOKEN is set, and EAS now builds and publishes on every push to main (first observed at ce65eb9). The maintainer merges every mobile PR; the seat does not enable auto-merge. Seat landing resumes only on a new maintainer ruling.

Inherited ledger

Item State Waits on
#186 (EAS config) decision batch #3, presented in session, not yet answered maintainer: item 1 Sentry token (rec. A, maintainer configures), item 2 appVersionSource (rec. A remote), item 3 split the platform jobs and build only Android on push (rec. A). Then one workflow PR, which the maintainer merges.
#174 pm:blocked objectstack-ai/objectstack#29642 (ruled B; spec lane) and a platform release
#153 pm:blocked objectstack-ai/cloud#3489. Carries the added item from batch #2 item 5 B (server-side revoke on removal).
#158 pm:blocked #153
#148 assigned to hotlong, PR #190 maintainer's own work; do not touch
#183, #184 assigned to hotlong maintainer-only
#149 untouched the first native-page card ruled under Route ownership

Platform cards this seat filed in objectstack:

Hot-file serial queue

Empty.

Notes

  • Owed, maintainer: device checks for every landed card, listed in each PR's 维护者速读.
  • Owed, maintainer: native-speaker review of the new locale bundles (zh-Hant was machine-converted).
  • Suggested, maintainer: add Code Quality (jest) to the main ruleset's required checks. Today the queue merges before jest finishes.
  • Security fixes ×4 landed before the first release (batch feat: Integrate Better Auth with Expo for authentication flow #2 item 1 B).

Activity

  1. added
    pm:seatSeat registry post — protocol carrier, not dispatchable work; the label page is the fleet board
    on Nov 2, 2026
  2. objectstack-fleet commented on Nov 2, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Maintainer ruling recorded: who lands mobile PRs.

    • Who: the maintainer (Justin), the account this seat runs under. Source: the Claude Code session session_01QSeKYnW1Xf6HDSWz1eGAqv, 2026-11-02.
    • Question put to the maintainer: must every mobile PR wait for the maintainer to merge it? Option 1 kept every merge with the maintainer. Option 2 had the seat land non-governed PRs after ACCEPT. Option 3 split PRs by risk.
    • Verbatim answer: 「非受管 PR 由席位落地」. The maintainer then reported 「我改了配置 Allow auto-merge」.

    Readings at the ruling:

    Setting Value
    allow_auto_merge true
    Ruleset on main deletion, non_fast_forward, required_status_checks: Lint & Type Check
    EAS Build / Update on main (92a0a26) Every build and publish step skipped (EXPO_TOKEN unset), so a merge publishes nothing

    Operating terms until the lane charter is amended (the charter PR is dispatched next):

    1. After ACCEPT, the seat lands a PR whose path surface is NOT governed (check-governed-merges --pr) and whose checks are all green on the current head. The seat marks it ready and enables auto-merge through the relay.
    2. Governed-surface PRs (.github/workflows/** and the rest of the register) stay with the maintainer.
    3. Release actions stay human. That covers eas-submit.yml, store submission and version cuts.
    4. Guard: before each landing, the seat reads the latest EAS Build and Update runs on main. If any build or publish step actually ran, which means EXPO_TOKEN is configured and a merge now pushes OTA to installed apps, the seat stops landing. Merges go back to the maintainer, and the seat asks the maintainer for a new ruling.
    5. Device checks are still listed for the maintainer in each PR's 维护者速读. Landing does not mean device-verified.
  3. changed the title [-][PM seat] repo:mobile — 🟢 os-justin[/-] [+][PM seat] repo:mobile — ⏳ vacant[/+] on Nov 3, 2026
  4. objectstack-fleet commented on Nov 3, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Shift end (seat leaves; on-demand seat, lane idle).

    Landed this shift (all on main):

    Nothing is in flight and no claim is held; check-handover exits 0. The successor reads the ledger in the post body above.

  5. changed the title [-][PM seat] repo:mobile — ⏳ vacant[/-] [+][PM seat] repo:mobile — 🟢 os-justin[/+] on Nov 3, 2026
  6. objectstack-fleet commented on Nov 3, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Ruling: batch #2 item 1 · letter B · maintainer 「批 #2 同意」 2026-11-03T08:21Z
    Ruling: batch #2 item 4 · letter A · maintainer 「批 #2 同意」 2026-11-03T08:21Z

    • Item 1, B: no security advisory. Security fixes ×4 landed before the first release.
    • Item 4, A: a route asked for while the main frame is on another origin is dropped, not held. The Known-limits line in docs/HYBRID-SHELL.md rides the next PR that touches that doc.
  7. objectstack-fleet commented on Nov 3, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Landing guard triggered: seat landing is suspended.

    EXPO_TOKEN is now configured:

    The last main EAS runs (427cb49, 06:31Z) still read skipped, because they predate the token. The next push to main will build and publish.

    So, per the ruling's term 4, the seat stops landing. Every mobile PR goes to the maintainer to merge, the seat does not enable auto-merge, and a new ruling is needed to resume seat landing.

  8. changed the title [-][PM seat] repo:mobile — 🟢 os-justin[/-] [+][PM seat] repo:mobile — ⏳ vacant[/+] on Nov 5, 2026
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

    pm:seatSeat registry post — protocol carrier, not dispatchable work; the label page is the fleet board

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions