ci(til): cite the paper that describes this release, not the first arxiv tag

.github/workflows/daily-til.md

@@ -142,6 +142,7 @@ Read all five with a single `cat` each, then choose the topic. Never run shell s
    - **Description**: one-sentence summary of the verdict/scope, 40-320 chars.
    - **Body**: markdown tables for comparisons (the corpus uses them heavily) — every table cell padded with one space on each side of every pipe, like `| Model | Price |` (compact `|Model|Price|` fails lint); fenced code blocks with a language wherever commands or config appear; citations ONLY as `[label](https://...)` — never `[[url]]` wiki-links and never bare URLs, including in source tables; a blank line before and after every heading and every list; file ends with a newline; a `<` followed by a letter or digit in prose (`<50ms`, `<model>`) is JSX to MDX and fails the compile (so is a bare `{`) — write `under 50ms`, escape it as `\<50ms` / `\{`, or put it in backticks.
    - **Sources must be reachable**: only domains on this workflow's network allowlist can be fetched (github.com, huggingface.co, openai.com, anthropic.com, ai.google.dev, blog.google, mistral.ai, deepseek.com, z.ai, qwencloud.com, python.org and their subdomains). Prefer candidates whose primary sources live there; if a candidate's key sources are blocked by the firewall, pick a different candidate rather than writing from memory.
+   - **Cite the paper that describes THIS release.** A model card often carries several `arxiv:` tags — the current technical report plus its predecessors. Picking the first or the oldest misattributes the work: PR #77 cited arXiv 2310.10688 (the 2023 original TimesFM paper) as TimesFM 3.0's reference, and PR #85 cited arXiv 2506.07900 as MiniCPM5-2B's technical report while the card also lists the newer 2602.09003. Read every `arxiv:` tag, prefer the newest one unless the card explicitly ties an older ID to this version, and if you cannot tell which describes this release, cite the model card and say the technical report was not identified.
    - **Prices come from the vendor's price sheet, never from arithmetic.** A relative claim ("one-tenth the price", "half the cost") is worthless without its baseline: read the sentence and name what it is cheaper *than* — vendors almost always mean their own previous model, not a competitor. Then fetch the vendor's pricing page (`docs.z.ai/guides/overview/pricing`, `qwencloud.com/models/<model>`, `openai.com/api/pricing`, `anthropic.com/pricing`) and quote the listed per-token numbers with that link. If no price is published, the cell reads "no official listing" — never multiply or divide some other model's price to produce a dollar figure, and never present a derived number as a price.
    - **Never**: fabricated testing claims, "In today's fast-paced world" intros, unsupported superlatives, uncited numbers, emoji anywhere (headings, tables, lists — use "Yes"/"No" in comparison tables, plain words everywhere else).
    - **Every contender must be real and fetched**: each row of a comparison table names a specific product you fetched a primary source for this run, with that source linked in the row or the section about it. Never invent placeholder contenders ("Generic X Server", "X Toolkit") to fill a table. If you cannot source at least three real contenders, write a single-product review of the one you can source instead of a comparison.