telegram-task-card-projection-notice

# Telegram Task Card Projection Notice This shipped file is retained beside the governed projection docs; it is **not** the active public Task Card manual. The public, channel-neutral owner is the intrinsic Task Card, with packaged procedures at [`task_card/manual/SKILL.md`](../../../tools/task_card/manual/SKILL.md). Source-checkout architecture lives at `src/lingtai/tools/task_card/ANATOMY.md` (not a packaged manual link). Use that owner for `start | inspect | retry | stop | remove | settings | manual`, renderer authoring, limits, recovery, and cleanup. Telegram only projects the producer's `taskcard/status` and `taskcard/taskcard.md` read-only. Author `taskcard.md` as Markdown: Telegram renders ATX headings/subheadings, `**bold**`, inline backtick code, and unordered, ordered, or task-list items inside the complete resident card. Raw HTML and special characters are escaped; malformed or unmatched Markdown delimiters stay safe literal text rather than becoming provider markup. Exact `active` plus a nonempty body projects the programmable slot; exact `inactive` idempotently excludes only that slot. Missing/unreadable status, active with a missing/blank body, other status text, and unchanged bytes are no-ops. The resident message, automatic event-journal slot, authored programmable bytes, and producer files are not deleted or rewritten. Do not use this retained package as the old Telegram-owned schema, endpoint, JSON-card renderer, reverse-MCP route, or refresh-ceiling source.