Conversation
…hority-review-236
…ate/wallet-chat-followup-20260914
…ate/wallet-chat-followup-20260914
Contributor
Bundle Size ReportWarning Bundle budget exceeded — not a blocker, but please confirm the regression is intentional.
Eager path (module entry + modulepreloaded chunks):
Chunks over 500 KB:
All files
Commit: 51097d6 |
Contributor
⚡ Performance ReportCold StartOverall: 🟠 uncertain | p50: 11.30s → 12.12s (+7.2%) | p95: 14.48s → 13.06s (-9.9%) | Mann-Whitney: z=1.77 not significant Phase breakdown
Warm StartOverall: 🔴 regressed | p50: 477ms → 8.84s (+1752.2%) | p95: 518ms → 10.17s (+1863.9%) | Mann-Whitney: z=4.40 ✅ significant Phase breakdown
Lukewarm Start (different site, same session)Overall: 🔴 regressed | p50: 11.87s → 15.30s (+28.9%) | p95: 19.36s → 15.86s (-18.1%) | Mann-Whitney: z=2.90 ✅ significant Phase breakdown
Commit: 51097d6 | Outliers (>2x best) discarded before stats |
…6-final # Conflicts: # vendor/truapi-host.lock.json # vendor/truapi-host/dist/wasm/web/truapi_server.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server.js # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.br # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.d.ts # vendor/truapi-host/dist/wasm/web/truapi_server_bg.wasm.gz
This was referenced Oct 2, 2026
Draft
# Conflicts: # packages/ui/src/host-callbacks/handlers.ts
Forward browser #185 and refresh native vendor packages from #709 at 901a3e754d86d9bc64bf647f103e9ea0a18de470.
This branch had an error being deployed
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.
Current repair qualification — 2026-10-02
6ef2aa616b6e771c236a37f36743212472ad0b38. Prior main baseline:f4012c50c3400d1186c332ad2ae50298cefd153d.726ef76bcce42b91d664d753ac4225df0a093472(chat). Complete matching SDK/host packages remain 0.23.0; no mixed or hand-patched Wasm bundle. Generated client bytes are unchanged. Production:wasm-signing-host; separate testing bundle:wasm-signing-host,test-host.d8e759c51c8e49dd829efbd3d5227217aeac9bd8d9b8952397716fe8bdd8f95cdist/generated/client.js6c48f48837ceda0c80163dbbc208a365e44230fd55e4b472b634bb3ac2a77aa38ecea2f14eecf6bdde983f04c1d28d1c7c6bffddef639d6a31cf5a7f38ec50b90f10b028409e4d17f6256f3f4fc08fec1fd9bf6a2102f19e77e2e91a567e4a6fe21b93f44979f8a46f5f066e1dca6259984334ff4f41dd1e71f09781b5402efaNative correction and causal limits
Bulletin mortal signatures now anchor to a finalized checkpoint, while nonce/runtime state comes from the freshest available signing snapshot. A checkpoint at least 64 blocks behind is rejected before broadcast. Regression coverage verifies the actual signature with a newer nonce and older finalized checkpoint, and the expiry boundary. Existing transaction retries/deadlines are unchanged; no chain error is suppressed. The affected test fixture uses
parking_lot::Mutex.The former Seity
Extrinsic marked as invalidrun used noncanonical best-block anchors, but retained evidence lacks the signed bytes and typed pool reason. Fork-sensitive mortality was a real correctness hazard; it is not claimed as the conclusively proved cause of that historical failure. Prior hosted Factory/Genesis timeout causes also remain unproved. No broker/readiness workaround, prewarming, extra retry, or timeout increase was added.Final exact-head hosted checks
Real-runtime local verification
All six consumers passed configured build, typecheck and lint. The later README-only formatting correction passed targeted Prettier checks and did not change runtime source or canonical native package bytes. Original full Wallet→Chat→Seity test sequences, without test retries, added waits, or prewarming:
0a24db4aa189adad7b93f9ff508c7949e39196ee301a235ba13248ef4281e9e3d859919fb6cfbe06d3dc8a41807c36b8bcdf001c47eccb9735305499Wallet's tested head is final. Chat and Seity tested heads precede documentation-only formatting merges; native/Wasm pins and runtime code are unchanged. Factory, Genesis-after-navigation and Submit passed on all three. These bounded passes do not establish the cause or elimination of the older hosted timeouts. Prior SharedWorker lifecycle, Chat/profile, Peer and JAM runtime proofs remain historical at their recorded heads; they were not all rerun on these artifacts.
Final hosted retest: failures remain
error; it is not evidence of a chain rejection. Retained traces include People-chain/local development sockets but do not expose the Asset Hub gateway WebSocket exchange, so these new failures do not establish an upstream or broker cause.paseo-bulletin-next-ipfs.polkadot.io. The zero-failure host-settings gate correctly failed.Doom: criterion corrected, backend matrix still unqualified
The user explicitly approved 35 FPS sustained over 30 seconds, with one frame of sampling-boundary tolerance:
frames + 1 >= elapsedMs * 35 / 1000. This replaces the instantaneousFPS >= 35sample; it is an acceptance-criterion change, not a runtime speedup. Runtime and displayed FPS are unchanged; raw samples are not rounded to force a pass. Update p95 <28.6ms, cold/warm first-frame limits <3,000/<1,000ms, audio and translation-cache checks remain. The revised official RPC benchmark passed once before the vendor replacement.The later isolated matrix used the rebuilt base pair at frontend
238ab5fa739788b2eb948ba1f807a1876edbacad, with fresh owned Chrome profiles and no concurrent builds/E2E:Distinct diagnostics found no presentation loss in a later instrumented 24-second shared-worker sample and observed a successful hidden RPC new-document reload. Neither diagnostic supersedes the failures or qualifies performance. No evidence-proved runtime fix, guest rebuild, speculative tuning, or further unchanged gate rerun was made. The original strict RPC failure and every new failure remain retained. Next causal capture must instrument the original early 30-second window and distinguish warm lifecycle states before proposing a runtime fix.
Retention and rollout boundary
Local verification used
paseo-next-v2, the pinned host-playground fixturef56294cea4430163bf16ec068844b1327441073c, and existing private QA identities. All three corrected sequences paired on their first existing setup attempt. A prior local launch failure and a misconfigured Previewnet-product run (34 passed, 20 skipped, 8 Chain/Contract failures) are retained separately, not presented as reproductions of the hosted Genesis timeout. Private traces/auth/signers were not published.The first repair heads also exposed a README formatting failure (corrected by documentation-only commits) and a PVM cache-unit-test 5,000ms timeout. No cache runtime/test change, limit increase, or causal claim was made for that isolated timeout. Older in-flight runs superseded by the formatting correction remain recorded as cancelled, not passed.
No PR merge, force push, deployment, environment approval, SDK/npm/product/guest publication, or rollback was performed by this repair. JAM remains JAM-TEST-INSTANCE, never JAM-PUBLIC-DEVNET. The user-owned
deploy: paseo.fyilabel is retained; repair-triggered deployment runs 36970790399 and 36971286469 were cancelled before deployment. The earlier rollout audit is retained below: an older workflow deployed56cea5d37577bf82684fb5c6b6e4ba81d2142938; this record does not claim live remained unchanged historically.Historical integration qualification (superseded; retained verbatim)
Current merged-main refresh and qualification — 2026-10-01
bb9ad3d8921c63cf62c98b9029289f458b1a67a2; base:feat/pvm-wasm. Includes merged mainf4012c50c3400d1186c332ad2ae50298cefd153dand fix: protocol iframe and SharedWorker chains on the pool, and every chain client recovers from halts #313. No separate/unmerged fix: protocol iframe and SharedWorker chains on the pool, and every chain client recovers from halts #313 boundary remains.6d97c7932f26cf190dd6c506ed5f4da110bada74, including native mainbda6ac518c8cc59319491b12e4e23b96777375fd. Complete canonical SDK/host artifact-generation pin:08bddf36912d61fcfa76e4fb733fd585c6b22bca. Later native changes are tests/docs/iOS-only, not SDK/Wasm inputs; the generation pin intentionally differs from the latest source head.web-wasm-signing-hostwithouttest-host, with testing Wasm separate. No hand-edited generated declarations or mixed variants. No package publication.d8e759c51c8e49dd829efbd3d5227217aeac9bd8d9b8952397716fe8bdd8f95cdist/generated/client.js(notdist/index.js)6c48f48837ceda0c80163dbbc208a365e44230fd55e4b472b634bb3ac2a77aa3a725bcbd6ff17a92bea89bb11868a45b6b3fdb178cb037cb00da1c46105526c90778dfa5255092bbfc7607dc226d1fc9a2d2d0315ffb669258341fa307556485Stack and hosted qualification
Wallet → PVM → Chat → Seity; PVM → Peer; JAM contains both Seity and Peer. All updates used fresh-fetch ancestry checks and ordinary pushes. User worktrees, metadata and canonical repositories were preserved.
70845db96bdd21409310daeff5e471b74ab5a1c9.351e5d73fab803a0fd2a4007ce2d2557aebaff05.bb9ad3d8921c63cf62c98b9029289f458b1a67a2.b03e83616857f4e4745d479776dde43cdfa6267a.44ed4f830a2c8f86990e02fb061c802aa389b0bc.dcdef40499119183aed82a39f784ef740d494341.Exact-head hosted results: functional 89 passed, 3 skipped; E2E 41 passed, 1 flaky, 20 skipped; 3 passed in the cold-start suite. Tests run.
Hosted E2E retained one flaky Chain → Chain Spec: Genesis Hash case: it failed on the first attempt and passed the existing CI retry. No retry setting was changed.
Performance Tests runs the cold-start suite, not the strict Doom matrix below. Existing thresholds, retries, deadlines and skips were not relaxed. Native current-head Core CI has 22 passed jobs and 2 path-filter skips; full iOS application CI is not claimed for the latest native heads.
Local and actual-runtime evidence
main-refresh-terminal-verified-pvm.json/ screenshot.main-refresh-pvm-transport.json/ screenshot.main-refresh-native-chat.json. No published guest/product was created.Strict Doom matrix — retained failure
Fresh isolated visible headless Chromium profiles; cold cache miss, real compiler, nonzero audio, and 360 frame updates for each backend. Warm reload uses a new document in the owned iframe: cache hit and zero translation. Gates remain FPS ≥35, p95 <28.6ms, cold first frame <3000ms, warm first frame <1000ms.
Evidence:
main-refresh-isolated-doom-{rpc-gateway,smoldot-direct,smoldot-shared-worker}.jsonand screenshots. Earlier hidden-tab and concurrent-QA failures remain recorded; no clock/rounding/threshold change or failure-only rerun was used to erase them.Other retained limits
Extrinsic marked as invalid). One UI call caused the existing two native broadcast attempts; both validated then invalidated. No matching included Submit was found in the inspected canonical block range. [INFERENCE] Noncanonical mortality anchors may explain invalidation, but the exact cause is unproved without the unretained signed extrinsic bytes. Evidence:main-refresh-seity-submit-diagnosis.json. Passing hosted E2E does not erase this local failure.main-refresh-seity-factory-diagnosis.json. No added retries, deadline changes, or unsupported cause claim.Rollout boundary
Not an all-green rollout qualification. The refreshed heads were not deployed, and this qualification granted no environment approval. No PR merge, SDK/npm publication, or guest/product publication was performed. JAM remains JAM-TEST-INSTANCE. All three refresh-triggered JAM Deploy runs were cancelled before rollout; latest final-head cancellation. Other branches have no deployment labels.
The live environment changed during qualification: older Deploy run 36945647296, attempt 3 was approved under GitHub account
replghost, explicitly checked out baseline56cea5d37577bf82684fb5c6b6e4ba81d2142938, and recorded deployment success at 2026-10-02 01:19:01 UTC. Its later published-product smoke failed. The operator/client/session behind that account is unproven; this qualification granted no approval and performed no rollback. The observed live content hash changed from4a7caf047fb7f350c1833039b93ba634698a47c56f051b8c7fc0525d4c59a5c8to5882695ee20df5d24a6ed2feb9e997f176fe27ecf4eafe742fabb39eba92885f; these are content hashes, not Git SHAs, and their exact byte-level mapping to a source commit is unproven.Earlier deployment authorizations/results below are historical evidence, not approval to deploy this refreshed stack.
Historical integration qualification (superseded; retained verbatim)
Current-main integration qualification (2026-10-01)
19253c28214900ce1a41a727e32f29672d0f90fb. Includes main74bb603e518ace149a846124f6e7353aca198c57, propagated through feat(wallet): add an opt-in debug-only browser test wallet #238 → feat(polkavm): run App Manifest v2 runtimes in Dotli #185 → feat(chat): restore separate Chat authority integration above PolkaVM #255 → feat(profile): show product-referenced Seity profiles in a host drawer #287 and feat(polkavm): run App Manifest v2 runtimes in Dotli #185 → feat(polkavm): JamPeerTransport over WebTransport for JAM apps (layer atop #185) #290, then combined in chore(deploy): Seity layer + JamPeerTransport (#287 + #290) #291. All six heads are published by normal ancestry-guarded pushes; no history rewrite.437a46c5af88b3c4a962d763f8fa5732e9c48183; complete feature-specific artifacts, signing-only browser Wasm, and separate testing Wasm. Native base #540 CI and Peer #1010 CI are green. No npm or guest publication.117ef1eb2928a470e65e48c05b5bf22e8ab29c02(successful deployment and smoke, deployment ID6778272827). Hosted smoke passed 8/8 published products and 19/19 wallet-free capabilities. Independent fresh HTTPS Chromium sessions confirmed Build0.6.0 (117ef1e)and playable Doom with advancing frames/input/audio on smoldot-direct, RPC gateway, and an actual SharedWorker, with zero browser exceptions. All three screenshots and geometry checks show the 384 px frame meeting the 360 px debug panel without a gap. An actual retained productionc4a08e9session waited for consent, navigated exactly once after Reload, retained the URL plus localStorage/IndexedDB/product-cache markers, and resumed playable Doom on117ef1ewith an activated controlling worker, no waiting worker, and zero exceptions. This is an actual release upgrade, not a substituted worker-script test. Local JSON/screenshots are retained underdotli-community-worktrees/paseo-fixed-doom-*andpaseo-debug-fix-retained-*. No other environment was approved; no PR merge, force push, npm release, or on-chain guest publication.Earlier sections are historical implementation and qualification records.
Latest dependency refresh qualification (2026-09-30)
a0de426a7923506bd32a6f6c1f5670527cfefd53; normal merges and ancestry-guarded pushes only, no history rewrite.437a46c5af88b3c4a962d763f8fa5732e9c48183. Feature-specific 0.23.0 client/host/WASM artifacts remain unchanged; this source pin is intentionally not relabeled as the refreshed upstream branch head.Earlier implementation and qualification history follows; the versions and heads above describe this refresh.
Summary
Chat authority integration above PolkaVM #185, paired with host-rust-core#709. This is the active Chat layer replacing historical #236.
SDK provenance
@parity/truapiand@parity/truapi-host: 0.23.0.437a46c5af88b3c4a962d763f8fa5732e9c48183in host-rust-core#709.vendor/truapi-host.lock.json. Wallet WASM enableswasm-signing-host, nottest-host.Artifact boundary
The final SDK refresh pins host-rust-core#709 at
437a46c5af88b3c4a962d763f8fa5732e9c48183, including the concurrent Contacts integration and subsequent native Chat review fixes. Client and host archives came from the canonical generated client, TypeScript builds, and matching wallet/testing WASM outputs of that exact source. The generated client digest remains unchanged; the host archive and wallet WASM changed. Their archive and artifact digests are recorded in the lock.The user explicitly selected deployment of the newer sharing APIs on experimental paseo.fyi. The combined #291 deployment is
76eb846e06713679891c6e0cc17a65919909eced, built from host sourceaf087f734be4d65d9363e68e43bf134145ae0085; its evidence is separate from this branch-only CI result.Experimental execution gate
PolkaVM execution defaults on for test environments (
paseo.fyi,paseo.li, previews, and localhost) and off for productiondot.li. Settings → Experimental → PolkaVM apps explicitly overrides either default; existing saved opt-outs and opt-ins remain authoritative. This is an execution gate, not build-time exclusion of runtime assets or Firebase-controlled eligibility. Product permissions remain separate from the execution setting.Qualification
Branch-CI-qualified head:
cec01502c69856e3599c65b8af4d6da46e9ea06d.Current-head checks pass, including unit, functional, and live E2E, type-checking, production builds, and full-history secret scanning. This qualifies branch CI, not a deployment or a fresh-browser smoke at this head. Deployment evidence is qualified separately in #291.
After pulling these local-file SDK dependencies, use
bun install --force --frozen-lockfileto replace Bun's cached packages.Earlier local Chromium verification rendered the real published PVM guest and completed a canonical SDK handshake through its live host port. The current paseo.fyi deployment is the combined #291 layer, not this branch alone.
Chat 0.2.1 publication transactions and prior exact-source native evidence remain recorded in #255 (comment). No wallet creation, funding, payment, or on-device Chat message was performed for this refresh.
Startup applies URL-selected protocol settings before wallet/debug hooks and drains shared-mode writes before iframe replacement or startup-triggered reload. Testnet published-product smoke starts without opting in; production
dot.liremains default-off and its smoke uses Settings and Save & Apply, and all existing rendering/input/audio/GPU checks remain intact. Failure-only deployed smoke traces and screenshots are retained for three days.Secret scanning retains the default rules and full-history scan. The public resolver mapping-slot vector is exempted only when both its exact value and test path match; a boundary smoke confirms changed values and the same value elsewhere remain detectable.
The current combined default-on release,
76eb846e, passes 8/8 published products without a testnet opt-in and 19/19 wallet-free capabilities. Independent fresh Chromium observed that exact release, ran Doom with the default enabled, and preserved an existing testnet opt-out across reload. This is combined #291 deployment evidence, not a deployed smoke of this branch alone.