@notis_ai/cli 0.2.0-beta.1792662829286.1 → 0.2.0-beta.1792679782834.1

package/README.md

@@ -581,7 +581,7 @@ Examples:
 
 Publish a Space and its sub-Spaces as the next Store version.
 
-When to use: Share a Space as an installable template: team listings publish at once, public ones wait for review.
+When to use: Share a Space you own as an installable template: team listings publish at once, public ones wait for review. Notis runs the same safety scan and Owner check as the submission page and explains any refusal.
 
 Options:
 - `--channel <team|public>` — Where to publish.

package/dist/agent-hooks/notis-agent-hook.mjs

@@ -42999,7 +42999,7 @@ var spacesCommandSpecs = [
   {
     command_path: ["spaces", "store", "publish"],
     summary: "Publish a Space and its sub-Spaces as the next Store version.",
-    when_to_use: "Share a Space as an installable template: team listings publish at once, public ones wait for review.",
+    when_to_use: "Share a Space you own as an installable template: team listings publish at once, public ones wait for review. Notis runs the same safety scan and Owner check as the submission page and explains any refusal.",
     args_schema: { arguments: [idArgument], options: [
       { flags: "--channel <team|public>", description: "Where to publish." },
       { flags: "--metadata <json>", description: "Listing name, tagline, description, category, icon, accent." },

package/dist/base-skills/notis-spaces/.notis-base-skill.json

@@ -1 +1 @@
-{"schema":1,"stamp":1792661200,"commit":"ff2a9f14ff6a63cb7fdd2fb65572946d33f72d0b"}
+{"schema":1,"stamp":1792677351,"commit":"771883529c1d8ea5c48ead21c09b868da2362b87"}

package/dist/base-skills/notis-spaces/SKILL.md

@@ -4,7 +4,7 @@ description: Explain Notis Spaces, sharing, resource links and lifecycle; build
 feature_flag: spaces
 mcp_resource: true
 mcp_tool_patterns: ["LOCAL_NOTIS_MANAGE_SPACE", "LOCAL_NOTIS_FIND_VIEWS", "LOCAL_NOTIS_RENDER_VIEW"]
-mcp_references: ["references/release.md", "references/architecture.md", "references/design.md", "references/sdk.md", "references/views.md", "references/memory.md", "references/troubleshooting.md", "references/reading.md", "references/context.md", "references/reports.md"]
+mcp_references: ["references/release.md", "references/architecture.md", "references/design.md", "references/sdk.md", "references/views.md", "references/memory.md", "references/troubleshooting.md", "references/reading.md", "references/context.md", "references/reports.md", "references/store.md"]
 ---
 
 # Notis Spaces
@@ -84,6 +84,7 @@ If your last action created the Space, archive it through the lifecycle tool.
 | Data hooks, record pages and the toolkit pieces | [SDK](references/sdk.md) |
 | Explain resources, sharing and lifecycle | [Platform boundaries](references/architecture.md) |
 | Diagnose a failed check or release | [Troubleshooting](references/troubleshooting.md) |
+| Publish a Space or its update in the Store | [Store publishing](references/store.md) |
 
 Use ordinary native data tools when they answer the question. For what a page
 actually displays, resolve its current link and render the deployed view.
@@ -188,7 +189,8 @@ conflicts require a fresh pull and merge. Use the Skill writer for renaming.
 Sites are standalone, scoped view websites, not memberships. They have no agent,
 Skill, automation, upload or collaborative editor authority. Store installations
 are independent copies with three-way updates. Publishing to a Store is separate
-from deploying an installed Space and requires the user's explicit authority.
+from deploying an installed Space and requires the user's explicit authority;
+you prepare it and only the submission page's Publish button publishes.
 
 ## Reports, HTML and context
 

package/dist/base-skills/notis-spaces/references/design.md

@@ -19,6 +19,7 @@ Space's data, and change only what the Space needs (the four rungs in
 | One record as the page | `DocumentPage` (see [SDK](sdk.md#first-party-record-components)). Pick its `width` for the page: `standard` (the default) is a centred 900 px reading column for a page read as text, `wide` (1200 px) or `full` for a record that is a working surface such as a wide table or board |
 | A form or settings page | `Section kind="form"`, `Button`, `NativeSelect`, `SegmentedControl`, `Notice`, `EmptyState` |
 | A list on your own layout | `useListKeys`, `useSelection`, `Row`, `SelectionBar`, `Panels` |
+| Files or pictures attached to an item, or a picture to open full screen | `AttachmentGallery` (opens `ImageViewer` on its images); `ImageViewer` alone for one picture ([SDK](sdk.md#toolkit-pieces)) |
 
 Floating UI comes from `Menu`, `Popover` and `Tooltip`; they open inside the
 Space and pick up its theme. Open as Side, Center or Full belongs to the list

package/dist/base-skills/notis-spaces/references/release.md

@@ -81,7 +81,9 @@ a new revision. Source restoration does not revert user data or provider effects
 
 ## Publication privacy and portability gate
 
-Before an explicitly authorized Store publication:
+When the user asks Notis to publish, follow [Store publishing](store.md): you
+prepare a submission and the user publishes from its page. This gate applies to
+an explicitly authorized direct CLI publication:
 
 1. Review the complete snapshot: source, listing text and icon, schema, selected
    starter rows, linked Skills/helpers and automations. Exclude personal data, account

package/dist/base-skills/notis-spaces/references/sdk.md

@@ -114,6 +114,15 @@ rather than from a copy.
   sparkline `null` is a gap. `PeriodPicker` without the `custom` preset offers
   presets only.
 - **Floating**: `Menu`, `Popover`, `Tooltip`.
+- **Files and pictures**: `AttachmentGallery` and `ImageViewer`, the ones
+  Notis conversations use. `AttachmentGallery` draws a row of file cards
+  (`items`: `url`, `name`, `type` or `kind`, `size`, `thumbnailUrl`); an
+  image card opens `ImageViewer` on the gallery's images (zoom, pan, arrows,
+  copy, download, Escape), and any other card goes to `onOpen` (a new tab by
+  default). `renderOpener` swaps a card's opener, `itemAction` adds a corner
+  button, `viewerActions` adds viewer buttons (class `nui-viewer-btn`) and
+  `onNotice` hears copy and download results. Use `ImageViewer` alone for a
+  picture that opens full screen. Do not build your own lightbox.
 - **Blocks**: `Section`, `Badge`, `Button`, `ToggleGroup`, `SegmentedControl`,
   `NativeSelect`, `EmptyState`, `Notice`, `Metric`. A page is a stack of
   `Section`s, full width and without boxes: `kind` is `bar` (period and

package/dist/base-skills/notis-spaces/references/store.md

@@ -0,0 +1,111 @@
+# Store publishing
+
+Use this when the user asks to publish a Space, or an update to one, in the
+Store. You prepare everything; the user chooses where it goes and presses
+Publish on the submission page. Store publication stays separate from deploying
+the installed Space ([Delivery](release.md)).
+
+## Never publish for the user
+
+There is no agent publish operation, and you never press, simulate or script
+the Publish button. Only the page's Publish button publishes, after the user
+picks Team or Public there. Asking you to publish means: prepare the submission
+and send the page link. A team listing goes live as soon as the user presses
+Publish; a public listing goes to the sandbox reviewer, and Notis messages the
+user with its result.
+
+## The flow
+
+All steps use `LOCAL_NOTIS_MANAGE_SPACE`. Each answer is the submission view:
+status, listing text, locales, sample rows and counts, screenshots, findings,
+`can_publish`, `blocked_reason` and `link`.
+
+1. **Prepare.** Call `store_prepare {space_id, request_id}` with the root of the
+   tree to publish and a stable request ID. Notis copies the tree into the
+   user's hidden Store review Space (the test copy, automations paused), pins
+   the source revision, takes screenshots and runs the safety scan. Retry with
+   the same request ID; never prepare twice to recover a lost answer.
+2. **Write the listing** with `store_submission_update {submission_id, metadata,
+   locales}`: name, tagline, description, category, icon and accent in
+   `metadata` (English), and the French name, tagline and description in
+   `locales.fr`. Say what the Space does for the person who installs it, from
+   its views, databases and Skills. Write French as natural French (tu), not a
+   word-for-word translation. No personal names, account details, customer or
+   company data from the source.
+3. **Write sample rows** with `store_submission_update {submission_id,
+   sample_rows}` (see below), then read the screenshots. Pass
+   `retake_screenshots: true` after sample rows or listing text change what the
+   views show.
+4. **Handle the findings** (see below): ask about privacy, fix the rest in the
+   source Space, and list every fix.
+5. **Send the link.** When `can_publish` is true, give the user the page
+   `link`, one short line on what is ready, the fixes you made and their answers.
+   If it stays false, say what still blocks it from `blocked_reason` and what
+   they can do.
+
+## Sample rows
+
+- Up to 8 rows per database, keyed by database key: `{database_key:
+  [{key, properties, body}]}`. Use only properties in that database's schema; a
+  relation lists the `key` of another row in the same sample set. `body` is
+  optional plain text (one paragraph per line); `key` is optional short text.
+- Realistic and wholly synthetic: plausible titles, dates, amounts and states
+  that show every main view working (a few statuses, a spread of dates, at
+  least one row in each group a view shows).
+- Never a real person's name, email address, phone number, company, address or
+  account identifier, and never content copied or paraphrased from the user's
+  own rows, notes, contacts or history. Use invented first names only when a
+  field needs a person ("Alex", "Camille"), and no contact details at all.
+- Sample rows exist only in the test copy and the published version. They never
+  enter the source Space. Installs start with them, and the installer removes
+  all of them with one click; updates never bring them back.
+
+## Findings
+
+Each finding has `id`, `check`, `severity` (`red` or `amber`), `privacy`,
+`where`, `message`, `fix` and `status`. Publish needs no open red finding and no
+unanswered privacy question.
+
+**Privacy.** A finding with `privacy: true` is a candidate, not yet a question.
+Judge whether it carries a real privacy risk for the publisher or for people in
+their data: an outside host that would receive installers' data, an integration
+or MCP call that reads private accounts, a read of Spaces outside the published
+tree, a sharing change, personal data in the listing, screenshots or samples. A
+candidate with no real risk is treated like any other finding. For each real
+risk, ask the user one plain question naming what and where, with two choices:
+
+- **Remove**: take it out of what is published.
+- **Keep**: publish it as it is; Notis adds your note to the listing so
+  installers see it.
+
+Record their answer with `store_finding_answer {submission_id, finding_id,
+answer: 'remove'|'keep', note, user_words}`. `user_words` are the user's own
+words; `note` is the short listing sentence for a Keep, written in plain words.
+Never answer a privacy question for the user.
+
+**Everything else.** Fix each non-privacy red finding in the source Space
+through the normal release path: pull, change, build, verify, deploy, read back
+([Delivery](release.md)). Then call `store_prepare` again for the same Space
+with a new request ID, so the open submission pins the new revision and scans
+again. List every fix for the user: what was found, where, and what you changed.
+A finding you cannot fix keeps Publish blocked; say so plainly. Amber findings
+need no fix; mention the ones an installer would notice.
+
+Test chats about the submission run on the test copy only; never write sample
+rows, listing text or fixes for the listing into the source Space's data.
+
+## Updates
+
+Publishing an update follows the same flow: `store_prepare` on the same root
+creates a new submission on the same listing, and Publish adds a new version to
+it. Never create a second listing, a copy of the Space or a new Space to ship an
+update. Installs that differ only in listing text or screenshots update
+themselves; installs of a version that changes code or databases show an
+Update available card and update when their owner chooses.
+
+## Status
+
+Read the submission with `store_submission_read {submission_id}`. `ready` means
+the page can publish; `in_review` means the public review is running and Notis
+will message the user with the result; `published` is live; `rejected` lists what
+to fix, which starts again from step 4 with a new `store_prepare`.

package/dist/sdk/src/ui/icons.tsx

@@ -55,6 +55,14 @@ const SHAPES: Record<string, Shape> = {
   'check-circle-fill': <g><circle {...F} cx="8" cy="8" r="6.5" /><path d="M5 8.2l2 2 4-4" fill="none" stroke="hsl(var(--background))" strokeWidth={1.5} strokeLinecap="round" strokeLinejoin="round" /></g>,
   'minus-circle': <g {...S}><circle cx="8" cy="8" r="6" /><path d="M5.5 8h5" /></g>,
   'x-circle-fill': <g><circle {...F} cx="8" cy="8" r="6.5" /><path d="M5.8 5.8l4.4 4.4M10.2 5.8l-4.4 4.4" fill="none" stroke="hsl(var(--background))" strokeWidth={1.5} strokeLinecap="round" /></g>,
+  'magnifying-glass-plus': <path {...S} d="M7 12A5 5 0 107 2a5 5 0 000 10zM10.6 10.6L14 14M5 7h4M7 5v4" />,
+  'magnifying-glass-minus': <path {...S} d="M7 12A5 5 0 107 2a5 5 0 000 10zM10.6 10.6L14 14M5 7h4" />,
+  'download-simple': <path {...S} d="M8 2.5v7.5M4.5 6.5L8 10l3.5-3.5M2.5 10v3a.5.5 0 00.5.5h10a.5.5 0 00.5-.5v-3" />,
+  link: <path {...S} d="M6.8 9.2l2.4-2.4M7.6 4.6l1.2-1.2a2.8 2.8 0 014 4l-1.2 1.2M8.4 11.4l-1.2 1.2a2.8 2.8 0 01-4-4l1.2-1.2" />,
+  file: <path {...S} d="M9.5 2H4a.5.5 0 00-.5.5v11a.5.5 0 00.5.5h8a.5.5 0 00.5-.5V5zM9.5 2v3h3" />,
+  'file-image': <g {...S}><path d="M9.5 2H4a.5.5 0 00-.5.5v11a.5.5 0 00.5.5h8a.5.5 0 00.5-.5V5zM9.5 2v3h3" /><path d="M3.5 12l3-3 2 2 1.5-1.5 2.5 2.5" /><circle cx="6.5" cy="6.75" r=".75" /></g>,
+  'file-video': <g {...S}><path d="M9.5 2H4a.5.5 0 00-.5.5v11a.5.5 0 00.5.5h8a.5.5 0 00.5-.5V5zM9.5 2v3h3" /><path d="M6.5 8v3.5L9.5 9.75z" /></g>,
+  'file-audio': <g {...S}><path d="M9.5 2H4a.5.5 0 00-.5.5v11a.5.5 0 00.5.5h8a.5.5 0 00.5-.5V5zM9.5 2v3h3" /><path d="M6 9.5v1.5h1.25L9 12.25v-4.5L7.25 9H6M10.5 8.5a1.8 1.8 0 010 2.5" /></g>,
 };
 
 export function hasIcon(name: string): boolean {