Docs recommend --gas auto --gas-adjustment 1.3, which under-estimates and fails while still charging the fee #22

Problem

--gas auto --gas-adjustment 1.3 is the documented default across roughly 17 files. It can under-estimate the gas a transaction actually needs, so the transaction fails with out of gas — and the fee is still charged, because the fee is deducted before execution. The user pays and gets no state change.

This was hit during a real mainnet validator setup: an edit-validator call estimated 63,625 gas but needed 68,089.

cli/overview.md is the root of the pattern — it explicitly calls the flag combination a "safe default", and the rest of the docs follow its lead:

| `--gas auto --gas-adjustment 1.3` | safe default; override with a fixed number for known-cheap txs. |

Impact

Anyone copy-pasting from the docs can lose fees to a transaction that never applies. It's worst on create-validator, which is the one irreversible step in validator onboarding and the moment an operator is least equipped to debug a silent failure.

Affected files

docs/cli/overview.md (the "safe default" guidance), docs/cli/staking.md, docs/cli/bank.md, docs/cli/governance.md, docs/ibc/channels.md, docs/ibc/hermes-setup.md, docs/validators/slashing.md, docs/validators/operations.md, docs/run-a-node/local-devnet.md, docs/modules/cw-hooks.md, docs/modules/tokenfactory.md, docs/modules/drip.md, docs/modules/ibc-transfer-app.md, and others.

Suggested fix

Either raise the recommendation to --gas-adjustment 1.8+ or use flat generous --gas values, and correct the cli/overview.md guidance so the bad default stops propagating.

Docs should also show verifying with query tx <hash> and checking code: 0, since a broadcast response only reports mempool acceptance — code: 11 is the out-of-gas signal.

Already done

#21 fixes this on the validator/mainnet path only (become-a-validator.md and the new validator-walkthrough.md use a flat --gas and document the verification step). This issue tracks the remaining files.