docs(#292): verification LT11 E2E deploy/indexer guardrails #829
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!829
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cursor/gitlab-issue-verification-42ca"
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 verification of GitLab #292 (LocalTerra SDK 53 / terrad v4). Core infrastructure, deploy, contracts, frontend unit tests, QA verify-deploy, and indexer integration tests pass. Strict
make test-e2epartially fails — documented guardrails added (LT11) for the deploy → indexer → E2E order that CI uses.Doc changes
docs/localterra-sdk53.md: LT11 — onedeploy-localper chain volume; rune2e-start-indexer.shbeforemake test-e2e; warn thatmake test-e2e-txredeploys without indexer restart.skills/AGENTS_E2E_STRICT_CHAIN.md: CI order (deploy→e2e-start-indexer→test-e2e); Cloud Agentsg dockerrequirement.AGENTS.md: Cloud Agent strict E2E note cross-linking LT11.Verification checklist (Cloud Agent VM)
reset → start → wait-healthy → deploy-localon new digestdocker pull ghcr.io/plasticdigits/localterra-cl8y:latest→ digestsha256:29e2d125…2fafmatchesdocker-compose.yml;terrad version4.0.1;make reset && make start && make wait-healthy;make build-optimized && make deploy-local(25 pairs, 60 seed swaps, stamp248c999)make test(contracts + frontend unit)make test-contracts— 438 tests;make test-frontend— 886/886 Vitestmake test-e2ewithout env-only skipssg docker -c 'make test-e2e': 102/106 smoke pass, 3 fail (#186 mobile wallet chip, #178 trade-book edit, #179 trade heading strict-mode — unrelated UI specs).sg docker -c 'make test-e2e-tx': 29/38 tx pass, 5 fail (indexer-dependent: limit order id, wrap-pool LUNC-C card, fee-discount swap timeout; root cause:test-e2e-txredeploys without indexer restart — LT11)make test-qa-verify-deploymake test-qa-verify-deploy+make qa-verify-deploy— pair schema OK, stamp == HEAD:latestdocker inspect/ compose commentdocker/init-chain.shSDK 53 genesismake test-indexer-integration(all suites); indexer syncs 25 pairs from factory; tx-search usespage/limit(LT10)make test-localterra-host-curlFollow-ups
make test-e2eusing CI order on a cleanmake reset-qavolume (deploy once →e2e-start-indexer.sh→sg docker -c 'CI=1 make test-e2e') to confirm tx specs green end-to-end.Closes nothing — issue stays open until E2E is fully green.
changed the description
changed the description
mentioned in issue #292
Security review
Commit reviewed:
7d4c9df9ab6781e3adb69f0ee5cdafb440906d5eScope: Documentation-only diff —
docs/localterra-sdk53.md(LT11 invariant + verification commands),skills/AGENTS_E2E_STRICT_CHAIN.md(CI deploy → indexer → E2E order),AGENTS.md(Cloud Agent strict E2E cross-link).Method: Inspected full MR diff; traced referenced scripts (
e2e-start-indexer.sh,deploy-dex-local.sh) for attacker-controlled input paths. No application, contract, indexer, or CI runtime code is modified.Outcome: FINDINGS: 0 medium+
No inline threads — nothing to annotate on the diff.
Notes:
deploy-localper chain volume, restart indexer before strict E2E). The stale-pair-row condition is a test-data consistency issue, not an exploitable production authz or injection surface.sg docker, Chrome--no-sandbox) is unchanged; not introduced by this MR.mentioned in commit
9e04cb8166mentioned in commit
0fb48c2da9mentioned in commit
a7d81f0aa1