From 32c2302c91902e6288f1fffd022e13ba2fdd10ec Mon Sep 17 00:00:00 2001 From: Sylvain Duchesne Date: Mon, 17 Aug 2026 10:48:35 +0200 Subject: [PATCH] Deployed, and it signs people in MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit First deployment carrying the injected wallet and the external data layer. A user signs in and sees their own data. That settles the one link in the chain nothing here had ever exercised: a deployed origin CAN be embedded in the hosted broker's iframe. The identity flow runs the application inside that iframe, so data reaching a signed-in user is proof the embedding works for this origin. It is settled by the deployment, not by a test, and the doctrine now says so: no scenario covers it, so a change of origin, of proxy, or of the broker's embedding policy would be found by a person rather than by the suite. Worth stating plainly what this deployment is: the first one able to sign anybody in at all. The production bundle never asked for its runtime configuration under NODE_ENV=production, so it had neither password nor wallet to hand the data layer, and the failure was invisible from outside — the server answered, the page rendered, and nothing was wrong except that nobody could get in. --- .project/concepts/tech-stack/knowledge_deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.project/concepts/tech-stack/knowledge_deployment.md b/.project/concepts/tech-stack/knowledge_deployment.md index e93004d..4cc1b2f 100644 --- a/.project/concepts/tech-stack/knowledge_deployment.md +++ b/.project/concepts/tech-stack/knowledge_deployment.md @@ -35,7 +35,7 @@ A `Dockerfile` exists (multi-stage Bun Alpine). **Installation goes through pnpm **No** pipeline is committed (`.github/workflows/` absent, no Coolify config in the repo). A knowingly accepted blind spot. To host the Bun app, the `coolify-hosting` skill applies. -Also untested: whether a **deployed origin** can be embedded in the hosted broker's iframe at all — the SDK's identity flow runs the app inside that iframe (see [[contract_polyfill-surface]]'s `ensureIdentity()` barrier). [[caveat_firefox-lna-blocks-broker-iframe]] records the one failure mode known here, and it is a **local-dev-origin** one (`127.0.0.1` blocked by Firefox LNA); no scenario in this repo exercises a real deployed origin against the broker's embedding policy. +**A deployed origin IS embeddable in the hosted broker's iframe — VERIFIED 2026-08-17 in production**, on the first deployment carrying the injected wallet and the external data layer: a user signed in and saw their own data, which is only reachable through that iframe. The question had been open because nothing in this repo exercises it; it is settled for this origin, and it is settled by the deployment rather than by a test — **no scenario covers it**, so a change of origin, of proxy, or of the broker's embedding policy would be found by a person, not by the suite. [[caveat_firefox-lna-blocks-broker-iframe]] remains the one recorded failure mode, and it is a local-dev-origin one (`127.0.0.1` blocked by Firefox LNA). ## Environment variables