@elaraai/e3-cloud-claude-plugin 1.1.1 → 1.1.3

package/.build/hooks/pre-read.js

@@ -1,4 +1,4 @@
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/host.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/host.js
 import { existsSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 var isCodex = existsSync(fileURLToPath(new URL("../../.codex-plugin/plugin.json", import.meta.url)));
@@ -6,7 +6,7 @@ function hostText(text) {
   return isCodex ? text.replaceAll("mcp__plugin_east_east__", "").replaceAll("/east:", "$east-codex-plugin:").replaceAll("Claude Code", "Codex") : text;
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/hook-io.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/hook-io.js
 async function readHookInput() {
   let input = "";
   for await (const chunk of process.stdin) {
@@ -34,10 +34,10 @@ function writeHookDecision(hookEventName, decision, reason) {
   process.stdout.write(JSON.stringify(output));
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
 var SEARCH_TOOLS = ["mcp__plugin_east_east__search_east_examples", "mcp__plugin_east_east__get_east_example", "mcp__east__search_east_examples", "mcp__east__get_east_example"];
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
 var EAST_GUIDANCE = {
   searchTool: "mcp__plugin_east_east__search_east_examples",
   getTool: "mcp__plugin_east_east__get_east_example",
@@ -79,7 +79,7 @@ var GATE_TEXT = gateText(EAST_GUIDANCE);
 var READ_TEXT = readText(EAST_GUIDANCE);
 var isExampleCorpusRead = corpusReadFor(EAST_GUIDANCE.scope);
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
 function preReadReminder(event, options) {
   return options.isCorpusRead(event.tool_name ?? "", event.tool_input ?? {}) ? { decision: "context", text: options.readText } : null;
 }

package/.build/hooks/pre-write.js

@@ -1,10 +1,10 @@
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
 import { readFile as readFile2 } from "node:fs/promises";
 import { existsSync as existsSync2, writeFileSync } from "node:fs";
 import { tmpdir } from "node:os";
 import { join } from "node:path";
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/host.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/host.js
 import { existsSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 var isCodex = existsSync(fileURLToPath(new URL("../../.codex-plugin/plugin.json", import.meta.url)));
@@ -12,7 +12,7 @@ function hostText(text) {
   return isCodex ? text.replaceAll("mcp__plugin_east_east__", "").replaceAll("/east:", "$east-codex-plugin:").replaceAll("Claude Code", "Codex") : text;
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/hook-io.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/hook-io.js
 async function readHookInput() {
   let input = "";
   for await (const chunk of process.stdin) {
@@ -40,7 +40,7 @@ function writeHookDecision(hookEventName, decision, reason) {
   process.stdout.write(JSON.stringify(output));
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
 import { readFile } from "node:fs/promises";
 var SEARCH_TOOLS = ["mcp__plugin_east_east__search_east_examples", "mcp__plugin_east_east__get_east_example", "mcp__east__search_east_examples", "mcp__east__get_east_example"];
 async function searchedInTranscript(transcriptPath, tools = SEARCH_TOOLS) {
@@ -53,7 +53,7 @@ async function searchedInTranscript(transcriptPath, tools = SEARCH_TOOLS) {
   return tools.some((tool) => raw.includes(`"name":"${tool}"`) || raw.includes(`"name": "${tool}"`));
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
 var EAST_GUIDANCE = {
   searchTool: "mcp__plugin_east_east__search_east_examples",
   getTool: "mcp__plugin_east_east__get_east_example",
@@ -95,7 +95,7 @@ var GATE_TEXT = gateText(EAST_GUIDANCE);
 var READ_TEXT = readText(EAST_GUIDANCE);
 var isExampleCorpusRead = corpusReadFor(EAST_GUIDANCE.scope);
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-hooks.js
 async function preWriteGate(event, options) {
   const cwd = event.cwd || process.cwd();
   const filePath = event.tool_input?.file_path;

package/.build/mcp/server.js

@@ -21556,7 +21556,7 @@ var StdioServerTransport = class {
   }
 };
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search.js
 import { readFile } from "node:fs/promises";
 
 // ../../node_modules/.pnpm/minisearch@7.2.0/node_modules/minisearch/dist/es/index.js
@@ -23369,7 +23369,7 @@ var objectToNumericMapAsync = async (object3) => {
 var wait = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
 var SPACE_OR_PUNCTUATION = /[\n\r\p{Z}\p{P}]+/u;
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search-guidance.js
 var EAST_GUIDANCE = {
   searchTool: "mcp__plugin_east_east__search_east_examples",
   getTool: "mcp__plugin_east_east__get_east_example",
@@ -23411,7 +23411,7 @@ var GATE_TEXT = gateText(EAST_GUIDANCE);
 var READ_TEXT = readText(EAST_GUIDANCE);
 var isExampleCorpusRead = corpusReadFor(EAST_GUIDANCE.scope);
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/search.js
 var MIN_SCORE = 5;
 async function loadIndexes(indexPaths) {
   const entries = [];
@@ -23537,7 +23537,7 @@ function getEntry(index, id) {
   return stored === void 0 ? null : stored;
 }
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/mcp/example-tools.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/mcp/example-tools.js
 var EAST_PACKAGES = ["east", "east-node-std", "east-node-io", "east-py-datascience", "east-ui", "e3-ui", "e3", "e3-ui-cli", "e3-create"];
 function isLoaded(index) {
   return typeof index.then === "function";
@@ -23610,7 +23610,7 @@ function registerExampleTools(server2, options) {
 import { fileURLToPath } from "node:url";
 var E3_CLOUD_INDEX_PATH = fileURLToPath(new URL("../../index.json", import.meta.url));
 
-// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.101_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
+// ../../node_modules/.pnpm/@elaraai+east-plugin@1.0.102_typescript@5.9.3/node_modules/@elaraai/east-plugin/dist/lib/transcript.js
 var SEARCH_TOOLS = ["mcp__plugin_east_east__search_east_examples", "mcp__plugin_east_east__get_east_example", "mcp__east__search_east_examples", "mcp__east__get_east_example"];
 
 // ../e3-cloud-plugin/dist/lib/names.js

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "e3-cloud",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "e3 cloud - apps for hosted e3 workspaces with @elaraai/e3-cloud-ui, files from buckets as inputs with @elaraai/e3-cloud-files, the e3-cloud CLI and @elaraai/e3-cloud-client: skills, example search and the search-first hooks",
   "author": {
     "name": "Elara AI",

package/index.json

@@ -591,7 +591,7 @@
       "package": "e3-cloud-files",
       "file": "static",
       "suite": "Files",
-      "test": "Declaring which inputs a bucket's files fill: a source, one file, the newest of a folder, every file of a folder and a folder's listing, each an ordinary e3.input a task takes, and the declarations e3-cloud files deploy deploys",
+      "test": "Declaring which inputs a source's files fill (a deployed workspace's own storage unless bound elsewhere): a source, one file, the newest of a folder, every file of a folder and a folder's listing, each an ordinary e3.input a task takes, and the declarations e3-cloud files deploy deploys",
       "keywords": [
         "Files",
         "Files.source",
@@ -606,6 +606,7 @@
         "key",
         "s3",
         "bucket",
+        "own storage",
         "input",
         "Blob",
         "e3-cloud-files"
@@ -615,7 +616,7 @@
         "import e3, { type Runner } from '@elaraai/e3';",
         "import { Files, FilesFolderType } from '@elaraai/e3-cloud-files';"
       ],
-      "source": "// src/files.ts: which inputs a source's files fill. Each workspace binds the source to s3://bucket/prefix/;\n// keys and prefixes here are relative to it, so the code never names a bucket\nexport const upload = Files.source('upload');\nexport const rates = upload.file('rates', { key: 'rates.json' });                          // Blob\nexport const stock = upload.latest('stock', { prefix: 'stock/', include: '*.json' });     // Blob: the greatest key, so name files by date\nexport const orders = upload.folder('orders', { prefix: 'orders/', include: '*.json' });  // Dict<String, Blob>, by path under the prefix\nexport const orderFiles = upload.listing('order_files', { prefix: 'orders/' });           // each file's size, modified and etag, no bytes\n// '*.json' is the prefix's own files; '**/*.json' takes its subfolders' too\nexport default Files.manifest([upload]);\n\n// src/package.ts: each is an ordinary input, unassigned until a sync sets it; a task decodes what arrives\nconst runner: Runner = { runtime: 'east-c', platforms: ['east-c-std'] };\nconst Rate = StructType({ currency: StringType, rate: FloatType });\nconst Order = StructType({ id: StringType, sku: StringType, amount: FloatType });\nexport const rateTable = e3.task('rate_table', [rates],\n  East.function([BlobType], ArrayType(Rate), (_$, file) => file.decodeUtf8().parseJson(ArrayType(Rate))), { runner });\nexport const allOrders = e3.task('all_orders', [orders],\n  East.function([FilesFolderType], ArrayType(Order), (_$, files) =>\n    files.flattenToArray((_$, file) => file.decodeUtf8().parseJson(ArrayType(Order)))), { runner });\nexport default e3.package('orders', '1.0.0', rateTable, allOrders);",
+      "source": "// src/files.ts: which inputs a source's files fill. A deployed workspace keeps them in its own storage, upload/, unless it binds\n// the source elsewhere; keys and prefixes here are relative to where they are, so the code never names a bucket\nexport const upload = Files.source('upload');\nexport const rates = upload.file('rates', { key: 'rates.json' });                          // Blob\nexport const stock = upload.latest('stock', { prefix: 'stock/', include: '*.json' });     // Blob: the greatest key, so name files by date\nexport const orders = upload.folder('orders', { prefix: 'orders/', include: '*.json' });  // Dict<String, Blob>, by path under the prefix\nexport const orderFiles = upload.listing('order_files', { prefix: 'orders/' });           // each file's size, modified and etag, no bytes\n// '*.json' is the prefix's own files; '**/*.json' takes its subfolders' too\nexport default Files.manifest([upload]);\n\n// src/package.ts: each is an ordinary input, unassigned until a sync sets it; a task decodes what arrives\nconst runner: Runner = { runtime: 'east-c', platforms: ['east-c-std'] };\nconst Rate = StructType({ currency: StringType, rate: FloatType });\nconst Order = StructType({ id: StringType, sku: StringType, amount: FloatType });\nexport const rateTable = e3.task('rate_table', [rates],\n  East.function([BlobType], ArrayType(Rate), (_$, file) => file.decodeUtf8().parseJson(ArrayType(Rate))), { runner });\nexport const allOrders = e3.task('all_orders', [orders],\n  East.function([FilesFolderType], ArrayType(Order), (_$, files) =>\n    files.flattenToArray((_$, file) => file.decodeUtf8().parseJson(ArrayType(Order)))), { runner });\nexport default e3.package('orders', '1.0.0', rateTable, allOrders);",
       "languages": [
         "typescript"
       ]
@@ -1076,13 +1077,17 @@
       "package": "e3-cloud-cli",
       "file": "static",
       "suite": "e3-cloud files",
-      "test": "Bringing a bucket's files into a workspace: deploy the declarations, bind each source to s3://bucket/prefix/, sync what changed, then run the dataflow; locally with your own cloud profile, the bytes only in the local repository",
+      "test": "Bringing files into a workspace: deploy the declarations; a deployed workspace's sources read its own storage, so push the files there with nothing to bind, or bind a source elsewhere (a path relative to the workspace such as ../production/upload/, or a bucket of your own); a local repository binds each source to s3://bucket/prefix/ and syncs with your own cloud profile, the bytes only in the local repository; then run the dataflow",
       "keywords": [
         "files",
         "deploy",
         "bind",
         "sync",
+        "push",
         "status",
+        "own storage",
+        "path",
+        "../production/upload/",
         "s3",
         "bucket",
         "--profile",
@@ -1094,7 +1099,7 @@
         "--reset"
       ],
       "imports": [],
-      "source": "e3 workspace deploy ./repo dev --from-source src/package.ts\ne3-cloud files deploy ./repo dev src/files.ts --dry-run          # checked against the package dev runs; changes nothing\ne3-cloud files deploy ./repo dev src/files.ts\ne3-cloud files bind ./repo dev upload s3://partner-drop/orders/ --profile partner --latest 30   # locally: your own profile, each folder's 30 newest\ne3-cloud files sync ./repo dev --dry-run                         # what a sync would take\ne3-cloud files sync ./repo dev                                   # reads only files whose ETag or size changed\ne3-cloud files status ./repo dev                                 # each mapping, its type, what it holds (pending for an unseeded record), bindings, the last sync\ne3 dataflow run ./repo dev                                       # a sync doesn't run the dataflow\n# <repo> may be a repository URL instead (https://e3.example.com/repos/acme): the same commands, run by the platform",
+      "source": "# A deployed workspace: its sources read its own storage (upload/), so the declarations and a push are all it takes\ne3 workspace deploy https://e3.example.com/repos/acme dev --from-source src/package.ts\ne3-cloud files deploy https://e3.example.com/repos/acme dev src/files.ts --dry-run   # checked against the package dev runs; changes nothing\ne3-cloud files deploy https://e3.example.com/repos/acme dev src/files.ts             # upload reads own storage upload/: put its files there with files push\ne3-cloud files push https://e3.example.com/repos/acme dev ./data/rates.json          # put with your e3 login alone, then synced\ne3-cloud files status https://e3.example.com/repos/acme dev                          # each mapping, its type, what it holds (pending for an unseeded record), where each source's files are, the last sync\n# A source bound elsewhere: a path relative to the workspace, or a bucket of your own the deployment grants (no location: its own folder again)\ne3-cloud files bind https://e3.example.com/repos/acme staging upload ../production/upload/   # a staging reading production's files (a push through it puts there too)\ne3-cloud files bind https://e3.example.com/repos/acme dev partner s3://partner-drop/acme/\n# A local repository has no storage of its own: bind each source to a bucket, read with your own profile\ne3 workspace deploy ./repo dev --from-source src/package.ts\ne3-cloud files deploy ./repo dev src/files.ts\ne3-cloud files bind ./repo dev upload s3://partner-drop/orders/ --profile partner --latest 30   # locally: your own profile, each folder's 30 newest\ne3-cloud files sync ./repo dev --dry-run                         # what a sync would take\ne3-cloud files sync ./repo dev                                   # reads only files whose ETag or size changed\ne3 dataflow run ./repo dev                                       # a sync doesn't run the dataflow",
       "languages": [
         "typescript"
       ]
@@ -1105,7 +1110,7 @@
       "package": "e3-cloud-cli",
       "file": "static",
       "suite": "e3-cloud files",
-      "test": "Pushing files from disk into a source and taking them in: each file matched to the mapping that takes it (by its name, or --as), checked against its type and limit, put with your e3 login alone where the source is the deployment's own bucket, then synced; unchanged once it is there; --dry-run plans and puts nothing",
+      "test": "Pushing files from disk into a source and taking them in: each file matched to the mapping that takes it (by its name, or --as), checked against its type and limit, put with your e3 login alone where the source is the workspace's own storage (as a source bound to nothing is), then synced; unchanged once it is there; --dry-run plans and puts nothing",
       "keywords": [
         "files",
         "push",
@@ -1119,11 +1124,12 @@
         "beast2",
         "typed",
         "unchanged",
+        "own storage",
         "dataset",
         "e3-cloud"
       ],
       "imports": [],
-      "source": "# A file by its name (a file mapping's key, or the newest under a latest prefix), a directory to a folder mapping; a row per file\ne3-cloud files push https://e3.example.com/repos/acme dev ./data/prices.beast2 ./data/deltas/2026-10-19.beast2\n#   prices.beast2      → prices                            Array<Struct{sku, price}>  38 MiB  put  taken in  412,310 rows\n#   2026-10-19.beast2  → mutation:price_book.load_prices  load_prices                 1 MiB  put  committed 9f2c1a0b7e3d\n# Next: e3 dataflow run https://e3.example.com/repos/acme dev\ne3-cloud files push ./repo dev ./data/orders/ --as orders         # a directory's files into the orders folder, each at its path\ne3-cloud files push ./repo dev ./data/prices.beast2 --dry-run     # the plan alone: put, unchanged or refused, and why\ne3-cloud files push ./repo dev ./data/x.beast2 --profile partner  # a bucket the platform does not write: your own credentials\ne3-cloud files sync ./repo dev --target prices --target mutation:price_book.load_prices   # only these targets\ne3-cloud files sync ./repo dev --reset price_book                 # a seeded record's file taken as its state again, mutations since or not",
+      "source": "# A file by its name (a file mapping's key, or the newest under a latest prefix), a directory to a folder mapping; a row per file\ne3-cloud files push https://e3.example.com/repos/acme dev ./data/prices.beast2 ./data/deltas/2026-10-19.beast2\n# upload  own storage upload/\n#   prices.beast2      → prices                            Array<Struct{sku, price}>  38 MiB  put  taken in  412,310 rows\n#   2026-10-19.beast2  → mutation:price_book.load_prices  load_prices                 1 MiB  put  committed 9f2c1a0b7e3d\n# Next: e3 dataflow run https://e3.example.com/repos/acme dev\ne3-cloud files push ./repo dev ./data/orders/ --as orders         # a directory's files into the orders folder, each at its path\ne3-cloud files push ./repo dev ./data/prices.beast2 --dry-run     # the plan alone: put, unchanged or refused, and why\ne3-cloud files push ./repo dev ./data/x.beast2 --profile partner  # a bucket the platform does not write: your own credentials\ne3-cloud files sync ./repo dev --target prices --target mutation:price_book.load_prices   # only these targets\ne3-cloud files sync ./repo dev --reset price_book                 # a seeded record's file taken as its state again, mutations since or not",
       "languages": [
         "typescript"
       ]
@@ -1308,7 +1314,7 @@
       "file": "static",
       "id": "e3-cloud-client:static:files",
       "suite": "@elaraai/e3-cloud-client files",
-      "test": "Files from code: deploy a workspace's declarations, bind a source, sync named targets (a seeded record reset) and wait for the sync's report, read what each mapping holds, and push a file from disk (plan, upload through the platform, sync), or a workspace's dataset as the file of its value",
+      "test": "Files from code: deploy a workspace's declarations (its sources reading its own storage, so a push needs no bind), bind a source elsewhere (a path relative to the workspace, or a bucket of your own), sync named targets (a seeded record reset) and wait for the sync's report, read what each mapping holds, and push a file from disk (plan, upload through the platform, sync), or a workspace's dataset as the file of its value",
       "keywords": [
         "getFiles",
         "deployFiles",
@@ -1331,6 +1337,7 @@
         "unchanged",
         "refused",
         "retaken",
+        "own storage",
         "workspace_protected"
       ],
       "imports": [
@@ -1341,7 +1348,7 @@
         "import { filesPushRefusalText, filesTargetText } from '@elaraai/e3-cloud-types';",
         "import manifest from './files.js';   // export default Files.manifest([upload])"
       ],
-      "source": "// The declarations (checked against the package the workspace runs), then where the source's files are\nconst deployed = await deployFiles(url, 'acme', 'staging', manifest, options);\nif (deployed.type === 'refused') throw new Error(deployed.value.problems.map((p) => p.type).join(', '));\nawait bindFilesSource(url, 'acme', 'staging', { source: 'upload', url: 's3://partner-drop/acme/', region: none, profile: none, latest: none }, options);\n\n// A sync of two targets: the seeded record's file taken as its state again (reset), and the fed mutation's new files\nconst start = await startFilesSync(url, 'acme', 'staging', {\n  targets: [variant('record', 'customers'), variant('mutation', { record: 'price_book', mutation: 'load_prices' })],\n  reset: ['customers'],\n}, options);\nconst id = start.value;   // started, or running: the sync under way, waited on the same way\nconst job = await filesSyncWait(url, 'acme', 'staging', id, options, { deadlineMs: 10 * 60_000 });\nfor (const m of job.report.type === 'some' ? job.report.value.mappings : []) {\n  console.log(filesTargetText(m.target), m.updated ? `written (commit ${m.commit.type === 'some' ? m.commit.value.slice(0, 12) : 'none'})` : 'as it was', m.refused.length === 0 ? '' : `refused ${m.refused[0]!.key}`);\n}\n\n// What each mapping holds now; a record not yet seeded is pending\nconst files = await getFiles(url, 'acme', 'staging', options);\nconsole.log(files.status.mappings.map((m) => `${filesTargetText(m.target)}: ${m.pending ? 'pending' : m.holds.type === 'some' ? m.holds.value.key : 'nothing yet'}`).join(' · '));\n\n// A push from disk: the plan says per file where it goes and how to upload it; uploadFilesPush puts it through the platform\n// (one PUT bound to its SHA-256, or a multipart upload it completes), then one sync of the targets put\nconst path = 'data/customers.beast2';\nconst size = (await stat(path)).size;\nconst plan = await planFilesPush(url, 'acme', 'staging', {\n  files: [{ name: 'customers.beast2', directory: none, size: BigInt(size), sha256, type: some(customerBookType), dataset: none }],   // sha256: hex; type: its beast2 header's\n  as: none,\n}, options);\nconst bytes: FilesPushBytes = { size, ranged: true, read: (start) => createReadStream(path, { start }) };   // a file reads from any offset\nfor (const f of plan.files) {\n  if (f.outcome.type === 'refused') console.warn(f.name, filesPushRefusalText(f.outcome.value));\n  else if (f.outcome.type === 'put') await uploadFilesPush(url, 'acme', 'staging', plan, f.outcome.value, bytes, options);   // an `external` put throws: your own credentials\n}\nawait startFilesSync(url, 'acme', 'staging', { targets: plan.files.flatMap((f) => (f.outcome.type === 'put' ? [f.outcome.value.target] : [])) }, options);\n// A workspace's dataset is offered as the file of its value: dataset: some({ workspace: 'dev', name: 'customers', hash }), its type the value's,\n// its bytes the value's beast2 as `e3 dataset get -f beast2` writes it, streamed (ranged: false: never held whole) and matched by its name.\n// `e3-cloud files push … dataset:dev.customers --from <repo>` does all of it",
+      "source": "// The declarations (checked against the package the workspace runs). A source bound to nothing reads the workspace's own storage,\n// <source>/ (upload/ here), so a push needs no bind; no answer names the bucket that holds it\nconst deployed = await deployFiles(url, 'acme', 'staging', manifest, options);\nif (deployed.type === 'refused') throw new Error(deployed.value.problems.map((p) => p.type).join(', '));\n// A source bound elsewhere: a path relative to the workspace ('../production/upload/': production's folder, which a push through it\n// puts into too), or a bucket of your own the deployment grants; `retaken` names the targets the next sync takes again whole\nconst bound = await bindFilesSource(url, 'acme', 'staging', { source: 'partner', url: 's3://partner-drop/acme/', region: none, profile: none, latest: none }, options);\nif (bound.type === 'refused') console.warn(bound.value.map((p) => p.type).join(', '));\n\n// A sync of two targets: the seeded record's file taken as its state again (reset), and the fed mutation's new files\nconst start = await startFilesSync(url, 'acme', 'staging', {\n  targets: [variant('record', 'customers'), variant('mutation', { record: 'price_book', mutation: 'load_prices' })],\n  reset: ['customers'],\n}, options);\nconst id = start.value;   // started, or running: the sync under way, waited on the same way\nconst job = await filesSyncWait(url, 'acme', 'staging', id, options, { deadlineMs: 10 * 60_000 });\nfor (const m of job.report.type === 'some' ? job.report.value.mappings : []) {\n  console.log(filesTargetText(m.target), m.updated ? `written (commit ${m.commit.type === 'some' ? m.commit.value.slice(0, 12) : 'none'})` : 'as it was', m.refused.length === 0 ? '' : `refused ${m.refused[0]!.key}`);\n}\n\n// What each mapping holds now; a record not yet seeded is pending\nconst files = await getFiles(url, 'acme', 'staging', options);\nconsole.log(files.status.mappings.map((m) => `${filesTargetText(m.target)}: ${m.pending ? 'pending' : m.holds.type === 'some' ? m.holds.value.key : 'nothing yet'}`).join(' · '));\n\n// A push from disk: the plan says per file where it goes and how to upload it; uploadFilesPush puts it through the platform\n// (one PUT bound to its SHA-256, or a multipart upload it completes), then one sync of the targets put\nconst path = 'data/customers.beast2';\nconst size = (await stat(path)).size;\nconst plan = await planFilesPush(url, 'acme', 'staging', {\n  files: [{ name: 'customers.beast2', directory: none, size: BigInt(size), sha256, type: some(customerBookType), dataset: none }],   // sha256: hex; type: its beast2 header's\n  as: none,\n}, options);\nconst bytes: FilesPushBytes = { size, ranged: true, read: (start) => createReadStream(path, { start }) };   // a file reads from any offset\nfor (const f of plan.files) {\n  if (f.outcome.type === 'refused') console.warn(f.name, filesPushRefusalText(f.outcome.value));\n  else if (f.outcome.type === 'put') await uploadFilesPush(url, 'acme', 'staging', plan, f.outcome.value, bytes, options);   // an `external` put throws: your own credentials\n}\nawait startFilesSync(url, 'acme', 'staging', { targets: plan.files.flatMap((f) => (f.outcome.type === 'put' ? [f.outcome.value.target] : [])) }, options);\n// A workspace's dataset is offered as the file of its value: dataset: some({ workspace: 'dev', name: 'customers', hash }), its type the value's,\n// its bytes the value's beast2 as `e3 dataset get -f beast2` writes it, streamed (ranged: false: never held whole) and matched by its name.\n// `e3-cloud files push … dataset:dev.customers --from <repo>` does all of it",
       "languages": [
         "typescript"
       ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elaraai/e3-cloud-claude-plugin",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "e3 cloud - apps for hosted e3 workspaces with @elaraai/e3-cloud-ui, files from buckets as inputs with @elaraai/e3-cloud-files, the e3-cloud CLI and @elaraai/e3-cloud-client: skills, example search and the search-first hooks",
   "license": "AGPL-3.0-or-later",
   "type": "module",

package/skills/e3-cloud-cli/SKILL.md

@@ -1,13 +1,14 @@
 ---
 name: e3-cloud-cli
-description: "The e3-cloud CLI — run an e3 cloud deployment from the shell. Use when: (1) Signing in (`e3 auth login` to a server, whose credentials e3-cloud shares), checking who you are and which e3 cloud release and e3 the deployment runs (`e3-cloud whoami SERVER`), and which this CLI is built with (`e3-cloud --version`, `--json`), (2) Building and deploying apps — `e3-cloud app build`, `app deploy` (UI-only, or with its package, `--dry-run`, several together, `--from-source`), `app list`, `app versions`, `app remove` (an app is developed in the cloud: deployed to a workspace of one's own and opened there), (3) Staging an app for the platform's next e3 (`app deploy --for-platform VERSION`, `app list-all`), (4) Staging and releases — `e3-cloud staging add|stop|list` (a staging protects the workspace it releases to: it then changes only by a release from it, or a rollback; `--force` on `app deploy` and `app remove` is an admin's override), `e3 workspace copy` for the rehearsal, `e3-cloud release URL FROM TO` with `--plan`, `--carry` and `--remove-apps` (a release carries the package, the apps and the Files declarations; the target keeps its data and bindings), `e3-cloud history`, `e3-cloud rollback`, (5) A repository's people and business roles — `e3-cloud user list|add|remove` (`--role owner`, or a user with `--roles 'Rostering,Finance'`), `e3-cloud role list|show|set|rm` (`--grant WORKSPACE/APP[:page,page]`), and for admins `user list-all|disable|enable|invitations|uninvite`, (6) Secrets (`e3-cloud secrets set|list|rm`), schedules (`schedule set|get|list|remove`), each task's compute size and timeout (`compute`, `timeout`), people's workspace settings (`settings`), (7) Records' history, rollback and backups (`e3-cloud records …`) and feedback (`e3-cloud feedback …`), (8) Files — a solution's inputs from files in a bucket: `e3-cloud files deploy|bind|sync|push|status`, given a local repository's path or a repository URL, and `files push` of files from disk or of a workspace's dataset as the file of its value (`dataset:WORKSPACE.NAME`, `--from` a local repository or a URL) (the e3-cloud-files skill declares and decodes them), (9) Walking a solution through its life, step by step — starting it, adding a staging, developing an app's pages, changing the package's tasks and inputs, migrating a record, Files, rehearsing and releasing, rolling back, an emergency change to production, people and roles, schedules, secrets and compute, feedback, the platform's next e3, and retiring an app or a workspace."
+description: "The e3-cloud CLI — run an e3 cloud deployment from the shell. Use when: (1) Signing in (`e3 auth login` to a server, whose credentials e3-cloud shares), checking who you are and which e3 cloud release and e3 the deployment runs (`e3-cloud whoami SERVER`), and which this CLI is built with (`e3-cloud --version`, `--json`), (2) Building and deploying apps — `e3-cloud app build`, `app deploy` (UI-only, or with its package, `--dry-run`, several together, `--from-source`), `app list`, `app versions`, `app remove` (an app is developed in the cloud: deployed to a workspace of one's own and opened there), (3) Staging an app for the platform's next e3 (`app deploy --for-platform VERSION`, `app list-all`), (4) Staging and releases — `e3-cloud staging add|stop|list` (a staging protects the workspace it releases to: it then changes only by a release from it, or a rollback; `--force` on `app deploy` and `app remove` is an admin's override), `e3 workspace copy` for the rehearsal, `e3-cloud release URL FROM TO` with `--plan`, `--carry` and `--remove-apps` (a release carries the package, the apps and the Files declarations; the target keeps its data and bindings), `e3-cloud history`, `e3-cloud rollback`, (5) A repository's people and business roles — `e3-cloud user list|add|remove` (`--role owner`, or a user with `--roles 'Rostering,Finance'`), `e3-cloud role list|show|set|rm` (`--grant WORKSPACE/APP[:page,page]`), and for admins `user list-all|disable|enable|invitations|uninvite`, (6) Secrets (`e3-cloud secrets set|list|rm`), schedules (`schedule set|get|list|remove`), each task's compute size and timeout (`compute`, `timeout`), people's workspace settings (`settings`), (7) Records' history, rollback and backups (`e3-cloud records …`) and feedback (`e3-cloud feedback …`), (8) Files — a solution's inputs from files, kept in a deployed workspace's own storage (nothing to bind, no bucket named) or a bucket of your own: `e3-cloud files deploy|bind|sync|push|status`, given a local repository's path or a repository URL, and `files push` of files from disk or of a workspace's dataset as the file of its value (`dataset:WORKSPACE.NAME`, `--from` a local repository or a URL) (the e3-cloud-files skill declares and decodes them), (9) Walking a solution through its life, step by step — starting it, adding a staging, developing an app's pages, changing the package's tasks and inputs, migrating a record, Files, rehearsing and releasing, rolling back, an emergency change to production, people and roles, schedules, secrets and compute, feedback, the platform's next e3, and retiring an app or a workspace."
 ---
 
 # e3-cloud — the e3 cloud CLI (@elaraai/e3-cloud-cli)
 
 `e3-cloud` runs the parts of an e3 cloud deployment that e3's own CLI does not:
 apps, releases, users and roles, secrets, schedules, task configs, records'
-history and backups, feedback, and files from buckets. e3's CLI (`e3`, `@elaraai/e3-cli`) still
+history and backups, feedback, and files (a workspace's own storage, or a
+bucket of your own). e3's CLI (`e3`, `@elaraai/e3-cli`) still
 does what it does against any server: repositories, packages, workspaces,
 datasets, dataflow runs and copies. Both sign in with `e3 auth login` and share its
 credentials (`~/.e3/credentials.json`).
@@ -110,9 +111,10 @@ e3-cloud staging list URL
 ```
 
 - The staging starts as a copy of production, data included: its package,
-  inputs, records, apps, task settings and Files (declarations, bindings and
-  what each input took). `--as-is` makes a workspace there the staging as it
-  stands; `--replace` copies over one.
+  inputs, records, apps, task settings and Files declarations and bindings.
+  Its own storage for files starts empty, its values kept (6). `--as-is`
+  makes a workspace there the staging as it stands; `--replace` copies over
+  one.
 - Production is then protected: its package, apps and Files declarations
   change only by a release from its staging, or a rollback. People go on
   using it: inputs, records, runs and schedules.
@@ -186,21 +188,27 @@ e3-cloud release URL staging production --plan
 ### 6. Files
 
 ```bash
-e3-cloud files deploy URL staging src/files.ts
-e3-cloud files bind   URL staging upload s3://bucket/acme/staging/
-e3-cloud files sync   URL staging
+e3-cloud files deploy URL staging src/files.ts                                    # its sources read staging's own storage
 e3-cloud files push   URL staging ./data/prices.beast2 ./data/customers.beast2    # from disk: matched by name (or --as), put, synced
 e3-cloud files push   URL staging dataset:dev.customers --from ./repo              # a local workspace's dataset, as the file of its value
+e3-cloud files bind   URL staging upload ../production/upload/                    # or read production's files
 e3-cloud files sync   URL staging --target record:customers --reset customers     # named targets; a seeded record's file as its state again
 e3 dataflow run URL staging
 ```
 
+- A deployed workspace keeps its sources' files in storage of its own, a
+  folder each (`upload/`), which `files push` puts them in with your e3 login
+  alone: nothing to bind, and no command names a bucket. `files bind` points
+  a source elsewhere: a path relative to the workspace (`../production/upload/`
+  is production's folder, and a push through it puts there), or
+  `s3://bucket/prefix/`, a bucket of your own the deployment grants.
 - The declarations (which inputs files fill) travel with releases; where
   each source's files are (its binding) is each workspace's own. A staging
-  copied from production reads production's files until bound elsewhere.
-- Before a release whose declarations read a source production hasn't bound,
-  bind it there: `files bind URL production invoices s3://…`. The release is
-  refused until then.
+  copied from production keeps production's values, its own storage empty:
+  a push adds to them, and its first sync wipes nothing. Bind its sources to
+  `../production/<source>/` to rehearse on production's files.
+- A source production hasn't bound reads production's own storage: push its
+  files there after the release, or bind it to a bucket of your own before.
 - A release syncs nothing: after it, `files sync URL production`, then run
   production. Production refuses `files deploy` (9 for the exception).
   Declaring and decoding the files: the e3-cloud-files skill.
@@ -372,7 +380,7 @@ one of its own.
 - A protected workspace refuses e3's `workspace deploy`, an app deploy or
   removal, a Files deploy, a copy onto it, and its removal or its staging's.
   Its data goes on: inputs, records, runs and schedules, and its Files
-  bindings and syncs.
+  bindings, pushes and syncs.
 
 ## Releases
 
@@ -397,21 +405,27 @@ and runs next by hand or on its schedule. Owners and admins release.
 
 ## Files
 
-A solution declares in its code which of its inputs come from files in a
-bucket (`@elaraai/e3-cloud-files`, its own skill). The CLI deploys the
-declarations, binds each source and syncs, given a local repository's path or
-a repository URL:
+A solution declares in its code which of its inputs come from files
+(`@elaraai/e3-cloud-files`, its own skill). The CLI deploys the declarations,
+pushes files, binds a source elsewhere and syncs, given a local repository's
+path or a repository URL:
 
 - `files deploy <repo> <ws> <source>` runs the source (its default export is
   `Files.manifest(...)`) and checks the declarations against the package the
   workspace runs; `--dry-run` keeps nothing. A protected workspace refuses
   it: its declarations come by a release (`--force`, an admin's override).
-- `files bind <repo> <ws> <source> s3://bucket/prefix/` says where a source's
-  files are; `--region` when the bucket's isn't yours. Locally only:
-  `--profile` (the profile to read with), `--latest n` (each folder's n
-  greatest keys). A workspace's bindings are its own: a release never
+- `files bind <repo> <ws> <source> [location]` says where a source's files
+  are when not in the workspace's own storage under its name (a deployed
+  workspace's default): a path relative to the workspace (`inbound/`, `./`,
+  `../production/upload/`), shown as `own storage <path>`; or
+  `s3://bucket/prefix/`, a bucket of your own (`--region` when the bucket's
+  isn't yours), as every binding of a local repository is, which has no
+  storage of its own. No location binds it to its own folder again. Locally
+  only: `--profile` (the profile to read with), `--latest n` (each folder's
+  n greatest keys). A workspace's bindings are its own: a release never
   changes them, and a source may be bound before a release brings the
-  declarations that read it.
+  declarations that read it. Bound elsewhere, the targets that took files
+  where it was are taken again whole by the next sync, which it names.
 - `files sync <repo> <ws>` reads only files whose ETag or size changed and
   writes only inputs whose files changed; `--target`, `--reset`, `--dry-run`. It doesn't
   run the dataflow: `e3 dataflow run` does, and the sync prints the command.
@@ -425,7 +439,9 @@ a repository URL:
   …); `--reset`, `--dry-run`, `--profile` (a bucket the platform doesn't
   write). A seed's or feed's history names the file, and the dataset it was
   pushed from.
-- `files status <repo> <ws>`: the declarations, the bindings, the last sync.
+- `files status <repo> <ws>`: the declarations, where each source's files
+  are (`own storage upload/`, or a bucket's URL), what each mapping holds,
+  the last sync.
 
 ## Traps
 
@@ -437,8 +453,9 @@ a repository URL:
 - Sign in with `e3 auth login <server>`: there is no `e3 login`. A run is
   `e3 dataflow run <repo> <ws>`: there is no `e3 start`.
 - A release or a sync runs nothing: run the dataflow after either.
-- A release is refused while its Files declarations read a source the target
-  hasn't bound: bind it in the target first.
+- A source a release's Files declarations read that the target hasn't bound
+  reads the target's own storage: bind it in the target first when its files
+  are in a bucket of your own, or push them to the target after.
 - `secrets set` reads the value from stdin unless `--value` is given; the
   next run reads the new value.
 - The version is e3 cloud's own, not e3's: use the CLI of the e3 cloud

package/skills/e3-cloud-client/SKILL.md

@@ -70,19 +70,28 @@ try {
 ## Files
 
 - `getFiles(url, repo, ws, options)` answers a workspace's Files: its
-  declarations (`manifest`), where each source is bound (`bindings`), the
-  last sync, a sync under way, and `status` — per mapping, what it holds and
-  whether its record is `pending` (seeded from a file, its file not yet
-  arrived).
+  declarations (`manifest`), where each declared source's files are
+  (`bindings`: a path of the workspace's own storage, relative to it, which
+  a source bound to nothing reads as `<source>/`; or a bucket's URL), the
+  last sync, a sync under way, the buckets the deployment grants besides
+  (`granted`), and `status` — per mapping, what it holds and whether its
+  record is `pending` (seeded from a file, its file not yet arrived). No
+  answer names the bucket that holds own storage.
 - `deployFiles(url, repo, ws, manifest, options `{ dryRun?, force? }`)` deploys declarations
   (`Files.manifest(...)` from `@elaraai/e3-cloud-files`): `deployed` with
   the targets the next sync takes again whole (`retaken`), `checked` for a
   dry run, or `refused` with every problem. A workspace with a staging
   refuses it (`workspace_protected`) unless an admin forces it.
 - `bindFilesSource(url, repo, ws, binding, options)` says where a source's
-  files are (`s3://bucket/prefix/`): `bound` with what the next sync takes
-  again, or `refused` (a bucket the deployment does not let the repository
-  bind). Bindings are each workspace's own; a release never changes them.
+  files are when not in the workspace's own storage under its name: `url` a
+  path relative to the workspace (`inbound/`, `./`, `../production/upload/`;
+  `ownStoragePathProblem` from `@elaraai/e3-cloud-types` says why one isn't),
+  or `s3://bucket/prefix/`, a bucket the deployment grants. It answers
+  `bound` with the targets that took files where it was, which the next
+  sync takes again whole, or `refused` (a malformed path, a bucket the
+  deployment does not let the repository bind). Bindings are each
+  workspace's own, and relative to it: in a copy, a path names the copy's
+  own storage, which starts empty. A release never changes them.
 - `startFilesSync(url, repo, ws, { dryRun?, targets?, reset? }, options)`
   answers `started` with the sync's id, or `running` with the one under way;
   `filesSyncWait(url, repo, ws, id, options, { deadlineMs?, refresh?, signal? })`

package/skills/e3-cloud-files/SKILL.md

@@ -1,15 +1,20 @@
 ---
 name: e3-cloud-files
-description: "Files for e3 cloud — a solution's inputs that come from files in a bucket (s3://bucket/prefix/), declared in its code and synced when asked, the same on a local repository and a deployed workspace. Use when: (1) Declaring which inputs a bucket's files fill with Files.source(name) and its file, latest, folder and listing, then Files.manifest([...]) as a module's default export, (2) Decoding what arrives in a task: a Blob (file, latest), a Dict of path to Blob (folder) or a listing of sizes, times and ETags, as East's JSON, CSV or text, (3) Deploying the declarations to a workspace and binding each source to s3://bucket/prefix/ with e3-cloud files deploy and bind, (4) Syncing what changed with e3-cloud files sync, locally with your own cloud profile (--profile, --latest), then running the dataflow with e3 dataflow run, (5) Reading a refusal: declarations that don't fit the package (FilesDeclarationError, a deploy's problems), an unbound source, a file over its limit, a protected workspace (workspace_protected), (6) Moving declarations to production through staging: a release carries them with the package and apps, a rollback restores them, a copy brings bindings and what each input took, and production's bindings stay its own, (7) Reading Files' East types (FilesManifestType, FilesBindingType, FilesSyncReportType — @elaraai/e3-cloud-types), (8) Taking a beast2 file in as an input of its type with no task in between: file or latest with a type, a collection of any size, (9) Feeding a record's mutation from files with source.mutation(def, spec), def one its record declares (priceBook.mutations.load_prices), each new file applied once, (10) Pushing files from disk into a source and taking them in with e3-cloud files push, matched by name or --as, dry-run, unchanged, or a workspace's dataset (a task's output, an input, a record) as the file of its value with dataset:workspace.name and --from, local or remote at either end, (11) Seeding a record from a file with source.record(name, type, spec, parts): e3.record with no initial value, declared whole with its indexes, mutations and migrations, pending until its file, its tasks waiting meanwhile, (12) Syncing or resetting particular targets with --target and --reset."
+description: "Files for e3 cloud — a solution's inputs that come from files, declared in its code and synced when asked, the same on a local repository and a deployed workspace: in a deployed workspace's own storage (named by a path relative to the workspace, never a bucket) or a bucket of your own (s3://bucket/prefix/). Use when: (1) Declaring which inputs a bucket's files fill with Files.source(name) and its file, latest, folder and listing, then Files.manifest([...]) as a module's default export, (2) Decoding what arrives in a task: a Blob (file, latest), a Dict of path to Blob (folder) or a listing of sizes, times and ETags, as East's JSON, CSV or text, (3) Deploying the declarations to a workspace with e3-cloud files deploy, each source reading the workspace's own storage until e3-cloud files bind says otherwise (a path such as upload/ or ../production/upload/, or s3://bucket/prefix/ for a bucket of your own, which a local repository always needs), (4) Syncing what changed with e3-cloud files sync, locally with your own cloud profile (--profile, --latest), then running the dataflow with e3 dataflow run, (5) Reading a refusal: declarations that don't fit the package (FilesDeclarationError, a deploy's problems), an unbound source, a file over its limit, a protected workspace (workspace_protected), (6) Moving declarations to production through staging: a release carries them with the package and apps, a rollback restores them, a copy keeps its values and starts with empty storage of its own, and production's bindings stay its own, (7) Reading Files' East types (FilesManifestType, FilesBindingType, FilesSyncReportType — @elaraai/e3-cloud-types), (8) Taking a beast2 file in as an input of its type with no task in between: file or latest with a type, a collection of any size, (9) Feeding a record's mutation from files with source.mutation(def, spec), def one its record declares (priceBook.mutations.load_prices), each new file applied once, (10) Pushing files from disk into a source and taking them in with e3-cloud files push, matched by name or --as, dry-run, unchanged, or a workspace's dataset (a task's output, an input, a record) as the file of its value with dataset:workspace.name and --from, local or remote at either end, (11) Seeding a record from a file with source.record(name, type, spec, parts): e3.record with no initial value, declared whole with its indexes, mutations and migrations, pending until its file, its tasks waiting meanwhile, (12) Syncing or resetting particular targets with --target and --reset."
 ---
 
 # e3-cloud-files — files as e3 inputs
 
-A solution says in its code which of its inputs come from files in a bucket,
-and which records are fed from them. Each workspace says where those files
-are, a bucket and a prefix, and `e3-cloud files sync` brings in what changed:
-on a local repository with your own cloud credentials, in the cloud with the
-platform's read-only role. A file arrives as it is, a `Blob`, and a task
+A solution says in its code which of its inputs come from files, and which
+records are fed from them. A deployed workspace keeps those files in storage
+of its own, a folder for each source (`upload/`), which `e3-cloud files push`
+puts them in with an e3 login alone: nothing to bind, no bucket to name. A
+workspace may bind a source elsewhere: another folder of its repository's
+storage, by a path relative to the workspace (`../production/upload/`), or a
+bucket of your own (`s3://bucket/prefix/`), which a local repository, having
+no storage of its own, always names. `e3-cloud files sync` brings in what
+changed: on a local repository with your own cloud credentials, in the cloud
+with the platform's read-only role. A file arrives as it is, a `Blob`, and a task
 decodes it; or, named with a type, a beast2 file arrives as the value it
 holds, with no task in between. `e3-cloud files push` puts files from disk,
 or a workspace's datasets as the files of their values, into a source and
@@ -54,11 +59,15 @@ export default e3.package('orders', '1.0.0', rateTable);
 ```
 
 ```bash
-e3 workspace deploy ./repo dev --from-source src/package.ts
-e3-cloud files deploy ./repo dev src/files.ts                          # checked against the package dev runs
+# A deployed workspace: upload reads its own storage, upload/, so nothing to bind
+e3 workspace deploy $REPO dev --from-source src/package.ts             # REPO=https://e3.example.com/repos/acme
+e3-cloud files deploy $REPO dev src/files.ts                           # checked against the package dev runs
+e3-cloud files push   $REPO dev rates.json                             # into dev's own storage, then taken in
+e3 dataflow run $REPO dev                                              # the dataflow runs on it
+
+# A local repository: no storage of its own, so bind each source to a bucket
 e3-cloud files bind   ./repo dev upload s3://bucket/prefix/ --profile p # where upload's files are, for dev
 e3-cloud files sync   ./repo dev                                        # what changed comes in
-e3 dataflow run ./repo dev                                              # the dataflow runs on it
 ```
 
 ## Decision Tree
@@ -66,7 +75,7 @@ e3 dataflow run ./repo dev                                              # the da
 ```
 What do you need?
 ├─ Declare which inputs a bucket's files fill (src/files.ts)
-│   ├─ A place files come from        → Files.source(name) — each workspace binds it to s3://bucket/prefix/
+│   ├─ A place files come from        → Files.source(name) — a deployed workspace's own storage, <name>/, unless bound elsewhere
 │   ├─ One known file                 → source.file(input, { key })                    input: Blob
 │   ├─ A beast2 file as its value     → source.file(input, { key, type: ArrayType(Row) })  input: Array<Row>, no task between
 │   ├─ The newest of a folder         → source.latest(input, { prefix, include? })     input: Blob, the greatest key
@@ -86,8 +95,12 @@ What do you need?
 │   └─ Choose files by name or time   → a listing: rows.filter(($, row) => row.modified.greaterThan(since))
 ├─ Bring the files into a workspace (the e3-cloud CLI; <repo> a local path or a repository URL)
 │   ├─ Deploy the declarations        → e3-cloud files deploy <repo> <ws> src/files.ts [--dry-run]
-│   ├─ Say where a source's files are → e3-cloud files bind <repo> <ws> <source> s3://bucket/prefix/ [--region r]
-│   │   └─ Locally only               → --profile <aws profile>, --latest <n> (each folder's n greatest keys)
+│   ├─ Where a source's files are     → a deployed workspace's own storage, <source>/: push puts them there, nothing to bind
+│   ├─ Bind a source elsewhere        → e3-cloud files bind <repo> <ws> <source> [path | s3://bucket/prefix/] [--region r]
+│   │   ├─ Another folder of its own  → a path relative to the workspace: inbound/, ./ (its folder); none: <source>/ again
+│   │   ├─ Another workspace's files  → ../<workspace>/<folder>/ (a staging reading production's: ../production/upload/)
+│   │   ├─ A bucket of your own       → s3://bucket/prefix/ (one the deployment's configuration grants the repository)
+│   │   └─ A local repository         → s3://bucket/prefix/ always (no storage of its own), --profile <aws profile>, --latest <n>
 │   ├─ Bring in what changed          → e3-cloud files sync <repo> <ws> [--target t…] [--reset record…] [--dry-run]
 │   ├─ Put files from disk            → e3-cloud files push <repo> <ws> <file|dir>… [--as target] [--dry-run] [--profile p]
 │   ├─ Push a workspace's dataset     → e3-cloud files push <repo> <ws> dataset:<ws>.<name>… [--from <repo>] (a task's output, an input, a record)
@@ -95,12 +108,12 @@ What do you need?
 │   └─ Run the dataflow on it         → e3 dataflow run <repo> <ws> (a sync doesn't run it)
 ├─ Production: a workspace with a staging (a deployed repository's URL)
 │   ├─ Change its declarations        → files deploy to the staging, then e3-cloud release <url> <staging> <production>
-│   ├─ A source it doesn't bind yet   → e3-cloud files bind <url> <production> <source> s3://… before the release
+│   ├─ A source it doesn't bind       → reads production's own storage, <source>/ (push there), unless bound elsewhere
 │   ├─ See what a release does        → e3-cloud release … --plan (each input added, changed, unchanged, removed)
 │   ├─ After a release                → e3-cloud files sync <url> <production>, then e3 dataflow run
 │   ├─ Undo a release                 → e3-cloud rollback <url> <production> (declarations go back with the package)
 │   ├─ An emergency change            → e3-cloud files deploy … --force (an admin's; history records it; the next release undoes it)
-│   └─ Rehearse on production's files → e3-cloud staging add … (a copy: declarations, bindings, what each input took)
+│   └─ Rehearse on production's files → e3-cloud staging add … (a copy: values kept, own storage empty), then bind ../production/upload/
 ├─ Keep synced inputs across a package deploy → e3 workspace deploy … --inputs keep-edited
 └─ Drive it from code
     ├─ The checks                     → @elaraai/e3-cloud-files/check: checkFiles, checkBindings, readPackageSurface
@@ -115,7 +128,7 @@ What do you need?
 // src/files.ts
 import { Files } from '@elaraai/e3-cloud-files';
 
-export const upload = Files.source('upload');   // each workspace binds it to a bucket and prefix
+export const upload = Files.source('upload');   // a deployed workspace's own storage, upload/, unless bound elsewhere
 
 export const rates  = upload.file('rates', { key: 'rates.json' });                         // input: Blob
 export const stock  = upload.latest('stock', { prefix: 'stock/', include: '*.json' });    // input: Blob, the greatest key
@@ -149,8 +162,9 @@ export default Files.manifest([upload]);       // what e3-cloud files deploy dep
   bytes' hash, so the same bytes under another name are applied no more; a
   file the mutation refuses holds the ones after it until it changes; a busy
   record leaves the file to the next sync.
-- Keys and prefixes are relative to where a workspace binds the source; a
-  prefix is `''` or ends with `/`.
+- Keys and prefixes are relative to where the source's files are (a
+  deployed workspace's own `upload/`, or where it binds the source); a prefix
+  is `''` or ends with `/`.
 - `include` is a glob over the path under the prefix: `*` within one folder,
   `**` across folders, `?` one character, `[a-z]` one of a set (`[!_]` any
   but), `{csv,json}` any of its alternatives (`*.{csv,json}`).
@@ -175,7 +189,7 @@ file's path under the prefix, in path order.
 
 ```
 e3-cloud files deploy <repo> <workspace> src/files.ts [--dry-run]
-e3-cloud files bind   <repo> <workspace> upload s3://bucket/prefix/ [--region r] [--profile p] [--latest n]
+e3-cloud files bind   <repo> <workspace> upload [path | s3://bucket/prefix/] [--region r] [--profile p] [--latest n]
 e3-cloud files sync   <repo> <workspace> [--target name|record:r|mutation:r.m ...] [--reset record...] [--dry-run]
 e3-cloud files push   <repo> <workspace> <file|dir|dataset:ws.name>... [--from repo] [--as target] [--reset record...] [--dry-run] [--profile p]
 e3-cloud files status <repo> <workspace>
@@ -184,9 +198,10 @@ e3 dataflow run <repo> <workspace>
 
 `files push` matches each file to the mapping that takes it (a `file` by its
 name, a `latest` under its prefix, a directory to the `folder`; `--as` names
-one), checks its type and size, puts it where the source is bound (the
-platform signs the upload into the deployment's own bucket, bound to the
-file's SHA-256; your own credentials elsewhere), then syncs what was put. A
+one), checks its type and size, puts it where the source's files are (into
+the workspace's own storage by an upload the platform signs, bound to the
+file's SHA-256; into a bucket of your own with your own credentials), then
+syncs what was put. A
 file the source holds already is `unchanged`; refused: `no_mapping`,
 `ambiguous` (name the target with `--as`), `not_included` (the mapping's
 glob leaves it out), `not_latest` (a greater key would shadow it), a typed
@@ -222,7 +237,11 @@ its state again, whatever mutated it since.
 
 `<repo>` is a local repository's path or a repository URL. Deploy the package
 first (`e3 workspace deploy`), then the declarations, which are checked
-against it. A sync reads only files whose ETag or size changed, writes only
+against it. A deployed workspace's sources read its own storage until bound
+elsewhere, so `files push` works after `files deploy` alone; a local
+repository has none, so bind each source to a bucket before its first sync.
+Own storage is named by its path alone (`own storage upload/`): no command,
+history or answer names the bucket that holds it. A sync reads only files whose ETag or size changed, writes only
 inputs whose files changed, and prints the next command when any did. It
 doesn't run the dataflow: `e3 dataflow run` does. Locally the bytes land only in the
 repository; `--profile` names the profile to read with and `--latest n`
@@ -266,15 +285,19 @@ keeps only each folder's n greatest keys.
   refuses until they're deployed again. A package deploy also resets synced
   inputs unless it keeps them (`--inputs keep-edited`); the next sync takes
   them again whole.
-- A changed declaration, or a source bound elsewhere, has its inputs taken
-  again whole at the next sync.
+- A changed declaration has its targets taken again whole at the next sync;
+  so does a source bound elsewhere, for the targets that took files where it
+  was (`files bind` names them).
 - A workspace with a staging refuses `files deploy` (`workspace_protected`):
-  deploy to the staging and release. A release is refused while the
-  declarations read a source the production workspace hasn't bound: bind it
-  there first. A release syncs nothing: sync production after it.
-- Bindings never travel with a release; a copy carries them. A staging
-  started as a copy of production reads production's files until you bind it
-  elsewhere.
+  deploy to the staging and release. A source production hasn't bound reads
+  production's own storage, `<source>/`: push its files there, or bind it
+  elsewhere. A release syncs nothing: sync production after it.
+- Bindings never travel with a release; a copy carries them, relative to the
+  copy. A source in own storage (bound by a path, or to nothing) reads the
+  copy's own storage, which starts empty; the copy keeps the values it was
+  given, a file put there adds to them or replaces them, and its first sync
+  wipes nothing. To rehearse on production's files, bind the staging's source
+  to `../production/upload/`; a bucket of your own stays where it was.
 - The version is e3 cloud's own, not e3's: install the release built with the
   e3 the deployment runs, its peers (east, e3) at exactly the versions it
   names, and the `e3-cloud` CLI of the same release.