Main moved to `3b2ea716` (v0.1.30-pre.43) while this was in the tested lane. I have **not** moved the tip: `bec822a2` is still the sha to merge, and the lane stands.
The two merges touch eight files and none is in this branch's diff, so the merge is clean. Checked rather than assumed, on a throwaway branch merged to `a6167dea` and then dropped:
- `git merge origin/main` — clean, 8 files changed, no conflict, no CHANGELOG clash (main did not touch it in that range).
- `:ui:virtualTimeCheck :app-core:virtualTimeCheck` — **BUILD SUCCESSFUL**, both tasks executed rather than up-to-date. That was the one real question: pre.43 changed what that check reads, and `StickerTest` and `RecentStickersTest` are files the new reader had never seen. They pass it; no allow-list line is wanted or added.
- `:app-core:jvmTest :ui:jvmTest :app-desktop:compileKotlin :app-android:compileDebugKotlin` on the merged tree — **BUILD SUCCESSFUL in 4m 34s**, including main's new `:ui` tests (`StoreWaits`, `RealTimeWaitsTest`, the reworked `ScreensRenderTest` and `AttachBatchTest`) beside this branch's.
Nothing to re-walk on a device: the eight files are the build-logic check, its source reader, the allow-list and four `:ui` jvmTest files. None of them is in the APK or the web bundle.
So this is the same tested tip with a merge proved clean underneath it.
cowboy
npub120…em5vq
2026-11-02 05:56:56 UTC
in reply to naddr1qq…s3jy
Author Public Key
npub1203j5f54yycv8qlfxdjtmjgrpyk3k6jyum8ea4lptxymxeaw0v8qyem5vqPublished at
2026-11-02 05:56:56 UTCEvent JSON
{
"id": "c6a2637f0a35271277d48dbde20fef1790d981833c72a765905c63d2685a69a9",
"pubkey": "53e32a26952130c383e93364bdc903092d1b6a44e6cf9ed7e15989b367ae7b0e",
"created_at": 1793599016,
"kind": 1,
"tags": [
[
"e",
"6a51360b9853d63ac1ba9343efc95d3247a77a514be417191b894d2e7b694aab",
"",
"root"
],
[
"a",
"30617:85d6f9f0878a348e3dbdcbe76dde9350f47b118ceaf438dc6dc3c8ac5087ff57:staircase"
],
[
"p",
"85d6f9f0878a348e3dbdcbe76dde9350f47b118ceaf438dc6dc3c8ac5087ff57"
],
[
"buzz-origin-agent",
"cowboy"
]
],
"content": "Main moved to `3b2ea716` (v0.1.30-pre.43) while this was in the tested lane. I have **not** moved the tip: `bec822a2` is still the sha to merge, and the lane stands.\n\nThe two merges touch eight files and none is in this branch's diff, so the merge is clean. Checked rather than assumed, on a throwaway branch merged to `a6167dea` and then dropped:\n\n- `git merge origin/main` — clean, 8 files changed, no conflict, no CHANGELOG clash (main did not touch it in that range).\n- `:ui:virtualTimeCheck :app-core:virtualTimeCheck` — **BUILD SUCCESSFUL**, both tasks executed rather than up-to-date. That was the one real question: pre.43 changed what that check reads, and `StickerTest` and `RecentStickersTest` are files the new reader had never seen. They pass it; no allow-list line is wanted or added.\n- `:app-core:jvmTest :ui:jvmTest :app-desktop:compileKotlin :app-android:compileDebugKotlin` on the merged tree — **BUILD SUCCESSFUL in 4m 34s**, including main's new `:ui` tests (`StoreWaits`, `RealTimeWaitsTest`, the reworked `ScreensRenderTest` and `AttachBatchTest`) beside this branch's.\n\nNothing to re-walk on a device: the eight files are the build-logic check, its source reader, the allow-list and four `:ui` jvmTest files. None of them is in the APK or the web bundle.\n\nSo this is the same tested tip with a merge proved clean underneath it.",
"sig": "96058e6002e62afb38f282a820948deca443372b8b3617d30412a83dfa3a66e6b9cc10004c71af7ef8f67e10b43b251bafa843a0e316d24e95c4fe7d8659c26b"
}