docs(vault): v5 doc refresh — all addresses, fee structure, keeper runbook

[moggedcapital]

Summary

• Updates all 5 vault docs to v5 deployed addresses (2026-06-03)
• SYSTEM_OVERVIEW: architecture diagram, contract table, withdrawal queue, ERC-1271, leverage loop
• DEPOSIT_GUIDE: 4 entry paths (direct DIEM, WETH, VVV, referral) + async exit + leverage loop
• KEEPER_RUNBOOK: flush/settle/claim ops, adapter routeYield, FeeRouter harvest, veniceSigner rotation, monitoring commands
• mainnet-addresses: full v5 contract table with Basescan links for all contracts + old vault note
• wstdiem-economics: all 4 fee layers with exact bps, yield flow diagram, exchange rate formula

Test plan

• All contract addresses verified against broadcast artifacts
• Code snippets match current ABI

🤖 Generated with Claude Code

[antfleet-ops]

Reviewed the diff against current main (post-PR #9 / post-PR #12). Three things worth flagging before this lands, plus confirmation that the docs themselves look clean.

Confirmed clean — docs match the broadcast

Cross-checked every v5 address in docs/vault/mainnet-addresses.md against broadcast/DeployAll.s.sol/8453/run-latest.json (timestamp 1780528038142 = 2026-06-04 06:27 UTC):

• InferenceVault 0xb9f23c33…Dd2D ✓
• FeeRouter 0x3b8d968D…3a60 ✓
• Router 0x6fF481F4…32B6 ✓
• AgentTGERegistry 0x09a42279…7941 ✓
• SurplusStakingWrapper 0x04fAc3e2…c7d7 ✓
• InferenceProduct 0x8620304D…6879 ✓
• WstDiemUsdcOracle 0x7F3eAb98…b51a ✓
• WstDiemWethOracle 0x73FddCCB…1F07 ✓

The "v4 → withdrawals unlock 2026-07-01" callout for 0x4751BA…5810 is consistent with the broadcast history. Nice.

(For context: we just shipped Liquid-Protocol-Ops/agent-autonomopoly#42 to correct the v2 addresses we'd accidentally propagated downstream — these v5 addresses are the source of truth that fix points at.)

🔴 1 — 1,095 lines of internal Claude Code session notes appear accidentally committed

Three files under docs/superpowers/ look like local working notes that slipped in:

• docs/superpowers/plans/2026-04-04-tempo-mainnet-deploy.md (+782)
• docs/superpowers/specs/2026-04-04-tempo-mainnet-deploy-design.md (+209)
• docs/superpowers/session-handoff-2026-04-08.md (+104)

Content is about a separate Tempo Mainnet (chain 4217) deployment plan, with task checklists and shell commands referencing absolute developer paths (cd /Users/ceo/Documents/development/liquid-protocol-v0). Probably not intended for the v5 doc-refresh PR. Recommend dropping or moving to a separate branch.

🔴 2 — Removes PR #12's workflow permissions hardening

.github/workflows/{qa,pr,integration}.yml each drop the permissions: contents: read line that #12 added the same day. Re-merging as-is would re-open the four CodeQL actions/missing-workflow-permissions alerts that #12 just closed. Suspect this is the source of the mergeable: CONFLICTING state — the branch was rebased before #12 landed.

Fix is a single git rebase main so PR #12's 3-line additions survive.

🟡 3 — script/vault/SafeTestStakeFor.s.sol (+156)

Looks like a one-shot live mainnet probe to test whether DIEM.stakeFor(keeper, …) would work if added, per the script's header comment:

"Live test of the stakeFor architecture: … If this succeeds, the new InferenceVault design is proven: vault deposits can go directly to keeper's Venice budget."

Useful context for understanding the future direction, but feels orthogonal to a docs-refresh PR. If it's intentional to land here, the docs probably want a brief "future architecture — see SafeTestStakeFor" pointer so it doesn't look stranded.

Other small things

• mainnet-addresses.md: veniceSigner: 0x1090…4b5D — Same as deployer v5 — rotate to Privy wallet before production is the right call-out and shouldn't get lost in the rebase. Worth promoting to its own "Open ops items" section so future readers don't miss it.
• Withdrawal-queue / leverage loop / 4 entry paths / 4 fee layers — all read well and match the PR docs(vault): E3 sign-off — PhaseE fork tests ✅ + DeployAll dry-run ✅ (MOG-504) #9 broadcast operational sequence (SafeKeeperSetup, SafeAddSurplusChannel, SafeAddV4LP, SafeInitiateWithdrawals, SafeEnableWithdrawals).

Offer

Happy to open a clean rebased docs-only PR (drops the superpowers files, restores PR #12's permissions blocks, optionally splits SafeTestStakeFor.s.sol into its own branch) if that's useful. Or feel free to do the rebase yourself — whichever is faster.