test: prove marketplace wallet journey

[ovitrif]

Closes #1212

This PR:

1. Adds the Android wallet journey for a Pubky marketplace purchase, aligned with the iOS journey in test: add marketplace wallet-leg journey bitkit-ios#720.
2. Adds stable identifiers for watch-only authorization, contact payments, incoming requests, and payment approval.
3. Records the live 2026-09-02 exact-head acceptance baseline and the first-release provenance for the existing claim and incoming-request surfaces.

Acceptance evidence covers the full controlled journey: seller watch-only claim, reciprocal linked-contact setup, fresh buyer funding, canonical Paykit delivery, payment approval, zero-confirmation detection, broadcast, one-block confirmation, paid request history, and Locks completion. This branch is rebased onto Android master merge 9698dea4, where merged #1178 supplies the incoming-request swipe behavior previously tracked by #1218.

Description

• Documents the controlled two-wallet integration fixture contract, emulator port mappings, evidence requirements, and exact cross-platform actions.
• Aligns request-row identifiers to PaymentRequestRow-<id> and adds PaymentRequestPay-<id>.
• Adds PubkyAuthAuthorize, PubkyAuthOK, and ContactPaymentsToggle identifiers.
• Cites merged upstream Paykit Server POC wake2pay from notification #2 for canonical request behavior and merged Android feat: send paykit payment proofs #1178 for incoming-request swipe behavior.
• Records successful live acceptance identifiers, both device identifiers, zero-confirmation and one-confirmation boundaries, and the intended first release milestone 2.6.0.

Preview

bitkit-android-1212-journey.mp4

QA Notes

Manual Tests

• 1. Fresh funded Android buyer → receive request 5db852f6-d47a-43c4-8b17-fb7a654ac4dd → review the accepted fallback seller identity pubky…apfiy, 15,000 sats, and 141-sat fee → swipe once → verify transaction a3a427ca69a3f1d3f26fb47f38182c8543fdbd997227ddb8a2dec1ef0e927166 at zero confirmations → mine one regtest block → verify confirmed Android activity, paid request history without a Pay action, confirmed Paykit delivery, and completed Locks purchase.

Automated Checks

• PaymentRequestsScreenTest.kt: all five focused Compose tests pass, including the incoming row and Pay identifiers.
• just compile: passes.
• just test: passes all 2,283 tests.
• just lint: passes with existing baseline findings outside this change.
• Post-undraft CI build and all E2E shards pass; lightning_security passed on its isolated rerun after the first attempt hit a runner Docker host-port collision before test execution.
• Independent exact-head source audit and narrow re-certification: pass with no findings.
• Exact head 0a0f7c8b4b7153fb9f0d39d7016ec1c0b73bf96a includes master merge 9698dea447592f0380ef4a7f8231c88beae46a18.
• Fresh arm64 E2E APK SHA-256: cf96c9a637fd5b037ee4e34b5ea5ea77dd6049c71497d3cb22b4d221159e721c.
• Preview video SHA-256: e21ce4b0bea14e42c0bb437cd8d443deebe6e2ba40488c0b24dbaaad54ec05ec.
• xmllint --noout journeys/pubky-marketplace/wallet-leg.xml: passes.
• git diff --check: passes.

[greptile-apps]

Greptile Summary

Adds stable Compose identifiers and documentation for the controlled Pubky marketplace wallet journey.

• Standardizes payment-request row identifiers and adds identifiers for payment approval, Pubky authorization, and contact-payment controls.
• Adds instrumented-test coverage for the payment-request identifiers.
• Documents the two-wallet regtest fixture, acceptance evidence, and end-to-end journey steps.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
app/src/main/java/to/bitkit/ui/screens/paymentrequests/PaymentRequestsScreen.kt	Standardizes request-row tags and adds a request-specific Pay-button identifier without changing payment behavior.
app/src/androidTest/java/to/bitkit/ui/screens/paymentrequests/PaymentRequestsScreenTest.kt	Updates identifier assertions and verifies that the incoming request exposes its Pay action.
app/src/main/java/to/bitkit/ui/screens/profile/PubkyAuthApprovalSheet.kt	Adds stable identifiers to the authorization and success actions.
app/src/main/java/to/bitkit/ui/settings/SettingsScreen.kt	Renames the contact-payments switch identifier to align with the documented journey.
journeys/pubky-marketplace/README.md	Defines the integration fixture, evidence contract, release provenance, and recorded acceptance runs.
journeys/pubky-marketplace/wallet-leg.xml	Encodes the seller-authorization, buyer-payment, broadcast, and confirmation journey.

Sequence Diagram

sequenceDiagram
    participant S as Seller Wallet
    participant F as Marketplace Fixture
    participant B as Buyer Wallet
    participant C as Regtest Chain
    S->>F: Authorize watch-only account claim
    S->>B: Establish reciprocal linked contacts
    F->>B: Deliver marketplace payment request
    B->>B: Review and approve payment
    B->>C: Broadcast transaction
    F->>C: Detect zero-confirmation payment
    F->>C: Mine one block
    C-->>B: Confirm transaction
    C-->>F: Confirm payment
    F->>F: Complete marketplace purchase

Loading

_{Reviews (2): Last reviewed commit: "docs: record selector replay" | Re-trigger Greptile}

[piotr-iohk]

QA LGTM on the identifiers + journey contract. Did not re-run the isolated marketplace fixture.

Checked latest (0a0f7c8b):

• Cited IDs exist on this branch: PubkyAuthWatchOnlyConsent / Approve / Authorize / OK, ContactPaymentsToggle, PaymentRequestsSheet, PaymentRequestRow-<id>, PaymentRequestPay-<id>, ReviewAmount, ReviewContactRecipient, GRAB, SendSuccess, ActivityAmount, ActivityTxDetails.
• xmllint --noout journeys/pubky-marketplace/wallet-leg.xml passes.
• Compose identifier tests in PaymentRequestsScreenTest match the hyphenated tags.
• CI green, including e2e-tests-staging - pubky_paykit.

Notes, not blockers:

• Merge #1217 first. This PR’s PaymentRequestRow- / PaymentRequestPay- tags are a subset of #1217 (that one also adds PaymentRequestDismiss-<id>).
• PR body QA notes cite request 5db852f6-… / tx a3a427ca…. README records different accepted runs (ad1a8463-…, then selector replay b7f67854-…). Fine if those are separate replays — worth one line so we do not treat it as a mismatch later.
• README says #1209 “preserves rejected incoming requests as visible history.” On #1217, parse rejects stay log-only; the visible-history / retry path is the explicit Pay terminal toast. Wording is slightly off.

I am not blocking on not replaying the Locks/Paykit Server fixture here. The journey is documentation of an accepted 2026-09-02 run, and the app-side selectors it needs are present.