mirror of
https://github.com/logos-co/eth-lez-atomic-swaps.git
synced 2026-08-27 09:51:11 +00:00
Danish AroraandClaude Opus 5
71c4d11ac5
* docs(trial): refresh 0.4.4 release facts, one catalog URL, honest Setup step count Things a first-time tester hits before they ever reach a swap. 1. docs/community-install.md still announced `swap v0.3.1` / `swap_ui v0.3.0` from 2026-08-03. Current is `swap v0.4.4` / `swap_ui v0.4.4`, both published 2026-08-18. The variant claims are re-verified against the actual release assets rather than copied forward: each sidecar.json reports builtVariants [darwin-arm64, linux-amd64, linux-arm64] with missingVariants [], and both .lgx payloads hash to their sidecar's sha256 and unpack to exactly those three variant trees, each carrying its swap_plugin/swap_ui_plugin binary. The build-modules.yml sentence is tightened to what the workflow actually triggers on (every pull request and every push to master) instead of "every push". 2. README and community-install disagreed on the catalog URL: the README sent people to logos.substratestudios.xyz while the doc called the raw.githubusercontent.com URL canonical. The repo-owned URL is now the single front door in both — it is what canary/leg-catalog.sh verifies on the 07:00 UTC nightly, and it does not depend on one person's domain. The mirror stays documented in community-install.md, reworded so it clearly is not the supported path. Those two files are the only places in the repo that advertise a catalog URL to users; canary/README.md's canary catalog is a deliberately separate channel and is left alone. 3. SetupView's subtitle said "Four steps" over five numbered SectionHeaders. Step 5 is a handoff to the market, not a setup step, so the subtitle now names it as the finish rather than renumbering the screen. No test asserts the subtitle (basecamp-ui-smoke checks the "Get set up" title only), so none needed updating. Also bumps the Atomic Swaps version placeholder in the trial-feedback issue template from 0.4.0 to 0.4.4, so the form testers file during this trial shows a current example. The "Logos Basecamp 0.2.2" prerequisite in community-install.md is knowingly left alone: Basecamp's latest is 0.2.3, but changing it asserts a minimum- version compatibility claim for swap 0.4.4 that the repo does not establish. Tracked separately. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJjDSCTRwgKbAA9ivxdbLz * no-mistakes(document): docs: drop stale Setup copy from PageScaffold example --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>