[PM seat] repo:mobile — 🟢 os-justin #160

Activity

1. objectstack-fleet

   assigned

   os-justin

   on Nov 2, 2026
2. objectstack-fleet

   added

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

   on Nov 2, 2026
3. objectstack-fleet commented on Nov 2, 2026

   

   objectstack-fleetBot

   on Nov 2, 2026

   ContributorAuthor

   More actions

   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.
4. objectstack-fleet

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

   unassigned

   os-justin

   on Nov 3, 2026
6. objectstack-fleet commented on Nov 3, 2026

   

   objectstack-fleetBot

   on Nov 3, 2026

   ContributorAuthor

   More actions

   repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

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

   Landed this shift (all on main):

   • Cards: Rebrand the app to ObjectOS: app name, URL scheme objectos, bundle id / package ai.objectos.mobile #151, Private servers: probe with the anonymous discovery endpoints and confirm the server's identity before connecting #154, Bridge: stable install id and pushTokenChanged for device registration; document the no-Service-Worker rule #163, Shell: act on the Console's ready and routeChanged signals, and settle who pads the safe area #162, Connect by QR code: objectos://connect?server=… links and the native scanner screen #156, Languages: follow the phone's language in the platform's 11 locales (ruling F of objectstack#29349) #159, Bridge: scan() — barcode / QR scanning for Console fields #146, CI: run the required checks on merge_group, so the merge queue on main can land PRs #171, Saved connections and the native "切换组织" switcher (organizations and company servers) #152, Managed deployment: read the server URL (and an optional lock) from MDM managed app configuration #157 and External sign-in bar: let enterprise IdP pages load in the WebView during sign-in, behind a native bar showing the IdP's domain #155.
   • PRs: feat: rebrand the app to ObjectOS (name, objectos scheme, ai.objectos.mobile) #164 through feat(bridge): scan() — native barcode / QR scanner for Console fields #170, ci: run Lint & Type Check and CI on merge_group #172, feat: saved connections and the native connection switcher (#152) #173 and feat: read the server from MDM managed app configuration (serverUrl, lockServer) #175 through fix(shell): bridge answers follow the shell's origin rule #178.
   • Seat landings through the merge queue: feat(shell): act on the Console's ready and routeChanged signals; the shell owns the safe area #166, feat: read the server from MDM managed app configuration (serverUrl, lockServer) #175, fix(shell): route delivery to the page follows the shell origin rule #177 and fix(shell): bridge answers follow the shell's origin rule #178.

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

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

   assigned

   os-justin

   on Nov 3, 2026
9. objectstack-fleet commented on Nov 3, 2026

   

   objectstack-fleetBot

   on Nov 3, 2026

   ContributorAuthor

   More actions

   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.
10. objectstack-fleet commented on Nov 3, 2026

    

    objectstack-fleetBot

    on Nov 3, 2026

    ContributorAuthor

    More actions

    repo:mobile#1 · os-justin · session_01QSeKYnW1Xf6HDSWz1eGAqv

    Landing guard triggered: seat landing is suspended.

    EXPO_TOKEN is now configured:

    • [Maintainer] Steps only the maintainer can take to get the ObjectOS app onto a phone #184 step 2 is ticked.
    • feat(eas): link the app to the EAS project so CI can build it #185's 维护者速读 says 「EXPO_TOKEN 已设置」.
    • [Maintainer] Steps only the maintainer can take to get the ObjectOS app onto a phone #184 notes, verbatim: 「设置后，每次合并到 main 都会真正执行 EAS 构建和 OTA 发布。按车道章程，合并权会回到你手上」.

    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.