docs(plan): publish v4 status after Android telemetry split

[xodapi]

Источник

docs/PROJECT_PLAN_FINAL_v3.ru.md was correct when written, but the queue changed after:

• feat(android): request notification permission at runtime #113 merged via feat(android): request notification permission #161
• feat(android): show Vimichi mascot on dashboard #103 merged via feat(android): show Vimichi dashboard card #162
• docs(android): decide telemetry source for live token chart #164 merged via docs(android): define live token telemetry source #165
• feat(android): add agent activity pulse and live token chart #105 was split into feat(android): add aggregate agent pulse and live token chart MVP #166 aggregate MVP and feat(telemetry): add input/output token rate split to agent contract #167 input/output telemetry follow-up

Что сделать

Publish a current docs/PROJECT_PLAN_FINAL_v4.ru.md that keeps v3 as history but updates the active queue and next steps.

Acceptance Criteria

• Add docs/PROJECT_PLAN_FINAL_v4.ru.md as the new source of truth.
• Do not delete or rewrite v1/v2/v3 historical plans.
• State that Android queue is now focused on feat(android): add aggregate agent pulse and live token chart MVP #166, with feat(android): add agent activity pulse and live token chart #105 as umbrella and feat(telemetry): add input/output token rate split to agent contract #167 blocked follow-up.
• State that live-core remains next after Android feat(android): add aggregate agent pulse and live token chart MVP #166 is evaluated, not parallel research.
• Mention docs(live-core): record ExponentialSmoother as v2 rolling_buffer option #163 as blocked/low-priority docs follow-up for ExponentialSmoother/rolling_buffer.
• No code/runtime changes.

Проверки

Docs-only. Run cargo fmt --check.

[xodapi]

🤖 Начинаю выполнение. Агент: Codex

[xodapi]

✅ PR готов: #169