fix(e2e): cloud agent SDK53 verification — deploy pair + Playwright LT12 (#292) #836
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!836
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cursor/gitlab-issue-workflow-b0e4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Cloud Agent full verification for GitLab #292. SDK 53 / terrad v4 stack is already on
main; this MR fixes cloud E2E guardrails discovered during verification:deploy-dex-localon SDK53 volumes produces a differentpair_address. Addede2e/helpers/deploy-pair.ts, setE2E_TRADE_PAIRinglobal-setup.tsfrom.qa-deploy-stamp.exact: true(#179), mobile wallet LUNC scoped to.sm:hiddenchip (#186).setup-cloud-localterranow runsnpm ci(if needed) + lockedplaywright install chromium(includes headless shell).Acceptance checklist (#292)
make setup-cloud-localterraon Cloud VMsha256:29e2d1…2faf, 25 pairsmake test(contracts + frontend unit)make test-contracts+make test-frontendmake test-e2esg docker -c 'CI=1 make test-e2e'after LT11/LT12make test-qa-verify-deploymake test-qa-verify-deploymake test-indexer-integrationmake test-localterra-host-curlVerification commands (third parties)
Blockers (issue stays open)
e2e-seed-expired-parked-claim-all.shfails on current chain.Core SDK53 paths verified: wasm upload/instantiate/execute, indexer v4 tx-search sync, deploy scripts, signing/broadcast in 33/38 on-chain tx specs.
Related:
docs/localterra-sdk53.mdLT11–LT12.changed the description
changed the description
mentioned in issue #292
Security review
Commit reviewed:
b023bd2b2600e44e51ac98fc1391a04bc58afc4dScope: 11 files — E2E deploy-pair helper, Playwright global-setup, smoke locator fixes,
setup-cloud-agent-localterra.shLT12 Playwright install, docs,smartcontracts/artifacts/checksums.txtOutcome:
FINDINGS: 0medium+ — NONESummary
Reviewed added/modified paths for injection, authn/authz, secret leakage, SSRF/XSS, path traversal, and supply-chain regressions. All changes are confined to local E2E / Cloud Agent setup; no production frontend, indexer API, or on-chain contract logic is touched.
e2e/helpers/deploy-pair.ts+global-setup.tsE2E_TRADE_PAIRor.qa-deploy-stamppair_addressvia regex (no shellsource). Values flow only into Playwrightpage.goto('/trade/…')and local indexer smoke requests during CI/dev E2E — not user-facing runtime. Attacker would need write access to the dev/CI workspace stamp or env; out of production threat model.navigation,pool,trade-page-initial-load)setup-cloud-agent-localterra.sh_ensure_playwright_browsersnpm ci+./node_modules/.bin/playwright install chromiumfrom existingpackage-lock.json; no new dependencies or user-controlled command injection.checksums.txtwasm-checksums.txtis the CI artifact). No deploy bypass introduced.No inline threads — nothing to anchor on the diff.
Automated security review (Cursor Cloud Agent)
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue.
Reviewed by Cursor Bugbot for commit
b023bd2b26. Configure here.Skip-chain smoke fails import
Medium Severity
Calling
e2eTradePairFromDeploy()at module load throws whenE2E_TRADE_PAIRand.qa-deploy-stampare absent. WithPLAYWRIGHT_SKIP_CHAIN=1,global-setup.tsis disabled and specs that used a hardcoded pair fallback now fail during collection before per-testtest.skipcan run.Additional Locations (2)
frontend-dapp/e2e/price-chart-smoke.spec.ts#L13-L14frontend-dapp/e2e/trade-book-edit-178.spec.ts#L7-L8Reviewed by Cursor Bugbot for commit
b023bd2b26. Configure here.added 1 commit
e91f1597- fix(e2e): allow skip-chain smoke to import specs without deploy stampCompare with previous version
changed the description
resolved all threads
Security review
Commit reviewed:
e91f159716b110e47dbe560ac5d40c2d8a8a78ffScope: 11 files —
e2e/helpers/deploy-pair.ts(incl. optional-chain legacy fallback), Playwrightglobal-setup.ts, smoke locator fixes,setup-cloud-agent-localterra.shLT12 Playwright install, docs,smartcontracts/artifacts/checksums.txtOutcome:
FINDINGS: 0medium+ — NONESummary
Re-reviewed the full MR diff (including commit
e91f159fixing skip-chain spec import) for injection, authn/authz, secret leakage, SSRF/XSS, path traversal, and supply-chain regressions. All changes remain confined to local E2E / Cloud Agent setup; no production frontend, indexer API, or on-chain contract logic is touched.e2e/helpers/deploy-pair.ts+global-setup.tsE2E_TRADE_PAIRor.qa-deploy-stamppair_addressvia anchored regex (no shellsource). Values flow only into Playwrightpage.goto('/trade/…')and local indexer smokerequest.getduring CI/dev E2E — not user-facing runtime. Attacker would need write access to the dev/CI workspace stamp or env; out of production threat model. Optional-chain legacy fallback is a hardcoded bech32 constant (same trust as prior inline default).navigation,pool,trade-page-initial-load)setup-cloud-agent-localterra.sh_ensure_playwright_browsersnpm ci+./node_modules/.bin/playwright install chromiumfrom existingpackage-lock.json; no new dependencies or user-controlled command injection.checksums.txtwasm-checksums.txtis the CI artifact). No deploy bypass introduced.No inline threads — nothing to anchor on the diff.
Automated security review (Cursor Cloud Agent)
mentioned in commit
7bc4fcf9efmentioned in issue #338
mentioned in issue #340
mentioned in commit
adce686b35mentioned in commit
82881336f7