feat(calendar): resolved days, range delete; list tables keep rows beside extra fields

[ysyneu]

What

SDK v0.15.17 (regenerated with cligen + make gen-cards)

• calendar event-list: response carries days — the resolved state of every date in scope (is_off, event_id, layer).
• calendar event-delete: --start-at / --end-at clear the calendar's own events off a date range; --event-id is optional; <cal-id> can be positional and --cal-id keeps working.
• calendar event-upsert: --summary is optional.
• Also from the spec: schedule fixed-time notify week/month cycles + --days, license list release_limited, work item status docs.

List tables with extra fields

listEnvelope (runtime) only treated {items, total, …pagination} as a list, so a response with any other field beside the rows printed as a flattened FIELD/VALUE dump — for a year of event-list that is ~1,000 lines of DAYS.2026-… keys. Now, when the rows field is Items/Docs/List, the table prints the rows as before and names the rest:

ACCOUNT_ID  CAL_ID  CREATED_AT        …  EVENT_ID           IS_OFF
1           cal.x   2026-01-10 08:00  …  cale.a             false
Showing 2 results (total 2).
Also in the response: days (use --json to see it).

Detail objects whose nested slice has another name stay vertical (TestGenericListPage_NestedRowsInDetailObject). HasMore is now pagination metadata. Affected today: calendar event-list, license list, work item list / post-mortem bind. --json/toon output is unchanged; output bounding (listEnvelopeKey) stays scalar-siblings-only on purpose, since a year's days map alone exceeds the 16 KB limit and cannot be shortened.

cligen's listEnvelope accepts object/array siblings the same way, so help and cards describe event-list as {items: [...], days, total}.

Card: calendar.md explains reading days (layer order), range reset, positional <cal-id>.

Checks

• go test ./... — all packages pass (new: TestRenderGenericTable_EnvelopeWithSiblings, …EmptyEnvelopeWithSiblings, TestGenericListPage_NestedRowsInDetailObject, …HasMoreIsMetadata, cligen TestListEnvelope)
• make check-cards — OK
• Built binary against a local mock API: event-list table/JSON as above; event-delete --cal-id X --event-id Y sends {"cal_id","event_id"}; event-delete X --start-at … --end-at … sends the range.