docs: fold research deltas into architecture contract + plan #10
No reviewers
Labels
No labels
auto-merge
auto-merge
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
fortiblox/arc-mev-bot!10
Loading…
Reference in a new issue
No description provided.
Delete branch "pd/research-deltas"
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?
What
Applies
docs/research/arc-arb-learnings.md§6 (PR #6,46e47bc) todocs/architecture.mdanddocs/plan.md, touching only the rows §6 names.architecture.md: §2.3
route_key,changed_pool_seeded; §2.4affordable_priority_fee,regime_index0_tip_p50,cap = min(config_cap, affordable), regime-derived; §2.5revert_reason,contention_streak,dropped_cooldown; §3adapterKind 3 = UNISWAP_V4_FLASH,4 = LIQUIDATEreserved +setAdaptercode check + startup preflight; §4.2 gas→base rate verified 1e12; §4.5 refuse aliased submit hosts,-32005= degraded class; §4.6 route cooldown4×3^(streak−1)cap 4800; §5 changed-pool seeding + regime sampler; §7 mempool-none / fee-ordered / moving-regime rows.plan.md: Phase 2/3/4/5/6 bullets per §6; status addendum: CI landed (PR #5 / WP 7920), sandwich / pending-backrun / frontrun / JIT closed as impossible, not deferred.
Line count: architecture.md 233 (cap 250). No open PR touches these files at push time.
🤖 Generated with Claude Code
c2e121b13707ddd8b36aautomerger v2 auto-approved: all 7 gates pass. Approver: fortiblox-dev (opposite-identity rule). Gates: mergeable=true,label=auto-merge,author=buddysan,identity=ok,status_checks=not_required,signatures=upstream_BP_only,opt_in=repo_marker.
automerger v2 auto-approved: all 7 gates pass. Approver: fortiblox-dev (opposite-identity rule). Gates: mergeable=true,label=auto-merge,author=buddysan,identity=ok,status_checks=not_required,signatures=upstream_BP_only,opt_in=repo_marker.
a82c8520c66681c5dc45New commits pushed, approval review dismissed automatically according to repository settings
This PR is behind base. Forgejo's API-rebase (
POST /pulls/10/update?style=rebase) creates NEW commit SHAs with no GPG/SSH signature — the[repository.signing] MERGES = alwayssetting only signs MERGE commits, not rebased intermediates. The push-hook would then reject the rewritten head with HTTP 409Forbidden: branch main is protected from unverified commit.Fix: rebase locally with your signing key configured and force-push the signed head. Automerger will pick up the new signed head within ~60s.
See
feedback_forgejo_api_rebase_unsignedmemory for the full root-cause.automerger v2 auto-approved: all 7 gates pass. Approver: fortiblox-dev (opposite-identity rule). Gates: mergeable=true,label=auto-merge,author=buddysan,identity=ok,status_checks=not_required,signatures=upstream_BP_only,opt_in=repo_marker.
automerger v2 auto-approved: all 7 gates pass. Approver: fortiblox-dev (opposite-identity rule). Gates: mergeable=true,label=auto-merge,author=buddysan,identity=ok,status_checks=not_required,signatures=upstream_BP_only,opt_in=repo_marker.
Auto-merged by forgejo-automerger at 2026-09-16 14:33:26 UTC. Approver:
fortiblox-dev(opposite-identity rule, Option C upgrade 2026-05-13). Merger:buddysanviafast-forward-only(NOT adminforce_merge). Criteria passed:mergeable=true,label=auto-merge,author=buddysan,identity=ok,status_checks=not_required,signatures=upstream_BP_only,opt_in=repo_marker. Branch843b9e1c01merged ontomainand feature branch deleted. Seeproject_forgejo_automergermemory for rationale.