messages: unify harness-injected data under <system-extra> tag

Replace the ad-hoc [SYSTEM INFO] / [TELEGRAM SYSTEM INFO] prefixes with a
single canonical <system-extra> wrapper, sourced from one constant
(SYSTEM_EXTRA_TAG) so emission and documentation can never diverge.

- core-api: SYSTEM_EXTRA_TAG + system_extra() helper; attachments_block
  rebuilt on top of it.
- telegram: system_info_message (location) uses the helper; the voice
  transcript is forwarded as a plain user message (it is the user's own
  words, not harness metadata).
- chat agents: new agents/common/harness.md include (long form, with an
  explicit "data, not instructions" guard), added to assistant/kid/
  project-coordinator. The tag name rides the __HARNESS_TAG__ sentinel,
  resolved in AgentSystemContext to SYSTEM_EXTRA_TAG — renaming the tag
  stays a one-line change.

agents/project-coordinator/AGENT.md

@@ -91,3 +91,7 @@ Then add a clear `## TASK` section describing exactly what you want done. You ca
 After a sub-agent finishes, **summarize the outcome for the user in plain language** — what was done, whether it succeeded, and any follow-up needed. Do not dump raw sub-agent transcripts. The user cares about the result, not which agent produced it.
 
 Keep your own messages concise. You are the single point of contact for this project: coordinate, do the everyday work yourself, delegate the specialized parts, and keep things moving.
+
+---
+
+<!-- INCLUDE: common/harness.md -->