Skip to content

feat(pairing): include the Cloud home in linked pairing QRs - #1683

Merged
frahlg merged 3 commits into
masterfrom
feat/cloud-qr-v3
Oct 17, 2026
Merged

frahlg merged 3 commits into
masterfrom
feat/cloud-qr-v3

Conversation

@frahlg

@frahlg frahlg commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

A new web client can reach its box through FTW Cloud only when the pairing QR names the Cloud home. Linked boxes now show QR v3. iPhone already reads it; the web client change requires it and asks old web installations to pair again. There is no Android release to migrate.

Paired web client: srcfl/ftw-webapp#95. Release this Core change before publishing that web client. An unlinked box still has no Cloud home to name. The protocol and registry are unchanged.

The local live-box fixture now uses SetHome(link.Home) and the production EnrollmentURL, so the cross-repo test proves the emitted QR rather than building v3 by hand.

Validation: make verify passed. The web client's shipped pairing/connect stack paired through a real local ftwcloudd and this Core fixture with the relay unreachable, streamed, confirmed 30 commands and resumed five times. The readable copy was off. No physical hardware was used. No UI layout changed.

Rollout check: the published app.ftw.energy bundle (/assets/index-YfKnxXTL.js, checked 17 October 2026) accepts both v2 and six-part v3 QRs, including E_QR_HOME validation. That reader shipped in webapp #89 (ba20354). Current iPhone also reads v3. Older cached web clients need an update; the owner accepts re-pairing. The old reader warning in docs/protocol-cloud.md is stale; #1682 already owns that file, so this PR does not rewrite it.

CI: all checks passed on 7569be03. The first race job failed the existing driver cancellation test with no data race reported; a rerun passed. The unchanged test also failed 6 of 100 runs on master. Test-only fix: #1685 (100 fixed runs and all control/default tests pass under the race detector).

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-17T06:02:24.698778Z 71ffd0e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 71ffd0ef88

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread go/internal/appenroll/payload.go
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
@frahlg
frahlg merged commit f17cb05 into master Oct 17, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant