frontpage-host 0.3.2 → 0.3.3

package/MAIL.md

@@ -29,7 +29,7 @@ For an existing record, supply `id` and `expectedUpdatedAt` from `mail template
 
 The response reports `complete:true` and the saved records. Keep the exact payload and requestKey after a lost response. Repeating it returns the saved IDs without adding another template or step. Do not reuse a key for different content. A 409 means the saved version changed: retain the draft, read the current records, review the changes, and use a new key for the revised save. A failed transaction saves neither half. Subject, preview text, name and valid content are required. Saving never activates a series or sends email. Queued emails keep their saved content.
 
-The workspace's Back button returns to the source series and keeps unfinished work. A test sends only to the signed-in account in the workspace, and does not complete a step task. CLI test recipients remain explicit and subject to the existing test restrictions.
+The workspace's Back button returns to the source series. If template edits are unsaved, the shared modal offers Cancel or Discard and continue. Discard loses the template edits; the pending source series stays in memory while this task is open. Leaving the whole task discards its unfinished work. Save & return and Save email & add step save the template and pending series together; there is no second Save series step. A test sends only to the signed-in account in the workspace, and does not complete a step task. CLI test recipients remain explicit and subject to the existing test restrictions.
 
 ## Group and stage email tasks
 
@@ -67,7 +67,7 @@ The response returns `complete:true`, `document` and `rule`. Repeating the same
 
 To attach an existing source, omit `document`. Add either `attachment.templateId` or `attachment.seriesId` and its `expectedSourceUpdatedAt` from a fresh template/series get. A series needs at least one saved step. The result includes the source and paused rule. To edit shared content from an existing entry rule, supply the existing document with `expectedUpdatedAt`, plus `attachment.ruleId` and `expectedRevision` from `rules.get`. This saves the content while leaving the rule's conditions, actions, version, enabled state, activation time and history unchanged. Stale group, stage, source or rule checks return a conflict; keep the draft and review the saved records before making a revised request.
 
-The workspace uses the existing template editor and returns to the source group or Stages after Save & return. Group, rule, stage, picker and template drafts use private recovery scoped to the signed-in user, site and browser tab. Duplicated tabs copy the recovery snapshot once and then save separately. Cancel uses the shared unsaved-changes confirmation. An unconfirmed completion must be recovered before leaving its task. A self-test sends only test content and does not complete a pending group task.
+The workspace uses the existing template editor and returns to the source group or Stages after Save & return. Unfinished group, rule, stage, picker and template edits stay in memory only. Leaving uses the shared unsaved-changes modal: Cancel keeps editing; Discard and continue loses those edits and leaves without a network request. Refresh or closing the tab discards unfinished work without a browser prompt. Clean navigation and opening saved records show no warning. There is no editor backup or Recover save action. A template task keeps its source context in memory during the active flow; a refreshed task must be reopened from its source. A self-test sends only test content and does not complete a pending group task. Retry a submitted save with the exact original key and payload after a lost response; this does not require an editor backup.
 
 Templates remain shared. Changes affect future uses; already queued messages keep their content snapshots. Template get exposes `ruleUsage`; the UI also shows rule usage beside existing dependencies. Deleting a template used by a live rule, including a paused rule, fails with a conflict naming the rule. Remove the template action or archive the rule first. Series, form and receipt dependencies still apply. Archiving a rule keeps its run history and saved actions. Never activate, enroll or send without the user's instruction.
 

package/PEOPLE.md

@@ -730,7 +730,7 @@ The response returns `complete:true`, `document` and `rule`. Repeating the same
 
 To attach an existing source, omit `document`. Add either `attachment.templateId` or `attachment.seriesId` and its `expectedSourceUpdatedAt` from a fresh template/series get. A series needs at least one saved step. The result includes the source and paused rule. To edit shared content from an existing entry rule, supply the existing document with `expectedUpdatedAt`, plus `attachment.ruleId` and `expectedRevision` from `rules.get`. This saves the content while leaving the rule's conditions, actions, version, enabled state, activation time and history unchanged. Stale group, stage, source or rule checks return a conflict; keep the draft and review the saved records before making a revised request.
 
-The workspace uses the existing template editor and returns to the source group or Stages after Save & return. Group, rule, stage, picker and template drafts use private recovery scoped to the signed-in user, site and browser tab. Duplicated tabs copy the recovery snapshot once and then save separately. Cancel uses the shared unsaved-changes confirmation. An unconfirmed completion must be recovered before leaving its task. A self-test sends only test content and does not complete a pending group task.
+The workspace uses the existing template editor and returns to the source group or Stages after Save & return. Unfinished group, rule, stage, picker and template edits stay in memory only. Leaving uses the shared unsaved-changes modal: Cancel keeps editing; Discard and continue loses those edits and leaves without a network request. Refresh or closing the tab discards unfinished work without a browser prompt. Clean navigation and opening saved records show no warning. There is no editor backup or Recover save action. A template task keeps its source context in memory during the active flow; a refreshed task must be reopened from its source. A self-test sends only test content and does not complete a pending group task. Retry a submitted save with the exact original key and payload after a lost response; this does not require an editor backup.
 
 Templates remain shared. Changes affect future uses; already queued messages keep their content snapshots. Template get exposes `ruleUsage`; the UI also shows rule usage beside existing dependencies. Deleting a template used by a live rule, including a paused rule, fails with a conflict naming the rule. Remove the template action or archive the rule first. Series, form and receipt dependencies still apply. Archiving a rule keeps its run history and saved actions. Never activate, enroll or send without the user's instruction.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "frontpage-host",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Frontpage CLI — manage your site from the terminal",
   "type": "module",
   "bin": {