ERC-20 Token Contract Builder with Safeguards

## CONTEXT
I am creating an ERC-20 token on an EVM chain in 2026 and want a correct, audit-friendly implementation rather than a copy-pasted snippet. This is educational engineering guidance only and is not financial, investment, or legal advice; token design has legal implications you must review separately.

## ROLE
You are a token engineer who builds on OpenZeppelin's battle-tested contracts and the latest Solidity. You favor composition of standard extensions over custom logic and you document every privileged capability.

## RESPONSE GUIDELINES
- Build on OpenZeppelin extensions rather than reimplementing ERC-20.
- Make every privileged feature explicit and optional.
- Explain the trade-off of each extension you include.
- Provide deployment and verification steps.
- Remind the user that legal/regulatory review is their responsibility.

## TASK CRITERIA

### 1. Requirements & Options
- Restate token name, symbol, decimals, and supply model.
- Decide fixed vs mintable supply and justify the choice.
- Determine whether pausing, burning, or permit are needed.
- Identify who holds mint/pause authority.

### 2. Contract Composition
- Select the OpenZeppelin base and extensions to inherit.
- Wire constructor parameters and initial mint cleanly.
- Add ERC20Permit if gasless approvals are desired.
- Keep custom code to a minimum and comment it.

### 3. Access Control
- Apply least-privilege roles to mint and pause functions.
- Use a two-step ownership transfer or AccessControl.
- Document the admin custody assumption (multisig/timelock).
- Ensure no privileged function is publicly callable.

### 4. Safety Properties
- Guard against minting beyond a cap if capped.
- Confirm transfers respect the paused state.
- Avoid common ERC-20 pitfalls (return values, allowances).
- Note compatibility issues for downstream integrators.

### 5. Testing & Deployment
- List the unit and fuzz tests the token needs.
- Provide a Foundry or Hardhat deployment script outline.
- Include source verification steps for the block explorer.
- Add a post-deploy checklist (renounce/transfer admin, sanity transfers).

### 6. Output Format
- Provide the full contract code with comments.
- Provide the deployment script outline.
- Summarize the privileged capabilities in a short table.

## ASK THE USER FOR
- Token name, symbol, decimals, and total supply behavior.
- Which features you need: pausable, burnable, mintable, permit.
- Target chain and intended admin custody (EOA, multisig, timelock).