gipity 1.0.396 → 1.0.397

package/dist/commands/sync.js

@@ -1,17 +1,18 @@
 import { Command } from 'commander';
 import { sync } from '../sync.js';
 import { createProgressReporter } from '../progress.js';
-import { error as clrError } from '../colors.js';
+import { error as clrError, muted } from '../colors.js';
 export const syncCommand = new Command('sync')
     .description('Sync files (a .gipityignore at the project root excludes paths, gitignore-style)')
     .option('--plan', 'Print the plan without applying any changes')
     .option('--force', 'Bypass the bulk-deletion guard')
+    .option('--prune', 'Remove files that exist on Gipity but not locally (applies the bulk deletes the guard defers)')
     .option('--json', 'Output as JSON')
     .action(async (opts) => {
     try {
         // JSON mode stays machine-clean; otherwise show live progress on a TTY.
         const progress = opts.json ? undefined : createProgressReporter();
-        const result = await sync({ plan: opts.plan, force: opts.force, progress });
+        const result = await sync({ plan: opts.plan, force: opts.force, prune: opts.prune, progress });
         if (opts.json) {
             console.log(JSON.stringify(result));
         }
@@ -20,8 +21,14 @@ export const syncCommand = new Command('sync')
             if (!opts.plan && result.applied > 0) {
                 console.log(`\n${result.applied} action${result.applied > 1 ? 's' : ''} applied.`);
             }
-            if (result.skipped > 0) {
-                console.error(clrError(`${result.skipped} action${result.skipped > 1 ? 's' : ''} skipped by guard.`));
+            // The guard defers bulk server-side deletes (files on Gipity but not
+            // local). Surface that here as a helpful hint - not a red error - with
+            // the one command that resolves it. Only `gipity sync` shows this;
+            // deploy/test/sandbox stay silent (their internal sync defers quietly).
+            if (result.deferredDeletes > 0) {
+                console.log(muted(`\n${result.deferredDeletes} file${result.deferredDeletes > 1 ? 's' : ''} on Gipity ` +
+                    `${result.deferredDeletes > 1 ? 'are' : 'is'} not present locally and ${result.deferredDeletes > 1 ? 'were' : 'was'} left untouched. ` +
+                    `Run 'gipity sync --prune' to remove ${result.deferredDeletes > 1 ? 'them' : 'it'}.`));
             }
             for (const e of result.errors)
                 console.error(clrError(e));

package/dist/knowledge.js

@@ -45,7 +45,7 @@ Gipity is the cloud platform your project runs on - hosting, databases, deployme
 
 Prefer the cheapest option that works - CLI and sandbox are instant and free, app services are runtime HTTP calls, \`gipity chat\` burns LLM tokens:
 
-1. CLI commands (fast, no agent overhead). The \`gipity\` CLI covers add, deploy, db, fn, logs, browser, sync, memory, skill, and more. All commands support \`--json\`.
+1. CLI commands (fast, no agent overhead). The \`gipity\` CLI covers add, deploy, db, fn, logs, browser, sync, memory, skill, email, and more. All commands support \`--json\`. You can send email yourself - \`gipity email send\` goes out as the agent from \`gipity@gipity.ai\` with no setup or API keys (\`gipity skill read email\`); don't build a \`mailto:\` workaround or reach for an SMTP library.
 2. Cloud sandbox via \`gipity sandbox run\` - Docker container with pre-installed tools for media (ffmpeg, ImageMagick, sox), documents (pandoc, LibreOffice), and data (pandas, matplotlib, sqlite3). Run \`gipity skill read sandbox-tools\` for the full toolkit. No network from inside the sandbox - fetch what you need before sending it in.
 3. App services - runtime HTTP endpoints your deployed app calls directly at \`https://a.gipity.ai/api/<PROJECT_GUID>/services/*\`. Available: LLM, TTS, image, sound, music, transcribe, video, file upload, realtime, location. Load the matching skill (\`app-llm\`, \`app-tts\`, etc.) before writing service code - they have the schemas, auth pattern, and common-mistake guards. For one-off generation during development, prefer \`gipity generate <image|video|speech|music>\` or \`gipity chat\`. \`gipity generate\` saves to a generic file in the current directory by default (e.g. \`./generated.png\`) - pass \`-o <path>\` to write it straight into your source tree so it deploys (e.g. \`gipity generate image "hero banner" -o src/assets/images/hero.png\`) instead of generating at cwd and moving it.
 4. Delegate to Gip (\`gipity chat "<task>"\`) - only when the work genuinely needs agent reasoning or a tool not in the CLI, sandbox, or app services. Required for: Twitter/X search, Gmail, calendar, push notifications, video understanding, audio source isolation, cross-model second opinions, multi-step orchestration. Don't use \`gipity chat\` for anything the sandbox can do - it's slower and burns tokens.
@@ -54,7 +54,7 @@ You are the developer. Write files in this directory - the Gipity Claude Code pl
 
 ## Use first-party services before reaching outside
 
-Gipity ships first-party services for what apps usually pull from third parties - auth, location/geocoding, LLM, image/audio/video generation, transcription, file uploads, realtime. Before calling an external API or adding an npm package for one of these, check \`gipity skill list\` for a match. First-party services need no API keys, cost less, and keep data in-house. Reach outside only when the catalog has no equivalent - and say so when you do.
+Gipity ships first-party services for what apps usually pull from third parties - auth, location/geocoding, LLM, image/audio/video generation, transcription, file uploads, realtime, and email (send as the agent via \`gipity email send\`, or from a deployed app via a workflow \`notify\` step - no SMTP/SendGrid/Nodemailer). Before calling an external API or adding an npm package for one of these, check \`gipity skill list\` for a match. First-party services need no API keys, cost less, and keep data in-house. Reach outside only when the catalog has no equivalent - and say so when you do.
 
 ## Don't guess Gipity facts - look them up
 
@@ -98,7 +98,7 @@ mkdir -p ~/GipityProjects/<slug> && cd ~/GipityProjects/<slug> && gipity init <s
 
 ## CLI quick reference
 
-Key commands: \`gipity add <template|kit>\`, \`gipity deploy dev\`, \`gipity sandbox run\`, \`gipity page inspect <url>\`, \`gipity page screenshot <url>\`, \`gipity db query "SQL"\`, \`gipity fn call <name>\`, \`gipity logs fn <name>\`, \`gipity skill read <name>\`.
+Key commands: \`gipity add <template|kit>\`, \`gipity deploy dev\`, \`gipity sandbox run\`, \`gipity page inspect <url>\`, \`gipity page screenshot <url>\`, \`gipity db query "SQL"\`, \`gipity fn call <name>\`, \`gipity logs fn <name>\`, \`gipity email send --to <addr> --subject <s> --body <b>\` (sends as \`gipity@gipity.ai\`; omit \`--to\` to self-send), \`gipity skill read <name>\`.
 Pull an existing remote project local (given its URL/slug): \`mkdir -p ~/GipityProjects/<slug> && cd ~/GipityProjects/<slug> && gipity init <slug>\` (adopts the matching project and syncs files down - this is the "clone").
 For deterministic text questions (letter/word counts, substring occurrences, nth word/char, anagrams), use \`gipity text analyze "<text>"\` - local and instant, no sandbox or LLM needed.
 Run \`gipity --help\` for the full list. Use \`--help\` on any command for details.
@@ -149,6 +149,7 @@ Kit skills (reusable building blocks - \`gipity add <kit>\`):
 - \`chatbot\` - the chatbot kit: persona + scope guardrails + static knowledge, bubble widget or headless engine
 
 Other key skills:
+- \`email\` - sending email as the agent from gipity@gipity.ai (no setup/keys) — plus Gmail-thread replies, HTML formatting, images
 - \`sandbox-tools\` - cloud sandbox capabilities and pre-installed tools
 - \`tts\` - agent-side speech tools (different from the \`app-tts\` HTTP service)`;
 export const DEFINITION_OF_DONE = `## Definition of done (build tasks)

package/dist/sync.js

@@ -481,16 +481,20 @@ async function bulkDeleteGuard(p, knownFiles, opts) {
     const totalDeletes = p.deletesLocal + p.deletesRemote;
     if (totalDeletes === 0)
         return true;
-    if (opts.force)
+    if (opts.force || opts.prune)
         return true;
     const denom = Math.max(knownFiles, 1);
     const fraction = totalDeletes / denom;
     if (totalDeletes < BULK_DELETE_COUNT || fraction < BULK_DELETE_FRACTION)
         return true;
     if (!opts.interactive || getAutoConfirm()) {
-        console.error(`Refusing to delete ${totalDeletes} file${totalDeletes > 1 ? 's' : ''} ` +
-            `(${Math.round(fraction * 100)}% of tree) non-interactively. ` +
-            `Re-run with --force or interactively to confirm.`);
+        // Non-interactive (deploy/test/sandbox auto-mirror): there's no human to
+        // confirm, so defer the bulk deletes SILENTLY and carry them forward. This
+        // is the safe default - uploads/downloads still apply, nothing is deleted -
+        // and it avoids spamming a "Refusing to delete N files" error on every
+        // command when a project legitimately has server-only files (e.g. runtime
+        // uploads, or sandbox outputs not kept locally). The deferred count rides
+        // out in SyncResult.deferredDeletes; `gipity sync --prune` applies them.
         return false;
     }
     const answer = await prompt(`\nPlan deletes ${totalDeletes} files (${Math.round(fraction * 100)}% of the tree). Type "delete" to confirm: `);
@@ -572,6 +576,7 @@ async function syncInner(projectGuid, root, ignore, opts, interactive) {
         return {
             plan: planned, applied: 0, skipped: 0, errors: [],
             summary: formatPlan(planned),
+            deferredDeletes: 0,
         };
     }
     // Bulk-delete guard over the *planned* deletes.
@@ -983,6 +988,7 @@ async function syncInner(projectGuid, root, ignore, opts, interactive) {
         skipped: skippedByGuard,
         errors,
         summary: formatPlan(planned),
+        deferredDeletes: skippedByGuard,
     };
 }
 function cleanupEmptyDirs(root, ignorePatterns) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gipity",
-  "version": "1.0.396",
+  "version": "1.0.397",
   "description": "The full-stack platform tuned for AI agents. Database, storage, auth, functions, deploy, and drop-in kits - all agent-tuned. Pair with Claude Code or use standalone.",
   "bin": {
     "gipity": "dist/updater/shim.js",