Add owner control quickstart to treasury runbook

[MontrealAI]

Summary

• Expand the README with an owner control quickstart that walks through guardian key generation, signing, aggregation, and hot control levers
• Keep treasury governance steps aligned with the deployed $AGIALPHA contract address and owner-only controls

Testing

• npm run lint
• npm run test
• npm run test:frontend

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Pass chain id to execute step to match signatures

The new quickstart signs envelopes with --chain-id 1 just above, but the execute command omits --chain-id, so treasury:execute falls back to chainId 0 by default (scripts/treasury/execute-intent.ts options) and recomputes a different digest than the guardians signed. With mismatched digests aggregateGuardianEnvelopes rejects every envelope and the walkthrough cannot reach threshold even with valid approvals; the execution step needs the same chain id (or CHAIN_ID env) to succeed.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Use TreasuryExecutor address instead of AGIALPHA token

The execute command hardcodes --treasury 0xa61a3b3a130a9c20768eebf97e21515a6046a1fa, which is the $AGIALPHA ERC-20 token (src/constants/token.js), not the TreasuryExecutor contract that exposes executeTransaction/IntentExecuted. Pointing treasury:execute at the token address will always revert because that function doesn’t exist there, so the runbook fails unless operators substitute the deployed executor address.

Useful? React with 👍 / 👎.