From 048007ea2db3600cc3d22d7514f4e342b18d7c97 Mon Sep 17 00:00:00 2001 From: archipelago Date: Tue, 6 Oct 2026 16:38:35 -0400 Subject: [PATCH] Record two-node iframe deployment and remaining recovery gates --- docs/https-app-gate-followup-20261006.md | 38 +++++++++++++++++++++++- docs/paid-content-recovery-followup.md | 9 ++++++ docs/post-1.9.0-progress-20261006.md | 22 ++++++++++++++ 3 files changed, 68 insertions(+), 1 deletion(-) diff --git a/docs/https-app-gate-followup-20261006.md b/docs/https-app-gate-followup-20261006.md index 843df708..862aa3de 100644 --- a/docs/https-app-gate-followup-20261006.md +++ b/docs/https-app-gate-followup-20261006.md @@ -48,7 +48,8 @@ backend or ISO has been deployed or published. Commit `88d473f6` fixes exact loopback authority handling for localhost, 127.0.0.1 and IPv6 loopback, without rewriting external hostname/path substrings. Two regressions reproduced the old failures;22focused tests and production UI build -pass. Source is not yet deployed. This is not claimed as the operator's gate cause. +pass. This UI correction is now deployed to dev and Yaya; it is not claimed +as the operator's exact gate cause. ## Remaining acceptance @@ -56,3 +57,38 @@ Reproduce the exact hostname/app in iframe and tab; qualify trusted TLS, HTTP LA authenticated/expired/logged-out sessions, companion, service restart, hostname regeneration and update persistence. Verify unauthenticated app access is still challenged. Preserve the public-management source guard and Shorty containment. + +### HTTP/HTTPS session-boundary matrix + +A follow-up owned-browser check on dev and Yaya passed all12 cases: HTTP and +HTTPS iframe loads each with authenticated, missing and invalid sessions. +Authenticated File Browser responses were200 without the gate page; missing and +invalid sessions remained401. Evidence: `/tmp/archy-https-frame-auth-matrix.log`. +The HTTPS diagnostic still explicitly bypasses certificate trust only in its +isolated browser contexts. This does not qualify the user's exact hostname/app, +physical companion, normal trust or expired-session renewal. No live config or +app state was changed by this matrix. + +### Dashboard deployment and repeat checks + +The UI from88d473f6 is deployed on dev and Yaya. Served index SHA256 is +`29589517ea9eb6ebd8722a3dd1113a5b597dd6845e393fbf384e17732d1d14df`. +Deployment verified unchanged backend bytes, session key and app container +identities/start times. Each node has a protected UI backup and rollback script. +Evidence: `/tmp/archy-https-runtime-ui-dev-deploy.log` and +`/tmp/archy-https-runtime-ui-yaya-deploy-final.log`. + +Four delayed app-loading cases per node pass at390/1440 widths, in embedded and +overlay modes. After deployment, all12 HTTP/HTTPS valid/missing/invalid-session +iframe cases pass again. Logs: `/tmp/archy-https-ui-dev-browser.log`, +`/tmp/archy-https-ui-yaya-browser-recheck.log` and +`/tmp/archy-https-frame-auth-after-ui-recheck.log`. + +Initial post-deployment browser attempts timed out and are retained as failures. +A diagnostic context without the dashboard's local authentication state landed +on Login; fresh authenticated contexts rendered both apps without page errors. +The matrix harness now catches its response timeout and seeds authenticated state +explicitly. Build-time disk/memory pressure was also measured; the owned build +was lowered in CPU/I/O priority without changing services. Neither observation +proves the cause of every timeout. Normal certificate trust, the exact reported +hostname/app, physical companion and restart/update persistence remain open. diff --git a/docs/paid-content-recovery-followup.md b/docs/paid-content-recovery-followup.md index a88ed3c7..b4c55151 100644 --- a/docs/paid-content-recovery-followup.md +++ b/docs/paid-content-recovery-followup.md @@ -224,3 +224,12 @@ See the current [NUT-07](https://github.com/cashubtc/nuts/blob/main/07.md) and [NUT-09](https://github.com/cashubtc/nuts/blob/main/09.md) specifications. Wallet integration still needs crash-boundary fixtures, followed by purchase-context and seller-receipt integration before any new paid-content acceptance claim. + +### Additional restore checks retained for the next batch + +Review of seed restore found that the current NUT-07 consumer verifies response +length but not each returned proof identifier. Match every response to the exact +requested curve point and reject unknown state values before crediting proofs. +Do not treat a same-length response as sufficient. Also prevent a seed scan from +making reserved outgoing operation outputs available before that operation's +result/commit is recovered. These are source findings; no live restore was run. diff --git a/docs/post-1.9.0-progress-20261006.md b/docs/post-1.9.0-progress-20261006.md index 3b5fa713..a8615502 100644 --- a/docs/post-1.9.0-progress-20261006.md +++ b/docs/post-1.9.0-progress-20261006.md @@ -901,3 +901,25 @@ Final wallet serialization/network/seed qualification:1,764backend tests pass, zero failures, five existing skips. This includes the concurrent receipt/history and seed-backup tests. Source is ready for review; not deployed, and the durable purchase journal remains open. + +## Latest: journal storage and deployed iframe URL correction + +Prepared swap recovery is committed ina4ede202; immutable private send journal +storage is committed ind4b359db. The final storage qualification passes1,773 +backend tests, zero failures, five existing skips, including changed terms, +corruption, restart, wrong currency and private-file checks. No updated wallet +backend has been deployed. Reservation/commit integration is the next uncommitted +batch under qualification, not a completed purchase or seller receipt protocol. + +The iframe URL correction88d473f6 is now deployed on dev and Yaya. Backend, session +key and app container identity/start times remained unchanged. Eight delayed app +launch cases pass across mobile/desktop and session/overlay modes;12HTTP/HTTPS +valid/missing/invalid session cases pass after deployment. Initial post-deployment +timeouts remain recorded, followed by fresh-context checks and successful reruns. +The exact reported app/hostname, ordinary certificate trust and physical companion +remain open. Deployment/rollback evidence is in +`docs/https-app-gate-followup-20261006.md`. + +The private HTML/PDF report was refreshed and passes390/1440layout checks with +all17task groups and no external resources. V4V's prepared node-only catalog is +still unsigned. No additional real payments, release publication or app update.