Why
The browser bridge vertical slice has been manually verified in dev mock mode through a real browser extension, SSH loopback forwarding, and the local test dapp. The remaining validation step is the non-mock path: bridge -> shared wallet client -> deckard-signerd -> unlocked wallet address.
This proves the extension flow works against the same daemon path used by Deckard/MCP, not only --dev-mock-account.
Related: #44, #49, #50.
Scope
- Run Deckard/signerd with a throwaway unlocked wallet.
- Start
deckard-browser-bridge without --dev-mock-account.
- Load the unpacked extension in a browser and exercise the test dapp.
- Capture any setup friction around remote development, SSH port forwarding, and competing wallet extensions.
Acceptance
eth_requestAccounts returns the unlocked Deckard daemon address.eth_accounts returns [] before permission and the account after eth_requestAccounts for that origin.eth_chainId reflects DECKARD_CHAIN_ID.- Failure cases are documented for locked wallet, missing daemon socket, and wrong chain configuration.
Why
The browser bridge vertical slice has been manually verified in dev mock mode through a real browser extension, SSH loopback forwarding, and the local test dapp. The remaining validation step is the non-mock path: bridge -> shared wallet client ->
deckard-signerd-> unlocked wallet address.This proves the extension flow works against the same daemon path used by Deckard/MCP, not only
--dev-mock-account.Related: #44, #49, #50.
Scope
deckard-browser-bridgewithout--dev-mock-account.Acceptance
eth_requestAccountsreturns the unlocked Deckard daemon address.eth_accountsreturns[]before permission and the account aftereth_requestAccountsfor that origin.eth_chainIdreflectsDECKARD_CHAIN_ID.