refactor: audit cleanup — archive docs, fix dupes, add auth

[eveselove]

Что сделано

1. Чистка документации (42 файла → archive/)

Перенесены 42 markdown файла из корня в archive/docs_legacy/:

• Victory announcements, readiness checklists, migration plans
• Оставлены 5 ключевых: README, AGENTS, CONTRIBUTING, REPO_STRUCTURE, ANTIGRAVITY_DEFAULT

2. Фикс дублированных полей в TaskUpdate

Удалены дублированные retry_count, tokens_used, cost_usd (были объявлены дважды — с None и с 0)

3. Bearer Token Auth Middleware

Добавлен SimpleAuthMiddleware:

• Активируется через AGENTFORGE_API_KEY env var
• Пропускает /health, /dashboard, /docs, /ws без авторизации
• Обратная совместимость: без ключа работает как раньше (без auth)

Antigravity audit session 2026-06-01

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
33534710	Triggered	Generic Password	77bb32e	node_modules/zod/src/v3/tests/error.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}