[GuillaumeDSM]

Summary

Prevent agent-seed QA from starting OctoBot against the wrong scheduler SQLite file when SCHEDULER_SQLITE_FILE is not exported, and add a supported node restart path that keeps seeded automations and orders.

Changelog

• start-background verifies SCHEDULER_SQLITE_FILE, NODE_SQLITE_FILE, and user/agent-seed/tasks.db all resolve to the same path; fails with an actionable error otherwise.
• bash .cursor/seed-agent.sh --restart stops the node, starts it in the background, and waits for the base URL (no seed, no bootstrap).
• Docs, tests, and Reuse before you write guidance in CONTRIBUTING-agent.md.

What's new?

Calling python -m tools.agent_seed start-background after only source .cursor/agent-seed.env now fails fast with paths and a hint to use seed-agent.sh --restart or --full. Always start or restart the demo node through seed-agent.sh so SCHEDULER_SQLITE_FILE is exported.

Reuse (follow-up)

Scheduler path checks use one private _resolve_env_path shared with resolve_scheduler_sqlite_path. Env name and default DB file come from octobot_services.constants.ENV_NODE_SQLITE_FILE and octobot_node.config.settings.SCHEDULER_SQLITE_FILE (no local copies of SCHEDULER_SQLITE_FILE / tasks.db).