@edgestore/cli 1.0.0-rc.7 → 1.0.0

package/agent-assets/skills.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 1,
-  "revision": "a41182e1d6c8254cac64febaaf62a9480ffddfc1b3600362c3845aed573cdbbe",
+  "revision": "0fca43f8ee6d98c05ac4cc2aff26a53c7a92770eb121b60810b0b24d9694d280",
   "files": {
-    "edgestore-setup/SKILL.md": "---\nname: edgestore-setup\ndescription: Use when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application. Not for unrelated storage migrations or account administration.\nlicense: MIT\n---\n\n# EdgeStore setup\n\nImplement uploads through the application's UI and server route. Verify the upload\nand retrieval there; if runtime access is unavailable, report what remains untested.\n\n## Establish the application and API version\n\nUse `edgestore --cwd <app> agent context --json` when the CLI is available. Otherwise\ninspect the selected workspace's manifests, installed EdgeStore package metadata,\nexisting routes/provider, and backend env-file convention. In a monorepo identify\nthe frontend and backend separately. Use the app's package versions, not the CLI's.\n\nRead the relevant installed `@edgestore/server`, `@edgestore/react`, or\n`@edgestore/sdk` `agent-docs/README.md` and follow its local references. These\nbelong to the installed package version; the skill and CLI can be newer. If the\nreference is absent, use installed types/source and version-matched documentation,\nand mention the fallback. Read the references again after installing packages.\n\nFor an existing 0.x integration, resolve maintenance versus migration with the\nuser before changing APIs. Preserve installed versions unless an upgrade is\nauthorized. For new integrations, install EdgeStore v1 packages from the `rc`\ntag (for example, `@edgestore/server@rc` and `@edgestore/react@rc`); use\n`@edgestore/sdk@rc` or `@edgestore/cli@rc` when needed. For missing packages in\nan existing integration, choose a compatible, explicit version. Use other\nprereleases only when requested or required by the application.\n\n## Choose the integration\n\nReuse the app's architecture, existing buckets, and configured storage provider.\nRead the matching installed server reference: `next.md` (App or Pages Router),\n`tanstack-start.md`, `remix.md` (Remix or React Router framework mode), `astro.md`,\n`hono.md`, `express.md`, or `fastify.md`. Check the app's routing convention and\nframework version before adapting examples. A React Router client-side app still\nneeds a backend. Reuse the existing backend or ask which one to add. Preserve S3,\nAzure, and custom providers rather than provisioning hosted EdgeStore resources.\n\nInfer a bucket name from the application's feature (for example avatars or\nattachments); fall back to `publicFiles` when context is insufficient. Infer public\nversus protected access from the application. Ask when the access policy is\nambiguous or the files may be sensitive. Configure the application's authorization\nrules for protected files.\n\nBefore changing configuration or provisioning, summarize the proposed setup for\napproval: app/backend, provider, account/project to create or reuse, bucket name,\nwho can access files, upload limits, and env destination. Proceed once approved;\nask again only if the plan materially changes. Reuse an existing env file when\nthe backend already loads it; otherwise use the framework's convention. Preserve\nexisting env values.\n\n## Use MCP and the CLI\n\nPrefer an available MCP for an action it supports; otherwise use the CLI.\nFor hosted setup, complete authentication, project linking, and credential\ndelivery as part of the task. When the CLI is needed but missing, install or\ninvoke `@edgestore/cli` with the application's package manager using the version\nguidance above. Start with read-only discovery.\nWhen sign-in is needed, initiate it with the available tooling, ask the user to\ncomplete the browser step, then resume setup and verification.\n\nCreating resources requires authorization for that setup. A project already\ncreated through MCP should be linked locally, not created again through CLI.\nAfter an uncertain mutation result, inspect for the resource before retrying or\nswitching tools. Do not delete/empty buckets, revoke keys, enable billable overage, or\nchange unrelated resources as an implicit setup step.\n\nFor hosted provisioning or credential delivery, read\n[references/hosted-setup.md](references/hosted-setup.md).\n\n## Implement and verify\n\nConfigure the backend router/provider and the matching client endpoint using\ninstalled references. Keep server keys in a loaded, gitignored backend env file,\nnot frontend variables (`VITE_*`, `NEXT_PUBLIC_*`).\nTreat credentials as required configuration. Do not add conditional providers,\nupload-enable flags, or disabled setup placeholders merely because authentication\nis pending. Finish setup instead; preserve optional-storage behavior only when\nthe application requires it.\nIn split workspaces, export the real backend router type and import it with\n`import type` on the frontend. For cross-origin calls, configure CORS for the\nintended frontend origin. Wrap the upload UI with the React provider.\n\nFor new attachment UI, reuse an existing upload component or build a reusable\ndropzone, preferably with `react-dropzone`, with accessible file selection,\nprogress, and error feedback. Use the React package's `dropzone.md`, `multi-file.md`,\nand `uploader-provider.md` references for examples. If absent, see the\n[Dropzone](https://edgestore.dev/docs/components/dropzone.md),\n[Multi-file uploader](https://edgestore.dev/docs/components/multi-file.md), and\n[Uploader provider](https://edgestore.dev/docs/components/uploader-provider.md) guides.\nAdapt the examples to the installed APIs and app styling; do not introduce a new\nstyling system just to use them.\n\nFor a failing integration, read the installed server's `troubleshooting.md` and\nthe React package's `errors.md`. Diagnose the failing app request before changing\nremote resources or credentials.\n\nRun `edgestore --cwd <app> doctor --offline` when available, plus the app's own\ntypecheck/build/tests. Investigate doctor warnings and skipped checks. Start the\napp, upload a small test file through its UI and server route, and independently\nretrieve and check the bytes.\nFor protected access, verify unauthenticated retrieval is denied and authorized\nretrieval works.\n\nUse the account and project authorized for testing. Keep credentials and signed\nURLs out of agent output; retrieve protected files in a local process that returns\nonly the result. Clean up only this task's test resources. Summarize the integration\nchoices, checks performed, blockers, and any test resources left behind.\n",
+    "edgestore-setup/SKILL.md": "---\nname: edgestore-setup\ndescription: Use when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application. Not for unrelated storage migrations or account administration.\nlicense: MIT\n---\n\n# EdgeStore setup\n\nImplement uploads through the application's UI and server route. Verify the upload\nand retrieval there; if runtime access is unavailable, report what remains untested.\n\n## Establish the application and API version\n\nUse `edgestore --cwd <app> agent context --json` when the CLI is available. Otherwise\ninspect the selected workspace's manifests, installed EdgeStore package metadata,\nexisting routes/provider, and backend env-file convention. In a monorepo identify\nthe frontend and backend separately. Use the app's package versions, not the CLI's.\n\nRead the relevant installed `@edgestore/server`, `@edgestore/react`, or\n`@edgestore/sdk` `agent-docs/README.md` and follow its local references. These\nbelong to the installed package version; the skill and CLI can be newer. If the\nreference is absent, use installed types/source and version-matched documentation,\nand mention the fallback. Read the references again after installing packages.\n\nFor an existing 0.x integration, resolve maintenance versus migration with the\nuser before changing APIs. Preserve installed versions unless an upgrade is\nauthorized. For missing packages choose a compatible, explicit version. Use a\nprerelease only when requested or required by the application.\n\n## Choose the integration\n\nReuse the app's architecture, existing buckets, and configured storage provider.\nRead the matching installed server reference: `next.md` (App or Pages Router),\n`tanstack-start.md`, `remix.md` (Remix or React Router framework mode), `astro.md`,\n`hono.md`, `express.md`, or `fastify.md`. Check the app's routing convention and\nframework version before adapting examples. A React Router client-side app still\nneeds a backend. Reuse the existing backend or ask which one to add. Preserve S3,\nAzure, and custom providers rather than provisioning hosted EdgeStore resources.\n\nInfer a bucket name from the application's feature (for example avatars or\nattachments); fall back to `publicFiles` when context is insufficient. Infer public\nversus protected access from the application. Ask when the access policy is\nambiguous or the files may be sensitive. Configure the application's authorization\nrules for protected files.\n\nBefore changing configuration or provisioning, summarize the proposed setup for\napproval: app/backend, provider, account/project to create or reuse, bucket name,\nwho can access files, upload limits, and env destination. Proceed once approved;\nask again only if the plan materially changes. Reuse an existing env file when\nthe backend already loads it; otherwise use the framework's convention. Preserve\nexisting env values.\n\n## Use MCP and the CLI\n\nPrefer an available MCP for an action it supports; otherwise use the CLI.\nFor hosted setup, complete authentication, project linking, and credential\ndelivery as part of the task. When the CLI is needed but missing, install or\ninvoke `@edgestore/cli` with the application's package manager using the version\nguidance above. Start with read-only discovery.\nWhen sign-in is needed, initiate it with the available tooling, ask the user to\ncomplete the browser step, then resume setup and verification.\n\nCreating resources requires authorization for that setup. A project already\ncreated through MCP should be linked locally, not created again through CLI.\nAfter an uncertain mutation result, inspect for the resource before retrying or\nswitching tools. Do not delete/empty buckets, revoke keys, enable billable overage, or\nchange unrelated resources as an implicit setup step.\n\nFor hosted provisioning or credential delivery, read\n[references/hosted-setup.md](references/hosted-setup.md).\n\n## Implement and verify\n\nConfigure the backend router/provider and the matching client endpoint using\ninstalled references. Keep server keys in a loaded, gitignored backend env file,\nnot frontend variables (`VITE_*`, `NEXT_PUBLIC_*`).\nTreat credentials as required configuration. Do not add conditional providers,\nupload-enable flags, or disabled setup placeholders merely because authentication\nis pending. Finish setup instead; preserve optional-storage behavior only when\nthe application requires it.\nIn split workspaces, export the real backend router type and import it with\n`import type` on the frontend. For cross-origin calls, configure CORS for the\nintended frontend origin. Wrap the upload UI with the React provider.\n\nImplement upload UI as a reusable component, reusing the app's components or\nadapting the React package's component references. For attachments, provide\ndrag-and-drop and file selection with a file list. For profiles or compact forms,\nchoose an avatar picker, file field, or upload button as appropriate.\nIf the installed references are absent, see the\n[Dropzone](https://edgestore.dev/docs/components/dropzone.md),\n[Multi-file uploader](https://edgestore.dev/docs/components/multi-file.md),\n[Avatar](https://edgestore.dev/docs/components/avatar.md),\n[File field](https://edgestore.dev/docs/components/file-field.md),\n[Upload button](https://edgestore.dev/docs/components/upload-button.md), and\n[Uploader provider](https://edgestore.dev/docs/components/uploader-provider.md) guides.\nUse the docs origin recorded in the installed references for these online guides.\nAdapt the examples to the installed APIs and app styling; do not introduce a new\nstyling system just to use them. For custom dropzones, prefer `react-dropzone`\nwith accessible file selection, progress, and error feedback.\n\nFor uploads in unsaved forms, use temporary files when supported: upload, save\nthe record, then confirm. A failed database save must leave the files temporary.\nPersist the upload result's ID/key and URL directly. Do not add a backend `get()`\njust to recheck the uploaded URL or size: it can return 404 while processing is\npending. Validate input and authorize attachments in the app; fetch authoritative\nmetadata only when the feature needs it. Wait for processing only when processed\ndetails are needed immediately, using the installed API's opt-in support.\n\nFor a failing integration, read the installed server's `troubleshooting.md` and\nthe React package's `errors.md`. Diagnose the failing app request before changing\nremote resources or credentials.\n\nRun `edgestore --cwd <app> doctor --offline` when available, plus the app's own\ntypecheck/build/tests. Investigate doctor warnings and skipped checks. Start the\napp, upload a small test file through its UI and server route, and independently\nretrieve and check the bytes.\nFor protected access, verify unauthenticated retrieval is denied and authorized\nretrieval works.\n\nUse the account and project authorized for testing. Keep credentials and signed\nURLs out of agent output; retrieve protected files in a local process that returns\nonly the result. Clean up only this task's test resources. Summarize the integration\nchoices, checks performed, blockers, and any test resources left behind.\n",
     "edgestore-setup/agents/openai.yaml": "interface:\n  display_name: \"EdgeStore Setup\"\n  short_description: \"Use when adding or troubleshooting EdgeStore file uploads.\"\n",
     "edgestore-setup/references/hosted-setup.md": "# Hosted setup and credential handoff\n\nUse MCP first for supported account/project/bucket discovery and authorized\nchanges; otherwise use the CLI. Confirm the account and project in the tool's\nmetadata before making changes.\n\nTo configure MCP:\n\n```sh\nedgestore mcp setup --client codex --dry-run --json\nedgestore mcp setup --client codex --yes\n```\n\nUse `claude` or `cursor` for those clients. Setup configures\n`https://api.edgestore.dev/mcp`. Sign in through your client and review the\nrequested permissions.\n\nCheck `--help` for the installed CLI's available commands. Use `--json` and file\ndelivery to keep secrets out of tool output. For CLI authentication, run\n`edgestore login`. If it opens a browser, use that flow rather than opening the\nsame authorization URL again.\n\nAfter MCP creates/selects a project, link the backend to that same project and\nexisting env convention:\n\n```sh\nedgestore --cwd <backend> project link <project-base-path> --env-file <env-file> --json\n```\n\nReuse an existing valid backend key when possible. When a new key is authorized:\n\n```sh\nedgestore --cwd <backend> project key create <project-base-path> --name local --output <env-file> --json\n```\n\nThe destination must be gitignored. If values already exist, inspect the\nconfiguration before considering `--update`. Check key presence and project\nassociation without reading secret values into agent context. If file delivery is\nunavailable, ask the user to configure the key locally, not paste it into chat.\nDo not substitute dashboard instructions for setup the available tools can perform.\nOn partial failure, follow the returned recovery status before retrying.\n\n`init` provisions or links resources. Use `project link` when MCP has already\ncreated the project.\n"
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@edgestore/cli",
-  "version": "1.0.0-rc.7",
+  "version": "1.0.0",
   "description": "Command-line interface for EdgeStore accounts and projects",
   "homepage": "https://edgestore.dev",
   "license": "MIT",
@@ -39,7 +39,7 @@
     "@babel/parser": "7.29.7",
     "@babel/types": "7.29.7",
     "@clack/prompts": "1.7.0",
-    "@edgestore/sdk": "1.0.0-rc.7",
+    "@edgestore/sdk": "1.0.0",
     "@manypkg/find-root": "3.1.0",
     "@manypkg/get-packages": "3.1.0",
     "@napi-rs/keyring": "1.3.0",