docs: refresh the live-activities leftovers against what actually shipped - #487
Merged
RonenMars merged 1 commit intoAug 1, 2026
Merged
Conversation
…pped [skip-ci] The doc existed only as an untracked file and still described the 2026-07-25 state, in which both stacks were open and unmerged. Every structural claim in it had since flipped, so read as written it pointed at work that no longer needs doing and hid the three items that do. tb-mobile #419–#423 were all closed unmerged and the work reached `land/integration-prep` as five direct commits instead, tb-streamer #292–#294 all merged, issue #424 is closed, and four of the five dependabot PRs are gone. The base it named, `integration-merge-354-355-376`, does not exist on origin — the branch that does is `integration-merge-354-355-376-v2`. Resolved items are kept with their reasoning rather than deleted, since that reasoning is why the decisions went the way they did. Two things got worse rather than better. The Expo issue draft for ITMS-90863 is gone: it lived in a `/private/tmp/` scratchpad that the previous snapshot flagged as needing a durable home, and that directory has since been cleaned. Both docs branches are still unpushed, so the runbook exists only inside a local worktree and one `git worktree remove` would take it with it. [skip-ci]
RonenMars
added a commit
that referenced
this pull request
Aug 1, 2026
…pped (#487) The doc existed only as an untracked working-tree file and still described the 2026-07-25 state, in which both stacks were open and unmerged. tb-mobile #419–#423 were all closed unmerged and the work reached `land/integration-prep` as five direct commits instead, tb-streamer #292–#294 all merged, issue #424 is closed, and four of the five dependabot PRs are gone. The base it named, `integration-merge-354-355-376`, does not exist on origin — the branch that does is `integration-merge-354-355-376-v2`. Resolved items keep their reasoning rather than being deleted, since that reasoning is why the decisions went the way they did. Two things got worse rather than better: the Expo issue draft for ITMS-90863 is gone with the `/private/tmp/` scratchpad that held it, and both docs branches are still unpushed, leaving the runbook inside a local worktree only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The doc existed only as an untracked working-tree file, so it never survived a clone, and it still described the 2026-07-25 state in which both stacks were open and unmerged.
Every structural claim had flipped
land/integration-prepas five direct commits (9f3dbcfe,19b00296,58ae32f5,9a2f84c9,67d1e21e)integration-merge-354-355-376integration-merge-354-355-376-v2Read as written, the doc pointed at work that no longer needs doing and buried the three items that do.
Two things got worse, not better
The Expo issue draft for ITMS-90863 is gone.
It lived in a
/private/tmp/session scratchpad, the previous snapshot explicitly flagged that it needed a durable home, and that directory has since been cleaned.§1.2 now says "rewrite the draft if you still want to file it" rather than "send the draft", and points at the bisection in §3.3, which is the part that took the work.
Both docs branches are still unpushed, so the runbook exists only inside a local worktree — one
git worktree removefrom being lost.What was kept
Resolved items keep their reasoning rather than being deleted, because that reasoning is why the decisions went the way they did: why renewal rather than patching
expo-widgets, whywithXcodeProjectrather thanmergeContents, why theexpo-modules-corepin is the right side of the trade.The wire contract in §2 is reframed from a pre-merge gate to the contract of record, since a decode mismatch does not error — the surface just stops updating.
Items that cannot be checked from this machine, such as whether Mac availability is still ticked in App Store Connect, now say so instead of implying they are outstanding.
Documentation only, so the commit carries
[skip-ci].