ae-things-progress
Thing progress summaries
Adapt the fact-collection and output contracts from aha-links. Read Thing operations and the CLI reference first. The CLI collects facts and the current model summarizes them; do not call a separate reporting backend. Write reports and report titles in the user's language.
When working with the Thing bound to this run, first read its execution snapshot as described in Execution snapshots and live context. Then collect the latest review or period facts using the workflow below, and describe these sources separately. Without a binding, use only the scope explicitly specified by the user.
Scope and time
ae-cli things +digest --agent-space-id <space-id> --from 2026-09-07T00:00:00+08:00 --to 2026-09-14T00:00:00+08:00 --time-zone Asia/Shanghai --format json
ae-cli things +digest --agent-space-id <space-id> --assignee-id <member-id> --format json
ae-cli things +digest --agent-space-id <space-id> --thing-ids <id-a>,<id-b> --format json
Never guess IDs or select a personal default space. Watchlists, groups and cross-space summaries are unsupported. Daily reports cover calendar days; weekly reports run from Monday 00:00 to the next Monday 00:00, defaulting to Asia/Shanghai. For today/this week, use the current time as the cutoff; for yesterday/last week, use the complete period. Custom intervals must be explicit. Command from/to values must include a timezone, and intervals are start-inclusive and end-exclusive.
Convert recorded ISO timestamps to the report timezone and label the timezone beside the time window, collection time and evidence dates. For example, 2026-09-10T04:50:00Z should appear as 2026-09-10 12:50 (Asia/Shanghai) in Asia/Shanghai. Removing Z and calling 04:50 "Shanghai time" is incorrect. If reliable conversion is unavailable, retain the original ISO value, label it UTC and disclose that it has not been converted; never fabricate a local time.