Update to Orendro

{
  "description": "Review a user's recorded day, week, or selected period in Orendro with consistent visuals, clear data gaps, and one practical next step. Use for daily summaries, weekly reviews, progress checks, or deciding what remains unrecorded.",
  "included_files": [
    {
      "relative_path": "references/shared-rules.md",
      "size_in_bytes": 1804
    }
  ],
  "name": "daily-review",
  "skill_md_contents": "---\nname: daily-review\ndescription: \"Review a user's recorded day, week, or selected period in Orendro with consistent visuals, clear data gaps, and one practical next step. Use for daily summaries, weekly reviews, progress checks, or deciding what remains unrecorded.\"\n---\n\nRead [shared rules](references/shared-rules.md) before operating.\n\n1. Resolve the requested period in the user's local timezone. Use supported\n   range/relative-day arguments. If the time window is materially ambiguous,\n   ask one clarification; otherwise use the explicit or stored local day.\n2. Retrieve only context relevant to the requested review. Use confirmed saved\n   goals and preferences when accessible. An empty bounded memory search does\n   not prove the user has no preferences.\n3. For a whole-day or multi-domain review, call daily_summary_get for that range.\n   Reuse its structured result. For a focused question, use the narrow relevant\n   domain tool instead of retrieving every domain.\n4. If the host supports the card, pass the daily_summary_get structured result\n   unchanged to render_daily_summary_card. Do not fabricate or edit fields to\n   make a card appear. Use a concise text equivalent when rendering is absent\n   or unsuitable for a notification.\n5. Describe recorded values and their completeness. A missing food entry is not\n   proof of a missed meal. A failed or denied read is not an empty day. Clearly\n   distinguish estimates from confirmed values and limits from minimum goals.\n6. Add one or two useful observations beyond the card. Keep them tied to the\n   available records; do not repeat every tile in prose or make causal claims\n   from a short history.\n7. For period comparisons, use comparable windows and measures. Disclose partial\n   current days, missing dates, and changing targets. Fetch extra data only\n   when needed to support the specific comparison.\n8. Offer one relevant next action, such as adding a missing record, reviewing\n   an expiring grocery item, or adjusting a chosen routine. Do not change a\n   goal, plan, or schedule just because a review suggests an improvement.\n9. When this workflow runs inside a scheduled task, obey the saved notification\n   condition and use the host's actual quiet-result mechanism when available.\n   Report access problems according to the agreed failure rule.\n\nOutput: local date/window, one supported card or compact text summary, a brief\ninterpretation, and at most one next-action question. If there are no useful\nrecords, offer a first action instead of interpreting zeros as actual behavior.\n"
}