frontpage-host 0.3.14 → 0.3.15

package/AGENTS.md

@@ -264,7 +264,7 @@ Manual group selection uses `groups.people` (20 per page, phone-only contacts in
 
 ## AI Support Agent
 
-Scale and internal sites, after owner activation. No pilot allowlist. Use `frontpage customer-inbox get|put|post RESOURCE`, stable write keys and current versions. Full guide: [CUSTOMER-INBOX.md](./CUSTOMER-INBOX.md). `export CONVERSATION_ID --out FILE` writes authorized paginated history and file metadata; `download FILE_ID --out FILE` downloads through a file grant. Outputs never overwrite existing files. `frontpage usage` reports shared site credits, mail and storage. The owner toolbar uses `manage_customer_inbox` for all site-wide Inbox settings, unlocked knowledge, files, customer conversations, private guidance, replies, takeover/return and recovery. The support agent has a separate server-bound customer scope and requires verification for People data. Both agents cannot edit or unlock locked knowledge; human UI/CLI can unlock it. Never lend a website agent a human CLI key.
+Scale and internal sites, after owner activation. No pilot allowlist. Use `frontpage customer-inbox get|put|post RESOURCE`, stable write keys and current versions for settings, sources and conversations. Knowledge saves use last-save-wins; read the latest note before editing. Knowledge history supports limit/cursor pagination and full revision reads by version, within the plan Rewind allowance plus the latest revision. Archive notes through POST knowledge/ID/archive with {} to stop future use while preserving all records; do not archive without the owner asking. Full guide: [CUSTOMER-INBOX.md](./CUSTOMER-INBOX.md). `export CONVERSATION_ID --out FILE` writes authorized paginated history and file metadata; `download FILE_ID --out FILE` downloads through a file grant. Outputs never overwrite existing files. `frontpage usage` reports shared site credits, mail and storage. The owner toolbar uses `manage_customer_inbox` for all site-wide Inbox settings, unlocked knowledge, files, customer conversations, private guidance, replies, takeover/return and recovery. The support agent has a separate server-bound customer scope and requires verification for People data. Both agents cannot edit, archive or unlock locked knowledge; human UI/CLI can unlock it. Never lend a website agent a human CLI key.
 
 
 Payments, invoices and recurring billing: see packaged [PAYMENTS.md](./PAYMENTS.md), `frontpage help payments`, and https://frontpage.host/developers/payments. Version 0.2.0 removes writable currency, Store checkout mode and Store-owned money commands; Store stays cart-only. Preview/review before sends; keep stable operation keys on retries. Autopay requires the customer’s own verified authorization.

package/CUSTOMER-INBOX.md

@@ -50,9 +50,11 @@ Aliases use 3–48 ASCII letters, numbers and single hyphens. The service normal
 | --- | --- | --- |
 | `knowledge` | GET | Recent notes; optional `?q=search` |
 | `knowledge/<id>` | GET | One full note |
-| `knowledge/<id>/history` | GET | Immutable revisions for that note |
-| `knowledge` | PUT | `{"title":"Evening visits","body":"Ask the owner before promising an evening visit.","expectedVersion":0,"reason":"Owner policy"}` |
-| `knowledge/<id>` | PUT | Current title/body, `expectedVersion`, `reason`, optional `locked` or `restoreVersion` |
+| `knowledge/<id>/history?limit=20` | GET | Revision summaries, `nextCursor`, and the plan history allowance; follow `&cursor=...` |
+| `knowledge/<id>/history?version=3` | GET | One full revision within the plan allowance, or the latest version |
+| `knowledge/<id>/archive` | POST | `{}`; keeps content and history, removes the note from future use |
+| `knowledge` | PUT | `{"title":"Evening visits","body":"Ask the owner before promising an evening visit.","reason":"Owner policy"}` |
+| `knowledge/<id>` | PUT | Current title/body, `reason`, optional `locked` or `restoreVersion`; legacy `expectedVersion` is accepted but does not reject a save |
 | `sources` | GET | Approved source records; `?overview=true` also includes the latest learning job status |
 | `sources` | PUT | `{"url":"https://example.com/help","enabled":true,"expectedVersion":0}`; fetches public text |
 
@@ -73,7 +75,19 @@ The response data is the same source with `enabled:false` and version `3`; its s
 
 Supply `body` on a source write to save an owner-approved excerpt instead of fetching. Published sources refresh when the agent reads a source older than 24 hours. The fetcher reuses Core's DNS-pinned public HTTP infrastructure, rejects private addresses, checks redirects and bounds content. Sources over 16000 text characters require an owner-approved excerpt. No scripts run. A source version/digest fences knowledge updates against a changed source.
 
-Knowledge search uses bounded literal keywords from natural-language queries and ranks notes by matched terms. Read the full matching note before updating it; update its current ID/version instead of creating a conflicting duplicate.
+Knowledge search uses bounded literal keywords from natural-language queries and ranks notes by matched terms. Read the full matching note before updating it; read its latest content and update that same ID instead of creating a duplicate. Knowledge uses last-save-wins: two saves can both succeed; the last completed save becomes current, and each saved change stays in history. This does not change version checks for settings, approved sources, or conversations.
+
+History uses the same central Rewind allowance as template history. Scale includes 90 days; internal sites have uncapped history. The latest revision stays available regardless of age. Older snapshots remain stored, but history reads and restores only allow revisions within the allowance or the latest revision. A paginated response includes `revisions` (version, actor, createdAt), `currentVersion`, `nextCursor`, `windowDays`, `unlimited`, `canUpgrade`, and `moreBeyondWindow`. A `version` request returns `{revision}` with full saved content. Older callers that omit pagination keep their full-revision response shape, bounded to 100 entries and the same allowance.
+
+```bash
+frontpage customer-inbox get 'knowledge/NOTE_UUID/history?limit=20' --site my-site --json
+frontpage customer-inbox get 'knowledge/NOTE_UUID/history?limit=20&cursor=21' --site my-site --json
+frontpage customer-inbox get 'knowledge/NOTE_UUID/history?version=3' --site my-site --json
+# archive.json contains {}. Use the same file and key when retrying.
+frontpage customer-inbox post knowledge/NOTE_UUID/archive --file archive.json --request-key archive_note_001 --site my-site --json
+```
+
+Archiving retains the note and every revision, hides it from normal lists/searches and future agent reads, and prevents later saves from reactivating it. There is no archived-notes screen or permanent-delete action. Runs already in progress keep what they loaded. Archiving does not remove matching information from approved webpages or replies already sent.
 
 Lock a knowledge note with `locked:true`. Neither the support agent nor the owner toolbar agent can change locked notes or locks. Human UI/CLI actions can unlock them. Restore an older note with `restoreVersion`; the service creates a new revision and preserves the old history. The agent can change only internal knowledge, using verified owner guidance or a current approved source. It cannot edit public pages or articles.
 
@@ -372,7 +386,7 @@ The support agent has its own system prompt plus the versioned private business
 | --- | --- | --- |
 | `knowledge_read` | `query`, `id` or `sourceId` | Search internal notes or read complete approved evidence. |
 | `history_read` | `before`, optional `query` | Retrieve up to ten older eligible messages in the assigned conversation under the `knowledge_read` grant; bounded to 6000 text characters. |
-| `knowledge_update` | Optional `id`; `title`, `body`, `expectedVersion`, `reason`, `evidenceKind`, `evidenceId`; source `evidenceVersion` | Available only in a restricted learning job. Update unlocked business facts from that job's assigned owner guidance or approved source revision. One-off guidance stays in the conversation. No public editing. |
+| `knowledge_update` | Optional `id` and legacy `expectedVersion`; `title`, `body`, `reason`, `evidenceKind`, `evidenceId`; source `evidenceVersion` | Available only in a restricted learning job. Update unlocked business facts from that job's assigned owner guidance or approved source revision. One-off guidance stays in the conversation. No public editing. |
 | `customer_read` | `sections` (`profile`, `notes`, `orders`, `activity`), optional `before` | Read only the request-bound verified customer. Notes page 25 at a time; orders page 20. A cursor must belong to that same customer and site. Order ownership ambiguity for an app identity returns `account_mapping_required`, with no orders. |
 | `verify_customer` | None | Request proof at the server-bound mailbox and pause. Resume unanswered work after confirmation and People projection. No recipient selector. |
 | `customer_update` | `name`/`phone`, `evidenceMessageId` | Enrich from an explicit customer statement; cannot change identity or permission. |

package/README.md

@@ -113,7 +113,7 @@ An explicit stock target already equal to the current count is a no-op. Repeatin
 
 ### AI Support Agent
 
-Included on Scale and internal sites after owner activation. Use `frontpage customer-inbox` for settings, knowledge and customer conversations. The command and API paths keep their existing names. See [AI Support Agent](./CUSTOMER-INBOX.md) for permissions, private guidance, takeover, verification and shared usage.
+Included on Scale and internal sites after owner activation. Use `frontpage customer-inbox` for settings, knowledge and customer conversations. Knowledge saves use last-save-wins. Read paginated revision history within the plan Rewind allowance, or archive a note to stop future use without deleting its records. The command and API paths keep their existing names. See [AI Support Agent](./CUSTOMER-INBOX.md) for permissions, private guidance, takeover, verification and shared usage.
 
 ### Website models and AI credits
 

package/dist/commands/customer-inbox.js

@@ -5,7 +5,7 @@ import { takeFlag, assertNoUnknownFlags } from "../argv.js";
 import { getApiKey } from "../auth/keychain.js";
 import { apiBase, v1Get, httpErrorFromV1, CliHttpError, EXIT_AUTH, EXIT_USAGE, EXIT_OK, exitCodeForError, } from "../http/client.js";
 import { emitOk, emitErr, isJson } from "../runtime.js";
-const RESOURCE = /^(?:status|activation|address|widget|website|settings|knowledge(?:\/[0-9a-f-]+(?:\/history)?)?|sources(?:\/[0-9a-f-]+)?|blocks(?:\/[0-9a-f-]+\/unblock)?|jobs(?:\/[0-9a-f-]+(?:\/resume)?)?|files(?:\/[0-9a-f-]+)?|receipts(?:\/[0-9a-f-]+)?|conversations(?:\/[0-9a-f-]+(?:\/(?:messages|routing|guidance|reply|control|state|revoke-sessions|verification))?)?)(?:\?[^#]*)?$/;
+const RESOURCE = /^(?:status|activation|address|widget|website|settings|knowledge(?:\/[0-9a-f-]+(?:\/(?:history|archive))?)?|sources(?:\/[0-9a-f-]+)?|blocks(?:\/[0-9a-f-]+\/unblock)?|jobs(?:\/[0-9a-f-]+(?:\/resume)?)?|files(?:\/[0-9a-f-]+)?|receipts(?:\/[0-9a-f-]+)?|conversations(?:\/[0-9a-f-]+(?:\/(?:messages|routing|guidance|reply|control|state|revoke-sessions|verification))?)?)(?:\?[^#]*)?$/;
 export function inboxCommand(args) {
     const work = [...args], verb = work.shift(), resource = work.shift(), file = takeFlag(work, "--file"), key = takeFlag(work, "--request-key"), out = takeFlag(work, "--out");
     assertNoUnknownFlags(work, "customer-inbox");

package/dist/registry.js

@@ -428,12 +428,16 @@ export const COMMANDS = [
             "frontpage customer-inbox put settings --file ./inbox-settings.json --request-key settings_revision_1",
             "frontpage customer-inbox get conversations",
             "frontpage customer-inbox get knowledge",
+            "frontpage customer-inbox get 'knowledge/NOTE_UUID/history?limit=20'",
+            "frontpage customer-inbox post knowledge/NOTE_UUID/archive --file archive.json --request-key archive_note_001",
         ],
         flags: [
             "Available on Scale and internal sites after owner activation; no pilot allowlist",
             "Writes require a stable --request-key and a JSON file; reuse both on retries",
             "Human CLI and owner-agent tools manage authorized conversations; customer support tools stay bound to the verified customer",
             "Luna and 10× AI billing are fixed",
+            "Knowledge uses last-save-wins; history follows plan Rewind limits and always includes the latest revision",
+            "Archive knowledge with {} to stop future use while keeping the note and history",
             "Full request examples: CUSTOMER-INBOX.md",
         ],
         seeAlso: ["people", "usage"],

package/llms.txt

@@ -61,3 +61,5 @@ Complete Store edits: use existing items update --file with changed fields and v
 Template history (frontpage-host 0.3.11+): read `mail template get ID` before editing. `mail template history ID --limit 20 --cursor CURSOR` pages saved copies; `mail template history-get ID --history-id COPY_ID` fetches full content. Edit any copy, then `mail template set ID --file content.json` with the stable template ID and content fields only to make a new latest copy. Last template save wins; past copies remain. Campaign and series conflict checks remain. Retry uncertain saves through `mail save` with the same requestKey and exact payload. History begins with content retained at launch; earlier overwritten edits are unavailable. History reads use the plan’s Rewind window and always include Latest, even when older. Older copies stay stored; lists and direct reads apply the same limit. Window metadata explains the limit and whether older copies exist. See MAIL.md.
 
 Video uploads: the current CLI prepares a browser-compatible MP4 after uploading a local video, including prompt --attach. Use the returned sitePath and actual filename. prepared:false plus warning means the original was retained and playback compatibility is not assured. media list prefers an exact completed prepared copy. Existing video URLs are unchanged. See AGENTS.md for the upload and fallback contract.
+
+AI Support Agent knowledge: read the latest note, then save the same ID. Last save wins and prior saved changes remain in history. Knowledge history supports limit/cursor and version reads within the plan Rewind allowance plus the latest version. Archive with customer-inbox post knowledge/ID/archive and {} to stop future use without deleting records. See CUSTOMER-INBOX.md.

package/package.json

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