- I1: an apply answer is a refusal only when our server sent it (a known
code, or a 4xx whose body says success:false); a proxy's 5xx, an
unreadable 2xx or a dropped connection says Outcome not confirmed and
reads Activity again. ApiError gains 'refused'; the server's own
pre-start failure is coded 'apply-failed'.
- M1: the lost-response test lets the apply run, then drops its answer.
- M2: a failed apply records its code in the job's scope; Activity offers
Review again for an overtaken plan (Maintenance for a duplicate cleanup
whose sources changed).
- M3: a failed duplicate cleanup toasts the server's reason.
- M4: a review button holds while its preview is read (one preview per
double press).
- M5: the storage guard also catches bracket and property assignment and
CacheStorage/IndexedDB opens; why the Toolkit build is skipped is
written down.
- M6: a refused storage listing says so on the Metadata cache row.
- M7, M8: D100 text corrected; workflow_storage has its title.
- M9: a busy start names the job the server named.
Vito Sansevero
a99a311e82