docs: verify #451 FACTORY_ADDRESS guard docs and regression harness #996
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!996
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/451-verify-factory-address-docs"
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
pair_discovery.rscomment with the mergedConfigError::EmptyFactoryAddressstartup guard (MR !983 / commit6ae40413).make verify-issue-451,make check-factory-address-docs, agent skillskills/AGENTS_FACTORY_ADDRESS_GUARD.md, and invariant Q5 indocs/qa-invariants.md.Acceptance checklist
FACTORY_ADDRESSin everyRUN_MODEmake verify-issue-451→ stepempty_factory_address_rejected_in_dev; manual:FACTORY_ADDRESS=' ' … ./target/debug/cl8y-dex-indexer→Configuration error: FACTORY_ADDRESS must be non-empty…exit 1FACTORY_ADDRESSnon-emptygrep 'FACTORY_ADDRESS not found' scripts/qa/verify-deploy.sh;make qa-verify-deploypre-flight (Q1)FACTORY_ADDRESSpreconditiongrep SEC-I02 docs/runbooks/launch-checklist.md;make check-factory-address-docs.gitlab-ci.ymltest-indexer-librunscargo test --lib(includesempty_factory_address_rejected_in_dev);make start-qarunsqa-verify-deployafter deployFull regression:
make verify-issue-451(8/8 PASS).Follow-ups
verify-issue-451to the Cloud Agent help one-liner inAGENTS.mdif agents routinely verify SEC-I02 issues.Security review — MR !996
Commit reviewed:
0529634a84940d314e8599c9f0a3b0330c32b058Scope: Documentation alignment for SEC-I02 / #451 (
FACTORY_ADDRESSnon-empty startup guard), regression harness (make verify-issue-451,make check-factory-address-docs), agent skill, Makefile wiring, and a comment/format-only touch inindexer/src/indexer/pair_discovery.rs.Outcome:
FINDINGS: 0medium+Summary: This MR does not change indexer runtime behavior beyond a doc comment and rustfmt-style formatting in
pair_discovery.rs. The security control under test (ConfigError::EmptyFactoryAddressat config load inindexer/src/config.rs, merged in !983) is documented and regression-tested, not weakened.Reviewed attack paths (none exploitable from this diff):
FACTORY_ADDRESS: Still blocked at startup byfactory_address.trim().is_empty()→EmptyFactoryAddressbefore the indexer serves traffic. The warn-and-skip branch inverify_factory_provenanceremains defensive dead code on normal startup paths; this MR only documents that.verify-issue-451.shandcheck_factory_address_docs.pyuse fixed repo-relative paths and hardcoded env values; no attacker-controlled sinks.Inline threads: None (no medium+ findings).
Security review: no medium+ findings on this diff.
added 9 commits
mainb5752c20- Merge branch 'main' into qa/451-verify-factory-address-docsCompare with previous version
Resolved merge conflicts with
main(1 file:docs/operator-secrets.md).Kept the #451 all-mode
FACTORY_ADDRESSguard section and prod wording that references it instead of duplicating the requirement; incorporatedmain's #458 note that the non-loopback dual-zero startup guard does not apply in prod because rate limits are clamped to safe minimums.Sanity:
make check-factory-address-docsPASS.Security review — MR !996 (re-run)
Commit reviewed:
b5752c20c50b8a03699921d32dcff5d0c797ae34Scope: Documentation alignment for SEC-I02 / #451 (
FACTORY_ADDRESSnon-empty startup guard), regression harness (make verify-issue-451,make check-factory-address-docs), agent skill, Makefile wiring, comment/rustfmt inindexer/src/indexer/pair_discovery.rs, and rustfmt-only touch insmartcontracts/contracts/factory/src/contract.rstest module. Includes post-mainmerge conflict resolution indocs/operator-secrets.md.Outcome:
FINDINGS: 0medium+Delta since prior review (
0529634a): Merge commitb5752c20rebased onto currentmain; no new runtime code paths or weakened controls. Operator-secrets merge kept the all-modeFACTORY_ADDRESSguard section and incorporatedmain's #458 prod rate-limit note without removing SEC-I02 enforcement.Reviewed attack paths (none exploitable from this diff):
FACTORY_ADDRESS: Still blocked at startup byfactory_address.trim().is_empty()→ConfigError::EmptyFactoryAddressinindexer/src/config.rs(merged !983). This MR documents and regression-tests that guard; the warn-and-skip branch inverify_factory_provenanceremains unreachable defensive dead code.verify-issue-451.shandcheck_factory_address_docs.pyuse fixed repo-relative paths and hardcoded env values; no attacker-controlled sinks.Inline threads: None (no medium+ findings).
Security review: no medium+ findings on this diff.
mentioned in commit
9b98249d3b