docs(workflow): clarify default validation order [AI-assisted]

[artemgetmann]

Summary

• Problem: AGENTS.md had the right rules, but not one explicit default order for runtime-facing work.
• Why it matters: new chats/worktrees were forced to infer the workflow from scattered sections, which makes validation order inconsistent.
• What changed: added a short implement -> local checks -> live E2E -> commit -> PR -> merge -> sync-runtime sequence to AGENTS.md.
• What did NOT change (scope boundary): no product code, tests, runtime behavior, or tooling changed.

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related fix(telegram-e2e): harden mtproto reply matching [AI-assisted] #107

User-visible / Behavior Changes

• Future agent sessions on main now have an explicit default workflow for runtime-facing changes in AGENTS.md.

Security Impact (required)

• New permissions/capabilities? (No)
• Secrets/tokens handling changed? (No)
• New/changed network calls? (No)
• Command/tool execution surface changed? (No)
• Data access scope changed? (No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS: macOS
• Runtime/container: N/A
• Model/provider: N/A
• Integration/channel (if any): N/A
• Relevant config (redacted): N/A

Steps

1. Open AGENTS.md.
2. Inspect Commit & Pull Request Guidelines.
3. Confirm the workflow order is now explicit.

Expected

• The workflow order is obvious without having to infer it from multiple sections.

Actual

• The workflow note is now present and consistent with the repo's existing validation and merge rules.

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios:
  • git diff --check
  • inspected the updated AGENTS.md section after the patch
• Edge cases checked:
  • includes the draft-PR exception so the rule is not overly rigid
• What you did not verify:
  • no code/runtime behavior, because this is process documentation only

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes)
• Config/env changes? (No)
• Migration needed? (No)
• If yes, exact upgrade steps:

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: revert commit 1ce0e779e3
• Files/config to restore: AGENTS.md
• Known bad symptoms reviewers should watch for: none; docs/process only

Risks and Mitigations

• Risk: None
  • Mitigation: N/A

AI Assistance

• AI-assisted
• Testing: docs-only validation