[GuillaumeDSM]

Thank you for sending your pull request.
But first, have you included unit tests, and is your code PEP8 conformant? More details

Summary

Seeded automations can be created with signal emitting turned on, via one --emit-signals option that is off by default.

Solve the issue: #___

Changelog

• Add --emit-signals to the existing bootstrap and all parsers, and forward it from seed-agent.sh --full and bootstrap.
• Apply the flag once in the shared create-automation builder so grid, index, and the stopped index all get the same emit_signals value.
• Cover the default (off) and the option (on) for grid and index.

What's new?

Copy followers fail immediately with no_trading_signal when the seeded leader is created with emit_signals: false. --emit-signals sets emit_signals: true at creation time for every scenario. Omitting the flag keeps today's behavior.

Reused _build_create_automation_user_action in tools/agent_seed/protocol/builders.py and the existing bootstrap scenario runners. No per-strategy copy of the flag.

Tests

PYTHONPATH=. pytest tools/tests/agent_seed/ — 99 passed.
python -m tools.extended_linter --base origin/dev — OK.

Verification

With --emit-signals, the grid leader (a0000000-0000-4000-8000-000000000001) was created with emit_signals: true. Copy follower 8b586a7f-a5e5-43bb-8e07-509644e54ba0 on agent-seed-kraken-sim-account-index-idle stayed running with 6 orders and no error from 06:52:12Z through 06:57:14Z. The node log had no no_trading_signal.

An index leader with the same flag also worked: follower b7e7263f-e689-46b4-adcd-02acfeb54bf3 stayed running with 3 trades and no no_trading_signal.

Without the flag, the grid create action has emit_signals: false and the grid reaches running with 6 orders. bash .cursor/seed-agent.sh --stop printed Port 8000 is free.