Skip to content

01a083c7 - Require a Lightning Address before forum posts - #145

Merged
TaprootFreak merged 7 commits into
developfrom
01a083c7-forum-post-requires-lightning
Sep 9, 2026
Merged

01a083c7 - Require a Lightning Address before forum posts#145
TaprootFreak merged 7 commits into
developfrom
01a083c7-forum-post-requires-lightning

Conversation

@TaprootFreakAI

@TaprootFreakAI TaprootFreakAI commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

EN:
Forum posts now require a Lightning Address. The overlay asks for it without Skip; contact messages still only need a name and the living-room rules. /welcome and /members/[accountId] now have overlay-address screenshot baselines.

DE:
Forum-Posts brauchen jetzt eine Lightning-Adresse. Das Overlay fragt danach ohne Skip; Kontakt bleibt bei Name und Wohnzimmerregeln. /welcome und /members/[accountId] haben jetzt Overlay-Address-Screenshot-Baselines.

Details

nextPostRequirement is rules, then name, then lightning-address. ContactLoader uses nextContactRequirement (rules then name only). Onboarding Skip on /setup/address is unchanged so members can still read the living room.

Variants overlay-address on /welcome and /members/[accountId] are catalogued in scripts/screen-variants.mjs, documented in the handbook, asserted in e2e, and have four Linux Chromium baselines each (desktop/mobile × light/dark).

Forum compose now opens the requirements overlay when lightning-address
is missing (no Skip). Contact still only needs rules and name.
The overlay title matches the rest of the catalog and drops Lightning
jargon.
Dialog queries now use the catalog title instead of Lightning jargon.
CI lint failed on a long Wallet of Satoshi dialog query.
GitHub CI lost a race: the busy flag was still set when the retry click ran.
@TaprootFreakAI

Copy link
Copy Markdown
Collaborator Author

EN:
Ready after 3 review passes.
Forum posts require a Lightning Address; the overlay collects it without Skip.

DE:
Bereit nach 3 Review-Durchläufen.
Forum-Posts brauchen eine Lightning-Adresse; das Overlay holt sie ohne Skip.

Details

Pass 1 asked for Wallet of Satoshi overlay copy and a CONTRIBUTING tree comment. A demand for new visual variants of RequirementsOverlay was rejected: name/rules overlays are also uncatalogued. Pass 2 aligned tests with that copy. Pass 3 flushed a GitHub-only PM-busy race in MemberProfileScreen tests. No open PR comments or review threads. mergeable=MERGEABLE. All six GitHub CI jobs succeeded at ff04ccb.

@TaprootFreakAI
TaprootFreakAI marked this pull request as ready for review September 9, 2026 09:34
@TaprootFreakAI
TaprootFreakAI marked this pull request as draft September 9, 2026 10:04
Forum post without a Wallet of Satoshi address is a distinct UI
state. Catalog, handbook, visual spec, and Linux Chromium shots
cover the overlay.
A reply without a Wallet of Satoshi address is a distinct state of
the member profile. Catalog, handbook, visual spec, and Linux
Chromium shots cover the overlay.
@TaprootFreakAI

Copy link
Copy Markdown
Collaborator Author

EN:
Ready after 2 review passes.
Forum posts require a Wallet of Satoshi address; /welcome and member profiles have overlay-address screenshot baselines.

DE:
Bereit nach 2 Review-Durchläufen.
Forum-Posts brauchen eine Wallet-of-Satoshi-Adresse; /welcome und Mitgliederprofile haben Overlay-Address-Screenshot-Baselines.

Details

Head 0725dd1d7fe721fbce8be16aa5139e0f1168505e. Mergeable. All six CI checks success on this SHA (typecheck/lint/handbook/e2e-check/screenshots/coverage/build, e2e behavior, four visual combos).

Pass 1 (previous head): quality asked for a /members/[accountId] overlay-address baseline as well as /welcome. That is now in the catalog, handbook, visual spec, e2e, and four Linux Chromium PNGs.

Pass 2: 0 counted defects. One quality note on Function: nextPostRequirement (title vs onboarding skip body) was not taken as a defect: e2e:check requires the Function: <Name> title, and the export is already exercised through the running app by the forum-post and member-reply overlay tests.

No unresolved review threads. No inline comments.

@TaprootFreakAI
TaprootFreakAI marked this pull request as ready for review September 9, 2026 11:37
@TaprootFreak
TaprootFreak merged commit 9a30ab4 into develop Sep 9, 2026
12 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.

2 participants