@wirecat/cli-core 0.546.0 → 0.548.0

package/CHANGELOG.md

@@ -7,6 +7,179 @@ shape of this file.
 
 ## Unreleased
 
+## 0.548.0 — 02.11.2026
+
+### Added
+
+- **A feed is asked whether it changed.** `sync` sends a feed the last answer's `ETag` / `Last-Modified` back as
+  `If-None-Match` / `If-Modified-Since`, and a `304` keeps every stored event without reading the feed again
+  (`feeds[].unchanged` in the answer). The validators are the feed calendar's sync token in the store, valid for one
+  window: the first sync of a new day, and `sync --rescan`, read the feed in full. `fetchFeedIfChanged` is exported;
+  a `fullListOnly` source now gets its last token in `changes()`, and a page may say `unchanged: true`.
+- **`calendars add` warns once on stderr for an `http://` feed**: the feed and any token in its address travel
+  unencrypted. It is still allowed; `webcal://` and `https://` do not warn.
+
+### Changed — may break callers
+
+- **`calendars remove` deletes a feed's events instead of cancelling them**, with the calendar row, its cursor, the
+  events and series only it held, their links, tags, search words and vectors, and people only it had seen. An event
+  another calendar also holds stays with that copy. The answer's `events` counts the events deleted. A new
+  `EventStore.forgetCalendar(calendarId, now)` does it: an `EventStore` written outside cli-core must add it
+  (`memoryEventStore` and the SQLite store have it, and `eventStoreContract` checks it). `calendars unsync` is
+  unchanged.
+
+## 0.547.0 — 02.11.2026
+
+### Added
+
+- **A server's refused SEARCH fails that folder, not the run, and proves nothing.** A mail source throws
+  `mail.search-refused` (`SEARCH_REFUSED`, `searchRefused`) when the server answers SEARCH with NO or BAD. `syncMail`
+  reads the other folders, answers `state: "partial"` with `refusedFolders`, and for the refused folder marks no mail
+  deleted, changes no membership, moves no resume point and leaves `mail_coverage` as it was. Before, a mail source that
+  read the refusal as "nothing found" made the folder look empty.
+- **Server search reads big mail text-first, and the next sync completes it.** A candidate is read up to
+  `SERVER_BOUNDS.textBytes` (256 KiB, `fetchRaw(items, { bytes })`); one cut short is stored with its text and no
+  attachments, marked `metadata.partial`, and `meta.issues` says `search.server-partial`. `syncMail` then reads up to
+  100 partial emails whole and clears the mark (`partial: { completed, left }`; `completePartial: false` skips it).
+  `MailStore.partialEmails` lists them. No store migration: the mark is a JSON key older builds ignore.
+- **`readClientFile` (from `@wirecat/cli-core/oauth`) reads a user's own Google Desktop OAuth client file** (the
+  `{ "installed": { client_id, client_secret } }` JSON from Google's console). It refuses a file other users can read
+  (`sign-in.client-file-open`) and a file of the wrong shape (`sign-in.client-file-invalid`), and never puts the file's
+  contents in an error. gcal, drive and mail each kept a copy of this reader.
+- **`openBrowser(url, browser?)` is exported from `@wirecat/cli-core/cli`**, so a CLI that does not start through
+  `startCli` opens the sign-in page the same way: `open`, `rundll32` or `xdg-open`, or the named browser.
+- **iCalendar feeds as read-only calendars.** With `deps.feeds` (`icsFeeds`), `calendars add <url> [--title]` follows a
+  public holiday calendar, a sports schedule or a published `.ics` address, and `calendars remove <calendar>` stops.
+  `sync` reads each feed after the provider (`syncWithFeeds`), so its events show in `events list`,
+  `search events`, `overlapping:` and `events remind`. Repeating events are expanded here (`expandSeries`: RRULE in
+  the event's own zone, RDATE, EXDATE and overrides). The address is a secret input, kept by the CLI and never
+  printed; a fetch follows redirects only to https and stops at 10 MB and 30 s. `readIcs` takes
+  `{ overrides: true }` and returns the calendar's `name`. See `docs/dev/CALENDARS.md`, "Feeds".
+- **History limits for pushed history, per profile.** A messenger whose history is pushed (`history: "store"`,
+  WhatsApp) saves one-to-one chats back `history_dialog_days` (1095 by default), groups of more than two people back
+  `history_group_days` (365) and nothing of a group above `history_group_members_max` people (50); at most 1095 days.
+  The chat row stays, so the chat is still listed. Live messages, `messages sync` and what the store already holds are
+  never dropped. `messages sync <chat> --full-history` fetches a chat and keeps its pushed history in full from then on
+  (`history_included` in the answer). `ChatsStore` gains `historySkips`, `historyShapes`, `recordHistorySkips` and
+  `setHistoryIncluded`; `Saving` takes `historyLimits`.
+- **Helpers for reading money and questions in a chat, for the project status work.** `amountsOf(text)` returns
+  every amount in a text, in order (`amountOf` is its first). `MONEY_REQUEST`, `MONEY_DONE` and `PROMISE` word lists
+  (ru, en, es) with `moneyClassesOf(text)` say which a text uses. `questions(messages, { asker: "owner" })` lists the
+  owner's own questions and whether anyone but the owner answered them, by a reply or by speaking next; the default,
+  `"others"`, is what it did before. `linkedChatsOf` is exported, now with each link's `role`, and so is
+  `AGENDA_DEFAULTS`, the silence `tasks agenda` waits before it lists a chat.
+- **A command's own history handler learns whether each batch reached the store**: `HistoryBatchHandler` takes
+  `saved`, a promise of the same `true` or `false` the messenger gets, so a link can count only what was kept.
+- **Every messenger command that takes a chat or a message also takes the reference other WireCat CLIs print**:
+  `chat:<provider>/<account>/<chat>` wherever a chat is named (`messages list chat:max/34871122/63488582`, bot
+  commands too), and `msg:<provider>/<account>/<chat>/<message>` wherever a chat or a message is, online and offline. A person lookup takes `contact:<provider>/<id>`. A reference of another
+  account is refused, naming the account it belongs to and the profiles of this CLI the store saw on it; it never
+  switches account. One of another messenger is refused with the command that opens it (`open it with tg <profile>
+  messages list chat:telegram/…`), and another kind (`document:413` given as a chat) with what the argument takes.
+- **`event:<id>` and `meeting:<account>/<meeting>[/<transcript>[/<cue>]]` parse with `parseReference`** and
+  `canonicalReference`, as every other kind: `event:N` was printed by the calendar and person answers and could not be
+  read back. The kinds are one table, `REF_KINDS`; `looksLikeReference(text)` tells a reference from a title such as
+  `Note: plan`. Reference errors carry a reason: `ref.malformed`, `ref.unknown-kind` (with the kind meant:
+  `"doc:413" … did you mean document:413?`), `ref.wrong-kind`, `ref.wrong-provider`, `ref.wrong-account`.
+- **`messages list` reads a window bounded on both sides, offline too.** The query takes a start and an end,
+  `'date>=2026-10-01 date<2026-10-20'` or `'date:[2026-10-01 TO 2026-10-19]'`, and `id>` with `date<`. A start reads
+  forward, oldest first, and stops at the end; an end alone reads back from it, newest page first, as before.
+  `--offline` and a messenger whose history is read from the store (WhatsApp) now answer both ways from the store
+  instead of refusing. A forward cursor carries the end, `after:<id>~<epoch ms>`, so the next page stops at the same
+  place. `--since`, `--since-time`, `--until`, `--until-time`, `--after-time` and `--before-time` on `messages list`
+  fail with the query form to type instead. The store's `messages()` window takes `after` (a message or a moment)
+  and `until`.
+- **One proposal inbox behind one check: `proposalRegistry(store, policy)`, `ProposalKind`, `parseProposalIds`
+  (`@wirecat/cli-core/services`) and `mayDecide` (`@wirecat/cli-core/store`).** The registry lists every pending
+  proposal newest first across kinds (`relationship`, `key_document`, `fact`, `memory`, `findings` for evidence
+  findings, and `action` for every other stored proposal), and decides many ids at once, each on its own: the answer
+  lists `decided` and `refused`, and one refusal never undoes the others. A new kind registers itself with its id
+  `prefix` or the `stored` proposal kinds it owns; nothing else changes. `parseProposalIds` reads
+  `17070-17079,fact:500-502,17080/f2` and refuses a range across prefixes. Unconfirmed agent and rule links show as
+  `link:<id>` (relationships) and `key:<id>` (key documents) until the store moves them.
+- **`knowledge.proposeRelation(scope, input, by)`**: an agent's or a rule's relationship is a stored `relationship`
+  proposal for the owner, not a link; the same pending pair returns the proposal already held. Removing a link to a
+  project, or rejecting any suggested link, leaves a rejected `relationship` proposal, so a later scan can skip it.
+- **`proposedActions.list({ kinds, except, project, proposedBy })`**, `proposedBy` on `facts.list` and
+  `memories.list`, `order: "created"` on `facts.list`, and the bot's `kind` (`agent` or `rule`) on the author of a
+  proposed action, a fact, a memory and an evidence findings batch; bots may have the kind `rule`, and an `Author` may
+  name it.
+- **`knowledge.decideLinkProposal(id, decision)`** decides a stored `relationship` or `key_document` proposal, and
+  **`knowledge.decideSuggestedLink(id, decision)`** an older unconfirmed link, each in one transaction: the link and
+  the decision land together or not at all. A decision's `reason` is kept: on a rejected proposal as its result, on a
+  fact in `metadata.decision`, on an evidence findings receipt.
+
+### Changed — may break callers
+
+- **`SERVER_BOUNDS.maxMessageBytes`, `ServerSearched.tooLarge` and `search.server-too-large` are gone**: a big
+  candidate is no longer left on the server; see `textBytes`, `ServerSearched.partial` and `search.server-partial`.
+- **An option after `--` is read as the option.** `messages sync -- -100 --json` now syncs `-100` and answers in JSON;
+  it failed with "too many arguments". After `--`, a word that is exactly one of the command's options, its own or a
+  global one (`--json`, `--limit 5`, `--json=id`), moves in front of `--`; every other word stays a positional. A
+  negative id needs no `--` at all. Commands that take free text keep every word after `--` literal: `messages send` and
+  `edit` (also the bot's), `polls create`, `topics create`, `chats create`, `chats folders create`, `contacts rename`,
+  `contacts aliases set`, `messages press`, `bot commands set`, `schedule command`, `events remind`, `complete`, and the
+  notes templates. Mark such a command with `annotate(command, { literal_after_dashes: true })`; MCP calls are never
+  lifted. A script that passed the literal word `--json` as a positional of another command now gets the option instead.
+- **A write to a calendar the account may only read refuses before anything is asked or journaled**
+  (`calendar.read-only`): create, quick add, import, update, delete, respond and move, for a feed and for a provider's
+  `reader` or `free-busy` calendar alike. Before, only the target of a move was checked; the provider refused the rest.
+  `calendars busy` and `search --backend server` leave feed calendars out.
+- **A locator of another account or messenger is refused with a new text and a reason.** `messages show`, `context`,
+  `link` and `download` said "that locator belongs to another account; select its profile first" or "…belongs to
+  another messenger"; they now say `<ref> belongs to account <id>; profile <name> is account <id>` (`ref.wrong-account`)
+  or `<ref> is a <messenger> message; open it with …` (`ref.wrong-provider`). A script matching the old text matches
+  the reason instead.
+- **A text of the form `<kind>:<no spaces>` given as a chat is read as a reference**, so a chat titled `note:plan` is
+  no longer found by that title; give its id or a part of the title.
+- The provider seeds of `telegram`, `max` and `whatsapp` name their CLI (`command: tg`, `max`, `wa`), which a
+  provider clash message now shows (`telegram (messages, from tg)`).
+- **Every decide method takes who decides, a `Decider`** (`"owner"` or `{ bot, model?, reason }`):
+  `facts.accept(ref, by)`, `facts.reject(ref, by)`, `memories.confirm(ref, by)`, `knowledge.confirmRelation(scope, id,
+  by)`, `knowledge.removeRelation(scope, id, by)`, `proposedActions.approve(id, by, result?)`,
+  `proposedActions.reject(id, by)`, `approveAsTask(store, id, by)`, and `by` is now required in
+  `evidenceFindings.review` and `meetingFindings.review`. `DocumentKnowledge.fact` and `.memory` take `by` for a
+  `confirm`, and `memories.markStale(ref, by)` and `.memory(…, "stale", by)` take it too: marking an agent's memory
+  stale is how it is turned down. `knowledge.relate` needs `by`: the owner's relationship is a link, an agent's is a
+  `relationship` proposal it returns instead. `notes.addLink` refuses any confirmed link without `by: "owner"`, so an
+  agent writes `confirmed: false` (the task service now does). `notes.removeLink(id, by)`, `facts.reverse(ref, by)`,
+  `facts.remove(ref, by)` and `memories.remove(ref, by)` take who removes; the document port's `addMemory` needs
+  `author`, `addFact` and `addLink` need `by`, with no owner default. `proposalRegistry(store)` takes no policy: the
+  host sets it once with `openStore({ decisions })`, and `store.decisionPolicy` is what the registry and every store
+  check read. A host passes the owner only when the owner runs the command, and
+  the agent's bot and reason otherwise.
+  An agent's confirmation of a relationship is recorded in the link's provenance, and of a fact or proposal as its
+  decider.
+
+### Fixed
+
+- **A sum written in groups of three read as the wrong amount: `50 000 ₽` was `0` and `4 300 ₽` was `300`**, because
+  only the last group was read. Groups after a space, a no-break or thin space, a dot or a comma (`50 000`,
+  `1.200 €`, `$1,200`) are one number now, a decimal part after them is kept (`5 000.50 ₽`), and amounts keep two
+  decimals instead of a whole number (`15.5 eur` was 16). This is the amount the duplicate check compares between
+  two tasks, so a reminder worded with a grouped sum is no longer compared on the wrong figure.
+- **`page.next` of `messages list` and `messages comments` runs as written.** It repeated the query's `id`/`date`
+  bound beside `--cursor`, which the command refuses as two starting points; it now keeps only `topic:` and
+  `starred:`.
+- **An inclusive start keeps a message sent exactly at it.** `messages list 'date>=2026-10-01'` skipped a message
+  sent at the first millisecond of the day, and `date<="…"` one sent at that moment.
+
+### Security
+
+- **An agent can no longer decide its own proposal.** Before, `facts.accept`/`reject`,
+  `memories.confirm`, `knowledge.confirmRelation`, `proposedActions.approve`/`reject`, `approveAsTask` and both
+  findings reviews never asked who decided, so over MCP an agent could confirm what it had proposed itself. Every one
+  of them, and the registry, now runs `mayDecide`: the owner always may; an agent needs a reason
+  (`proposal.reason-required`), is refused its own bot's proposal (`proposal.own`), a rule scorer's proposal and one
+  that names no author (`proposal.owner-only`), and every decision when the host turns agent decisions off
+  (`proposals.agent-decisions-off`). An agent can no longer add a memory already `confirmed`, mark its own memory
+  stale, write a confirmed project link itself, or remove a link. A link records only free-text provenance, which
+  anyone can write, so only the owner decides an unconfirmed link or removes a link; the rejected record a removal
+  leaves names who removed it. Findings an agent accepted for the owner record that agent, not the owner. Only the
+  owner removes or reverses an accepted fact or another bot's memory; an agent withdraws only its own row while it is
+  proposed. Turning agent decisions off now holds for every store method, not only the registry, and a bot is the
+  same bot whatever its letter case (`Claude-Code` is `claude-code`).
+
 ## 0.546.0 — 02.11.2026
 
 ### Added

package/dist/calendar/cli/answers.d.ts

@@ -24,7 +24,7 @@ export declare const calendarFeed: v.StrictObjectSchema<{
     readonly events: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
     readonly hint: v.StringSchema<undefined>;
 }, undefined>;
-/** `calendars remove`: the feed's calendar, no longer synced, and how many stored entries were marked deleted. */
+/** `calendars remove`: the feed's calendar, gone, how many stored entries were deleted, and how many events with them. */
 export declare const calendarFeedRemoval: v.StrictObjectSchema<{
     readonly id: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.MinLengthAction<string, 1, undefined>]>;
     readonly external_id: v.StringSchema<undefined>;
@@ -35,6 +35,7 @@ export declare const calendarFeedRemoval: v.StrictObjectSchema<{
     readonly synced: v.BooleanSchema<undefined>;
     readonly seen_at: v.NullableSchema<v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.IsoTimestampAction<string, "an ISO 8601 time in UTC">, v.EndsWithAction<string, "Z", "an ISO 8601 time in UTC, ending in `Z`">]>, undefined>;
     readonly removed: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
+    readonly events: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
 }, undefined>;
 export declare const calendarBusy: v.StrictObjectSchema<{
     readonly start: v.SchemaWithPipe<readonly [v.StringSchema<undefined>, v.IsoTimestampAction<string, "an ISO 8601 time in UTC">, v.EndsWithAction<string, "Z", "an ISO 8601 time in UTC, ending in `Z`">]>;
@@ -100,11 +101,15 @@ export declare const calendarSync: v.StrictObjectSchema<{
         readonly embedded: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
         readonly left: v.BooleanSchema<undefined>;
     }, undefined>, undefined>;
-    /** Each feed's events as read, and how many it could not take (`syncWithFeeds`). */
+    /**
+     * Each feed's events as read, and how many it could not take (`syncWithFeeds`); `unchanged` when the feed answered
+     * 304 and the counts are those of the read before.
+     */
     readonly feeds: v.OptionalSchema<v.ArraySchema<v.StrictObjectSchema<{
         readonly calendar_id: v.NumberSchema<undefined>;
         readonly events: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
         readonly skipped: v.SchemaWithPipe<readonly [v.NumberSchema<undefined>, v.IntegerAction<number, undefined>, v.MinValueAction<number, 0, undefined>]>;
+        readonly unchanged: v.OptionalSchema<v.LiteralSchema<true, undefined>, undefined>;
     }, undefined>, undefined>, undefined>;
 }, undefined>;
 export declare const calendarSyncProgress: v.StrictObjectSchema<{

package/dist/calendar/cli/answers.js

@@ -21,8 +21,8 @@ export const calendar = v.strictObject({
 });
 /** `calendars add`: the feed's calendar, how many events the feed holds now, and the sync to run next. */
 export const calendarFeed = v.strictObject({ ...calendar.entries, events: count, hint: text });
-/** `calendars remove`: the feed's calendar, no longer synced, and how many stored entries were marked deleted. */
-export const calendarFeedRemoval = v.strictObject({ ...calendar.entries, removed: count });
+/** `calendars remove`: the feed's calendar, gone, how many stored entries were deleted, and how many events with them. */
+export const calendarFeedRemoval = v.strictObject({ ...calendar.entries, removed: count, events: count });
 const busyRow = v.strictObject({
     /** One of the account's calendars, by its id; or `person`, by the address asked. */
     calendar: v.optional(id),
@@ -72,8 +72,16 @@ export const calendarSync = v.strictObject({
     hint: v.optional(text),
     /** What `sync --embed` embedded: `embedEvents`' answer. */
     embeddings: v.optional(v.strictObject({ model: text, embedded: count, left: v.boolean() })),
-    /** Each feed's events as read, and how many it could not take (`syncWithFeeds`). */
-    feeds: v.optional(v.array(v.strictObject({ calendar_id: v.number(), events: count, skipped: count }))),
+    /**
+     * Each feed's events as read, and how many it could not take (`syncWithFeeds`); `unchanged` when the feed answered
+     * 304 and the counts are those of the read before.
+     */
+    feeds: v.optional(v.array(v.strictObject({
+        calendar_id: v.number(),
+        events: count,
+        skipped: count,
+        unchanged: v.optional(v.literal(true)),
+    }))),
 });
 export const calendarSyncProgress = v.strictObject({
     calendar_id: id,

package/dist/calendar/cli/index.js

@@ -3,7 +3,7 @@ import { annotate, sharedCommand } from "@wirecat/cli-base/commands";
 import { timezoneOf } from "@wirecat/cli-base/query";
 import { clockMeta } from "@wirecat/cli-base/standards";
 import { Argument, InvalidArgumentError, Option } from "commander";
-import { environmentOf, runBudgetOf } from "../../cli/context.js";
+import { environmentOf, outputFor, runBudgetOf } from "../../cli/context.js";
 import { honoursDryRun } from "../../cli/dry-run-guard.js";
 import { changesStore, ownerOnlyOption, writesFileOnlyWith } from "../../cli/effects.js";
 import { queryTerms, withQuery } from "../../cli/list-query.js";
@@ -14,7 +14,7 @@ import { searchEvents } from "../../services/events-search.js";
 import { dateWindow } from "../../services/moment.js";
 import { linkPeople } from "../../services/people.js";
 import { BUSY_QUERY, BUSY_QUERY_NOTE, busyAnswer, busyQuery, workingHoursOf } from "../busy.js";
-import { isFeedCalendar, syncWithFeeds } from "../feeds.js";
+import { isFeedCalendar, isPlainHttp, syncWithFeeds } from "../feeds.js";
 import { eventPreparation, nextMeeting, PREPARE_MESSAGES } from "../prepare.js";
 import { accountsMeta, CALENDAR_UNTRUSTED_FIELDS, calendarIn, calendarItem, EVENTS_QUERY, EVENTS_QUERY_NOTE, EXPORT_MAX, eventAnswer, eventIdOf, eventOf, eventsAnswer, eventsFilter, eventsIcs, peopleAnswer, resolveAnswer, reviewsAnswer, sourceAccounts, weekFilter, } from "../reads.js";
 import { REPEAT_HELP } from "../recurrence.js";
@@ -30,8 +30,6 @@ const REMOTE_READ = { remote: "read", local: "none" };
 const LOCAL_OR_REMOTE_READ = { remote: "read", local: "read" };
 const REMOTE_WRITE = { remote: "write", local: "write" };
 const GROUP = { remote: "none", local: "none" };
-/** Every time a store can hold, for marking all of a calendar's entries at once. */
-const EVERYWHERE = { from: -8.64e15, to: 8.64e15 };
 /** How many pieces one `sync --embed` embeds, as drive's. */
 const EMBED_MAX = 600;
 // A list's marker goes on each item: a host's list envelope is strict and `--jsonl` prints only the items.
@@ -130,6 +128,9 @@ const addCalendarCommandsDefinition = (program, deps) => {
             if (command.optsWithGlobals().offline)
                 throw new CliError("permission_error", "calendars add reads the feed; leave out --offline");
             const { calendar, events } = await feeds().add(url, opts.title === undefined ? {} : { title: opts.title });
+            if (isPlainHttp(url))
+                outputFor(command).renderer.warn("this feed's address starts with http://, so the feed and any token in its address travel unencrypted; " +
+                    "use https:// if the server offers it");
             const [saved] = await deps.store.saveCalendars(deps.accountId, [calendar], now());
             print({
                 ...calendarItem(saved),
@@ -138,7 +139,8 @@ const addCalendarCommandsDefinition = (program, deps) => {
             }, command);
         });
         example(annotate(calendars.command("remove"), { effects: LOCAL_WRITE, mcp: false })
-            .description("stop following a feed calendars add added: its address is forgotten and its stored events go")
+            .description("stop following a feed calendars add added: its address is forgotten and its stored events are deleted, " +
+            "not cancelled. Only a feed; calendars unsync stops a provider's calendar")
             .argument("<calendar>", "the feed calendar's id, its ics: id, or its title"), "calendars remove 7").action(async (reference, _opts, command) => {
             const calendar = await calendarIn(deps.store, deps.accountId, reference);
             if (!isFeedCalendar(calendar))
@@ -146,9 +148,8 @@ const addCalendarCommandsDefinition = (program, deps) => {
                     reason: "feed.not-a-feed",
                 });
             await feeds().remove(calendar.externalId);
-            await deps.store.setCalendarSynced(calendar.id, false, now());
-            const removed = await deps.store.markUnseen(calendar.id, now() + 1, EVERYWHERE, now());
-            print({ ...calendarItem({ ...calendar, synced: false }), removed }, command);
+            const { entries, events } = await deps.store.forgetCalendar(calendar.id, now());
+            print({ ...calendarItem({ ...calendar, synced: false }), removed: entries, events }, command);
         });
     }
     if (deps.freeBusy)

package/dist/calendar/feeds.d.ts

@@ -28,6 +28,8 @@ export interface FeedSyncStats {
     calendarId: number;
     events: number;
     skipped: number;
+    /** The feed answered 304: nothing was read again, and the counts are those of the read before. */
+    unchanged?: true;
 }
 /** The profile's iCalendar feeds: a source the engine expands locally, and how one is added and forgotten. */
 export interface CalendarFeeds {
@@ -47,6 +49,8 @@ export interface CalendarFeeds {
 }
 /** `webcal://` is `https://`: calendar apps write it so a click opens them, and the feed itself is served over https. */
 export declare const feedAddress: (text: string) => URL;
+/** An `http://` address: allowed, but the feed and any token in its address travel unencrypted. */
+export declare const isPlainHttp: (text: string) => boolean;
 export interface FetchFeedOptions {
     /** Names the feed in errors; the address never appears in one. */
     name: string;
@@ -54,11 +58,26 @@ export interface FetchFeedOptions {
     signal?: AbortSignal;
     limits?: FeedLimits;
 }
+/** The last answer's `ETag` and `Last-Modified`, sent back so the server can say the feed has not changed. */
+export interface FeedValidators {
+    etag: string | null;
+    lastModified: string | null;
+}
 /**
  * The feed's text: http or https, each redirect followed by hand and only to https, the body cut off at its limit and
  * the request at its time. Errors name the feed and the status, never the address, which may hold a token.
  */
 export declare const fetchFeed: (address: string, options: FetchFeedOptions) => Promise<string>;
+/**
+ * `fetchFeed` that sends `since` as `If-None-Match` and `If-Modified-Since`: `"unchanged"` when the server answers 304,
+ * otherwise the text and the validators to send next time.
+ */
+export declare const fetchFeedIfChanged: (address: string, options: FetchFeedOptions & {
+    since?: FeedValidators;
+}) => Promise<{
+    text: string;
+    validators: FeedValidators;
+} | "unchanged">;
 /** One feed event in the neutral words, its text cleaned as an invitation's is: feed text is somebody else's. */
 export declare const feedEntry: (event: IcsEvent, zone: string) => EntryInput;
 export interface FeedRead {

package/dist/calendar/feeds.js

@@ -26,6 +26,8 @@ export const feedAddress = (text) => {
         throw invalidAddress("must not hold a user name or a password");
     return url;
 };
+/** An `http://` address: allowed, but the feed and any token in its address travel unencrypted. */
+export const isPlainHttp = (text) => feedAddress(text).protocol === "http:";
 const sameAddress = (a, b) => feedAddress(a).href === feedAddress(b).href;
 const readBody = async (response, name, maxBytes) => {
     const reader = response.body?.getReader();
@@ -58,8 +60,17 @@ const STATUS_ERRORS = {
  * The feed's text: http or https, each redirect followed by hand and only to https, the body cut off at its limit and
  * the request at its time. Errors name the feed and the status, never the address, which may hold a token.
  */
-export const fetchFeed = async (address, options) => {
-    const { name, limits = FEED_LIMITS } = options;
+export const fetchFeed = async (address, options) => (await fetchFeedIfChanged(address, options)).text;
+/**
+ * `fetchFeed` that sends `since` as `If-None-Match` and `If-Modified-Since`: `"unchanged"` when the server answers 304,
+ * otherwise the text and the validators to send next time.
+ */
+export const fetchFeedIfChanged = async (address, options) => {
+    const { name, limits = FEED_LIMITS, since } = options;
+    const conditional = {
+        ...(since?.etag ? { "if-none-match": since.etag } : {}),
+        ...(since?.lastModified ? { "if-modified-since": since.lastModified } : {}),
+    };
     const run = options.fetch ?? fetch;
     const timeout = AbortSignal.timeout(limits.timeoutMs);
     const signal = options.signal ? AbortSignal.any([options.signal, timeout]) : timeout;
@@ -69,8 +80,12 @@ export const fetchFeed = async (address, options) => {
             const response = await run(url, {
                 redirect: "manual",
                 signal,
-                headers: { accept: "text/calendar, text/plain;q=0.5, */*;q=0.1" },
+                headers: { accept: "text/calendar, text/plain;q=0.5, */*;q=0.1", ...conditional },
             });
+            if (response.status === 304 && Object.keys(conditional).length) {
+                await response.body?.cancel();
+                return "unchanged";
+            }
             const location = response.headers.get("location");
             if (response.status >= 300 && response.status < 400 && location) {
                 await response.body?.cancel();
@@ -95,7 +110,11 @@ export const fetchFeed = async (address, options) => {
                     retryable: response.status >= 500 || response.status === 429,
                 });
             }
-            return await readBody(response, name, limits.maxBytes);
+            const text = await readBody(response, name, limits.maxBytes);
+            return {
+                text,
+                validators: { etag: response.headers.get("etag"), lastModified: response.headers.get("last-modified") },
+            };
         }
     }
     catch (error) {
@@ -213,6 +232,19 @@ export const readFeed = (text, zone, window) => {
         skipped,
     };
 };
+const lastRead = (token, window) => {
+    if (token === null)
+        return null;
+    try {
+        const held = JSON.parse(token);
+        if (held?.v !== 1 || held.window?.from !== window.from || held.window.to !== window.to || !held.validators)
+            return null;
+        return held;
+    }
+    catch {
+        return null;
+    }
+};
 const calendarOf = (feed, timezone = null) => ({
     externalId: `${FEED_PREFIX}${feed.id}`,
     title: feed.title,
@@ -236,8 +268,9 @@ export const icsFeeds = (options) => {
             });
         return feed;
     };
-    const read = (url, name) => fetchFeed(url, {
+    const read = (url, name, since) => fetchFeedIfChanged(url, {
         name,
+        ...(since ? { since } : {}),
         ...(options.fetch ? { fetch: options.fetch } : {}),
         ...(options.signal ? { signal: options.signal } : {}),
         ...(options.limits ? { limits: options.limits } : {}),
@@ -248,9 +281,16 @@ export const icsFeeds = (options) => {
         async calendars() {
             return (await options.registry.read()).map((feed) => calendarOf(feed));
         },
-        async changes(calendar, { window }) {
+        async changes(calendar, { cursor, window }) {
             const feed = await feedOf(calendar.externalId);
-            const text = await read(feed.url, `feed ${calendar.id}`);
+            const held = lastRead(cursor, window);
+            const got = await read(feed.url, `feed ${calendar.id}`, held?.validators);
+            if (got === "unchanged") {
+                const [events, skipped] = [held?.events ?? 0, held?.skipped ?? 0];
+                stats.set(calendar.id, { calendarId: calendar.id, events, skipped, unchanged: true });
+                return { entries: [], removed: [], cursor, unchanged: true };
+            }
+            const { text, validators } = got;
             const found = readFeed(text, calendar.timezone ?? options.zone, window);
             for (const entry of found.entries) {
                 const changed = found.overrides.get(entry.externalId);
@@ -258,7 +298,10 @@ export const icsFeeds = (options) => {
                     overridesOf.set(entry, changed);
             }
             stats.set(calendar.id, { calendarId: calendar.id, events: found.events, skipped: found.skipped });
-            return { entries: found.entries, removed: [], cursor: null };
+            const next = validators.etag || validators.lastModified
+                ? { v: 1, validators, window, events: found.events, skipped: found.skipped }
+                : null;
+            return { entries: found.entries, removed: [], cursor: next && JSON.stringify(next) };
         },
     };
     return {
@@ -271,7 +314,7 @@ export const icsFeeds = (options) => {
                 throw new CliError("validation_error", "this profile follows a feed at this address already", {
                     reason: "feed.duplicate",
                 });
-            const found = readFeed(await read(address, "the feed"), options.zone);
+            const found = readFeed((await read(address, "the feed")).text, options.zone);
             const feed = {
                 id: randomBytes(6).toString("hex"),
                 url: address,

package/dist/calendar/source.d.ts

@@ -13,7 +13,10 @@ export interface CalendarSourceTraits {
     expands: "on-request" | "in-changes" | "local";
     /** The cursor encodes the window (Graph delta): a new window means a new full round. */
     cursorHoldsWindow: boolean;
-    /** No incremental cursor: every run is a full list (an ICS feed). */
+    /**
+     * No incremental cursor: every run is a full list (an ICS feed). The token the last list gave still reaches
+     * `changes()`, so the source can ask whether anything changed since.
+     */
     fullListOnly: boolean;
 }
 export interface ChangePage {
@@ -27,6 +30,11 @@ export interface ChangePage {
     nextPage?: string;
     /** On the last page: the cursor for the next run; `null` when the source has none. */
     cursor?: string | null;
+    /**
+     * A full-list source's list is the one its token was given with (an ICS feed's 304): nothing was read, so nothing
+     * is saved and nothing stored is marked unseen. Only on a single page with no entries.
+     */
+    unchanged?: true;
 }
 /** `reset`: the cursor is dead (Google 410, Graph `syncStateNotFound`, CalDAV `valid-sync-token`). */
 export type ChangeResult = ChangePage | {
@@ -61,7 +69,7 @@ export interface CalendarSource {
     readonly provider: string;
     readonly traits: CalendarSourceTraits;
     calendars(): Promise<CalendarInput[]>;
-    /** `cursor: null` asks for a full list of the window. */
+    /** `cursor: null` asks for a full list of the window; a `fullListOnly` source lists in full whatever it is given. */
     changes(calendar: StoredCalendar, request: {
         cursor: string | null;
         page?: string;

package/dist/calendar/sync.d.ts

@@ -23,6 +23,8 @@ export interface PendingRound {
     series: string[];
     /** A full round asks every series it lists; otherwise only those that changed. Absent reads as true. */
     everySeries?: boolean;
+    /** The source said its list is unchanged since `from`: the round marks nothing unseen. */
+    unchanged?: true;
 }
 /** What the engine keeps in `EventStore.cursor`. Version 1 had no `round`, `updatedAt` or `done`. */
 export interface CalendarCursor {

package/dist/calendar/sync.js

@@ -29,7 +29,7 @@ const roundOf = (value) => {
         round.series.some((id) => typeof id !== "string") ||
         (round.everySeries !== undefined && typeof round.everySeries !== "boolean"))
         return undefined;
-    const { full, from, window, startedAt, reset, page, listed, next, series, everySeries } = round;
+    const { full, from, window, startedAt, reset, page, listed, next, series, everySeries, unchanged } = round;
     return {
         full,
         from,
@@ -41,6 +41,7 @@ const roundOf = (value) => {
         next,
         series,
         ...(everySeries === false ? { everySeries } : {}),
+        ...(unchanged === true ? { unchanged } : {}),
     };
 };
 export const parseCalendarCursor = (value) => {
@@ -87,9 +88,9 @@ export const calendarSyncWindow = (now) => {
     return { from: Date.UTC(year - 1, month, date), to: Date.UTC(year, month + 3, date) };
 };
 const CONTINUE = "run sync again to continue";
-const freshRound = (full, from, window, now, reset = false, everySeries = true) => ({
+const freshRound = (full, from, window, now, reset = false, everySeries = true, keepToken = false) => ({
     full,
-    from: full ? null : from,
+    from: full && !keepToken ? null : from,
     window,
     startedAt: now,
     reset,
@@ -112,7 +113,7 @@ const roundFor = (source, stored, { window, now }) => {
     // The daily full round asks only the series that changed, and every series once the window's end moved on far
     // enough that their new slots matter (foundation §6.2 step 7).
     const everySeries = !full || stored?.slotsTo === undefined || window.to - stored.slotsTo >= SLOTS_EVERY;
-    return freshRound(full, stored?.token ?? null, window, now, false, everySeries);
+    return freshRound(full, stored?.token ?? null, window, now, false, everySeries, source.traits.fullListOnly);
 };
 const deadList = (provider) => new CliError("invalid_response", `${provider} refused a full list as a dead cursor`);
 /**
@@ -218,7 +219,9 @@ const syncOne = async ({ source, store, calendar, window, now, expand, budget, s
         }
         if (page.removed.length)
             result.removed += await store.removeEntries(calendar.id, page.removed, now);
-        if (page.nextPage === undefined)
+        if (page.unchanged && source.traits.fullListOnly && page.entries.length === 0 && page.nextPage === undefined)
+            round = { ...round, page: null, listed: true, next: page.cursor ?? null, unchanged: true };
+        else if (page.nextPage === undefined)
             round = { ...round, page: null, listed: true, next: page.cursor ?? null };
         else {
             if (seen.has(page.nextPage))
@@ -260,7 +263,8 @@ const syncOne = async ({ source, store, calendar, window, now, expand, budget, s
     }
     if (signal?.aborted)
         return "cancelled";
-    result.unseen = round.full ? await store.markUnseen(calendar.id, round.startedAt, round.window, now) : 0;
+    result.unseen =
+        round.full && !round.unchanged ? await store.markUnseen(calendar.id, round.startedAt, round.window, now) : 0;
     await save({
         token: round.next,
         window: round.window,

package/dist/calendar/testing/memory.js

@@ -343,6 +343,45 @@ export const memoryEventStore = () => {
         async setCalendarSynced(calendarId, synced) {
             calendarOf(calendarId).synced = synced;
         },
+        async forgetCalendar(calendarId, now) {
+            const calendar = calendarOf(calendarId);
+            const mine = entries.filter((one) => one.calendarId === calendarId);
+            const ids = new Set(mine.map(({ id }) => id));
+            const eventIds = new Set(mine.flatMap(({ eventId }) => (eventId === null ? [] : [eventId])));
+            const seriesIds = new Set(mine.flatMap(({ eventSeriesId }) => (eventSeriesId === null ? [] : [eventSeriesId])));
+            for (let at = entries.length - 1; at >= 0; at--)
+                if (ids.has(entries[at].id))
+                    entries.splice(at, 1);
+            for (let at = revisions.length - 1; at >= 0; at--)
+                if (ids.has(revisions[at].entryId))
+                    revisions.splice(at, 1);
+            for (let at = reviews.length - 1; at >= 0; at--)
+                if (reviews[at].linkableType === "calendar_entry" &&
+                    ids.has(reviews[at].linkableId))
+                    reviews.splice(at, 1);
+            participants = participants.filter((one) => !ids.has(one.entryId));
+            attachments = attachments.filter((one) => !ids.has(one.entryId));
+            for (const id of ids)
+                unlinked.delete(id);
+            let gone = 0;
+            for (const id of eventIds)
+                if (entries.some((one) => one.eventId === id))
+                    refreshEvent(id, now);
+                else if (events.delete(id))
+                    gone++;
+            for (const id of seriesIds)
+                if (entries.some((one) => one.eventSeriesId === id))
+                    refreshSeries(id);
+                else {
+                    series.delete(id);
+                    for (const event of events.values())
+                        if (event.eventSeriesId === id)
+                            event.eventSeriesId = null;
+                }
+            cursors.delete(calendarId);
+            calendars.splice(calendars.indexOf(calendar), 1);
+            return { entries: ids.size, events: gone };
+        },
         async saveEntries(calendarId, list, now) {
             calendarOf(calendarId);
             for (const input of list)