vite-plugin-zephyr 1.4.2 → 1.6.0

package/README.md

@@ -36,6 +36,31 @@ pnpm add --dev vite-plugin-zephyr
 bun add --dev vite-plugin-zephyr
 ```
 
+## AI Agent Skills (Optional)
+
+This package ships the `zephyr-vite` Agent Skill for AI coding agents, together
+with the shared `zephyr-core` and `zephyr-module-federation` guides. The
+skills are versioned with the package, so your agent reads guidance that
+matches the release you installed.
+
+Zephyr does not need Intent at runtime. Coding agents only find these skills
+after you opt in with
+[TanStack Intent](https://tanstack.com/intent/latest/docs/getting-started/quick-start-consumers):
+
+```sh
+pnpm add -D @tanstack/intent
+pnpm dlx @tanstack/intent@latest install
+```
+
+Allow `vite-plugin-zephyr` when `install` asks. Intent saves that choice in the
+`intent.skills` allowlist in your `package.json`. To check or load the skill
+yourself:
+
+```sh
+pnpm exec intent list
+pnpm exec intent load 'vite-plugin-zephyr#zephyr-vite'
+```
+
 ## Usage
 
 ### Basic Configuration

package/dist/lib/vite-plugin-zephyr.js

@@ -554,8 +554,18 @@ function withZephyrCore(options = {}) {
                 return null;
             }
         },
-        buildStart () {
+        async buildStart () {
             environmentBuildStarted = true;
+            try {
+                const engine = await zephyr_engine_defer;
+                if (engine.sourceContext && engine.sourceCapture?.phase !== 'build-start' && !engine.pendingSourceCapture) {
+                    const capture = (0, external_zephyr_agent_namespaceObject.captureSource)(engine.sourceContext, 'build-start');
+                    if (engine.hasActiveBuild) engine.sourceCapture = capture;
+                    else engine.pendingSourceCapture = capture;
+                }
+            } catch (error) {
+                (0, external_zephyr_agent_namespaceObject.handleGlobalError)(error);
+            }
         },
         buildEnd (error) {
             if (error) directBuildFailed = true;

package/dist/lib/vite-plugin-zephyr.mjs

@@ -2,7 +2,7 @@ import { readFile } from "node:fs/promises";
 import { createHash, randomUUID } from "node:crypto";
 import { createRequire } from "node:module";
 import magic_string from "magic-string";
-import { ApplicationContext, ZeErrors, ZephyrEngine, ZephyrError, assertZephyrBuildTarget, claimPartialAssetMapBatch, commitPartialAssetMapClaimBatch, createManifestContent, handleGlobalError, logFn, normalizeBasePath, rewriteEnvReadsToVirtualModule, rollbackPartialAssetMapClaimBatch, savePartialAssetMap, zeBuildAssets, zeBuildDashData, ze_log } from "zephyr-agent";
+import { ApplicationContext, ZeErrors, ZephyrEngine, ZephyrError, assertZephyrBuildTarget, captureSource, claimPartialAssetMapBatch, commitPartialAssetMapClaimBatch, createManifestContent, handleGlobalError, logFn, normalizeBasePath, rewriteEnvReadsToVirtualModule, rollbackPartialAssetMapClaimBatch, savePartialAssetMap, zeBuildAssets, zeBuildDashData, ze_log } from "zephyr-agent";
 import { extractEntrypoint } from "./internal/extract/extract-entrypoint.mjs";
 import { extract_mf_plugins } from "./internal/extract/extract_mf_plugin.mjs";
 import { extract_vite_assets_map } from "./internal/extract/extract_vite_assets_map.mjs";
@@ -514,8 +514,18 @@ function withZephyrCore(options = {}) {
                 return null;
             }
         },
-        buildStart () {
+        async buildStart () {
             environmentBuildStarted = true;
+            try {
+                const engine = await zephyr_engine_defer;
+                if (engine.sourceContext && engine.sourceCapture?.phase !== 'build-start' && !engine.pendingSourceCapture) {
+                    const capture = captureSource(engine.sourceContext, 'build-start');
+                    if (engine.hasActiveBuild) engine.sourceCapture = capture;
+                    else engine.pendingSourceCapture = capture;
+                }
+            } catch (error) {
+                handleGlobalError(error);
+            }
         },
         buildEnd (error) {
             if (error) directBuildFailed = true;

package/package.json

@@ -1,11 +1,12 @@
 {
   "$schema": "https://raw.githubusercontent.com/vitejs/vite-plugin-registry/refs/heads/main/data/schema/extended-package-json.schema.json",
   "name": "vite-plugin-zephyr",
-  "version": "1.4.2",
+  "version": "1.6.0",
   "description": "Vite plugin for Zephyr",
   "keywords": [
     "deploy",
     "module-federation",
+    "tanstack-intent",
     "vite",
     "vite-plugin",
     "zephyr"
@@ -24,6 +25,9 @@
     "dist",
     "README.md",
     "LICENSE",
+    "skills",
+    "!skills/_artifacts",
+    "!skills/**/.zephyr-generated",
     "!dist/**/*.map"
   ],
   "type": "commonjs",
@@ -51,12 +55,13 @@
     "acorn": "^8.18.0",
     "acorn-walk": "^8.3.5",
     "magic-string": "1.2.3",
-    "zephyr-agent": "1.4.2"
+    "zephyr-agent": "1.6.0"
   },
   "devDependencies": {
     "@module-federation/vite": "1.21.2",
     "@rslib/core": "1.0.0",
     "@rstest/core": "0.11.12",
+    "@tanstack/intent": "0.5.3",
     "@types/node": "^24.13.3",
     "rollup": "^4.63.1",
     "typescript": "~7.0.0",

package/skills/zephyr-core/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026-present Zephyr Cloud and contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/zephyr-core/README.md

@@ -0,0 +1,13 @@
+# zephyr-core
+
+Skill for general Zephyr frontend setup and deployment workflows.
+
+Includes:
+
+- `SKILL.md` for the main trigger and workflow
+- `references/sdk-setup.md` for plugin and codemod setup
+- `references/deployment-model.md` for versions, snapshots, tags, and environments
+- `references/env-vars.md` for `ZE_PUBLIC_*` and environment overrides
+- `references/examples-resume.md` for concrete starter examples
+- `references/docs-map.md` for docs links and `llms.txt`
+- `references/troubleshooting.md` for common setup issues

package/skills/zephyr-core/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: zephyr-core
+description: Use when the user asks about Zephyr setup, with-zephyr, SDK selection, Change Attribution, human/AI contributions, dirty-source version differences, versions, tags, environments, snapshot/version URLs, dashboard workflows, docs, or public env vars.
+license: Apache-2.0
+metadata:
+  author: Zephyr Cloud IO
+  purpose: Use when the user asks about Zephyr setup, with-zephyr, SDK selection, versions, tags, environments, snapshot/version URLs, dashboard workflows, docs, or public env vars.
+  domain: sdk
+  type: core
+sources:
+  - ZephyrCloudIO/zephyr-packages:**/skills/zephyr-core/references/*.md
+  - ZephyrCloudIO/zephyr-packages:**/scripts/sync-package-skills.mjs
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/attribution.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/hooks/*.cjs
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/index.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/rstack.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/bundlers/rstack.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/bundlers/index.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/engine/ast-grep.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/operations.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/types.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/tests/bundler-configs.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/tests/rstack.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/tests/rstack-inheritance.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/tests/codemod.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/src/tests/attribution.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/with-zephyr/README.md
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/change-attribution/*.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/transformers/ze-build-snapshot.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/transformers/ze-build-dash-data.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/zephyr-engine/index.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-edge-contract/src/lib/change-attribution.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-edge-contract/src/index.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-edge-contract/src/lib/snapshot.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-edge-contract/src/lib/zephyr-build-stats.ts
+  - ZephyrCloudIO/zephyr-packages:**/scripts/verify-change-attribution.mjs
+  - ZephyrCloudIO/zephyr-packages:**/scripts/verify-live-attribution.mjs
+  - ZephyrCloudIO/zephyr-packages:**/scripts/verify-attribution-storage.mjs
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/index.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/http/http-request.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/http/http-request.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/http/fetch-with-retries.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/http/fetch-with-retries.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/lib/node-persist/upload-provider-options.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-agent/src/zephyr-engine/__test__/upload_assets.test.ts
+  - ZephyrCloudIO/zephyr-packages:**/libs/zephyr-edge-contract/src/lib/api-contract-negotiation/get-api-contract.ts
+---
+
+# Zephyr Core
+
+Use this skill for Zephyr SDK adoption and build-integrated deployment. It ships
+with every published Zephyr package, including supporting libraries that are not
+themselves build plugins. Do not assume the package containing this guide exports
+`withZephyr`; choose the actual integration for the application's stack.
+
+Prefer a more specific skill shipped alongside this one for its supported task,
+such as `zephyr-vite` or `create-zephyr-apps`. Check the installed integration's
+README, exported types, and peer compatibility before applying code examples.
+
+Zephyr is a build-integrated deployment platform for frontend and frontend-adjacent apps: it plugs into the build, publishes immutable versions, and lets users route traffic through tags and environments.
+
+## What to cover
+
+- Start with the smallest useful answer.
+- Prefer Zephyr's user-facing model first: setup -> build -> version URL -> tags/envs -> promote/rollback.
+- Use repo/code-path nuance only when it clarifies behavior or corrects docs drift.
+- If the question is really about remote resolution, hosts/remotes, `zephyr:dependencies`, or multi-bundler Module Federation, switch to `../zephyr-module-federation/SKILL.md`.
+- First-time users usually need: a supported stack or fallback upload path, Zephyr auth/account access, and git metadata for repo/branch/commit identity.
+
+## What Zephyr does
+
+- Zephyr integrates with the build and publishes immutable frontend versions.
+- Zephyr gives users permanent version URLs plus mutable tags and environments.
+- Zephyr can manage public runtime config overrides and deployment routing.
+- Zephyr does not replace the app's own framework/bundler config; it integrates into it.
+- Zephyr does not make public `ZE_PUBLIC_*` values secret.
+
+## Core mental model
+
+- Zephyr plugs into the app build through a bundler/framework integration.
+- A build creates an immutable version/snapshot and a permanent version URL.
+- Tags and environments are mutable pointers on top of immutable builds.
+- Promotion and rollback are mostly pointer changes, not rebuilds.
+- `ZE_PUBLIC_*` values can be captured at build time and overridden per environment later.
+
+## Answer flow
+
+1. Identify the user's stack and deployment goal.
+2. Read `references/sdk-setup.md` for setup guidance.
+3. Read `references/deployment-model.md` for versions, snapshots, tags, envs, and dashboard workflows.
+4. Read `references/env-vars.md` if the task mentions env vars, runtime config, build once deploy everywhere, or `ZE_PUBLIC_*`.
+5. Read `references/examples-resume.md` when the user wants concrete starter patterns.
+6. Read `references/docs-map.md` when deeper docs links are useful.
+7. Read `references/troubleshooting.md` when setup/build/auth/git issues appear.
+8. Read `references/change-attribution.md` for optional tracking, agent/editor hooks,
+   source fingerprints, and version comparisons involving local changes. Obtain
+   explicit opt-in before enabling capture or installing hooks.
+
+## Source priorities
+
+- Canonical public docs: `https://docs.zephyr-cloud.io`
+- Raw docs path pattern: `https://docs.zephyr-cloud.io/<path>.md`
+- Docs index: `https://docs.zephyr-cloud.io/llms.txt`
+- Community help: `https://discord.gg/zephyrcloud`
+- Architecture docs: `https://docs.zephyr-cloud.io/reference/architecture.md`
+- Public docs source: `https://docs.zephyr-cloud.io`
+- Examples source: `https://github.com/ZephyrCloudIO/zephyr-examples`
+
+## Guardrails
+
+- Do not invent SDK names; verify against `references/sdk-setup.md`.
+- Do not blur version vs tag vs environment; explain the distinction plainly.
+- Do not present `ZE_PUBLIC_*` as secret storage. They are public client-facing values.
+- Call out docs drift when relevant instead of silently repeating conflicting details.

package/skills/zephyr-core/references/attribution-storage.md

@@ -0,0 +1,144 @@
+# Attribution storage and repository policy
+
+Read this when selecting storage, controlling source-text sharing, or implementing
+the endpoint. First enable tracking with [Change Attribution](change-attribution.md).
+
+## Repository preferences
+
+Commit `.zephyr/attribution.json` at the Git root. Each repo has its own file;
+apps in a monorepo share its capture preferences. It contains preferences, never
+credentials, custom endpoint URLs, or a claimed account tier:
+
+```json
+{ "schemaVersion": 1, "enabled": true, "storage": "local" }
+```
+
+Storage configuration requires an existing enabled repository; enable with
+`with-zephyr . --attribution` first. A blank codemod storage answer preserves
+existing preferences. Missing `storage`, including older configs, means **local**. Source copies,
+attribution, and version receipts stay in the worktree Git directory. Local
+mode neither resolves attribution credentials nor makes attribution requests,
+and attaches no attribution to uploaded snapshots/build stats. Ordinary Zephyr
+deployment still uploads its assets and normal deployment metadata.
+
+```bash
+pnpm exec ze-cli attribution configure --storage remote
+# Paid/BYOC: independently choose source-text fields.
+pnpm exec ze-cli attribution configure --storage remote --patches include --lines omit
+pnpm exec ze-cli attribution status
+```
+
+| Mode/account       | Source text sent                                        |
+| ------------------ | ------------------------------------------------------- |
+| Local, any account | None                                                    |
+| Remote, free       | Unified patch and structured changed-line text required |
+| Remote, paid       | Neither by default; either/both optional                |
+| Remote, BYOC       | Neither by default; either/both optional                |
+
+Free remote source-text opt-out is rejected before sending. Choose local to keep
+it local. Tier comes from authenticated service policy, not repo configuration
+or deployment provider. Paid/BYOC shared preferences can include
+`"content": { "patch": false, "lines": false }` or enable either field.
+
+All remote records include file hashes, attribution ranges/origins, and available
+session/model/effort/usage metadata. `patch` is the unified difference against the
+**captured Git HEAD**, with ordinary context. `lines` contains text/origin of
+added/removed lines. A patch inherently contains line text even when `lines` is
+false; omit both to share no source text. Range positions/origins remain metadata.
+New files can have every line in their difference. Full source snapshots and
+binary contents are not uploaded. Exclusions apply to working source and HEAD.
+Remote payloads are limited to 20 MiB. Server version comparisons need the Git
+baseline; patches cannot reconstruct unchanged committed files on their own.
+
+## Private restriction and precedence
+
+Keep this checkout local even when its shared config selects remote:
+
+```bash
+pnpm exec ze-cli attribution configure --storage local --local
+```
+
+This atomically writes `zephyr-attribution/config.local.json` inside the worktree
+Git directory with owner-only POSIX file permissions. It preserves shared config
+and cannot enable remote or additional content. Deliberately remove that file
+to resume shared settings. Local receipts also use owner-only files: this is
+filesystem protection, not disk encryption. Windows relies on worktree ACLs.
+
+Private restrictions apply first. Sharing requires both repo opt-in and server
+authorization. An optional shared `repositoryId` must match the service's
+application/repository binding. Unknown fields, including tokens, URLs, and tier,
+are rejected by configuration commands. Invalid or newer configuration at build
+time disables sharing without blocking deployment; the SDK does not ignore
+unrecognized permissions and accidentally authorize remote uploads. Credentials use existing SDK authentication/private storage; CI
+supplies credentials through its secret environment.
+
+## Control-plane contract and secure persistence
+
+The SDK implements the client and shared types. **Server endpoints, policy
+management, encryption, retention, and BYOC routing are not implemented in this
+workspace.** Remote publication requires `ATTRIBUTION_POLICY` in authenticated
+application configuration, with this shape:
+
+```json
+{
+  "schemaVersion": 1,
+  "repositoryId": "repo-123",
+  "revision": "policy-revision-7",
+  "storage": "remote",
+  "tier": "paid",
+  "content": { "patch": true, "lines": true }
+}
+```
+
+Policy `content` is the server's allowlist, not source-text opt-in. Paid/BYOC
+repo preferences still default off; free requires both allowed and included.
+Persist policy by organization/repository, allow repo-admin updates, retain
+revision/audit history, and derive tier from billing/BYOC entitlement. A repo
+file must never be able to claim a different tier.
+
+The client sends `AttributionUploadRequest` to **`POST /attribution`** on the
+existing authenticated API gateway. It includes application/repository/build/
+snapshot IDs, policy revision, effective content flags, attribution metadata,
+and optional HEAD comparison. It resolves bearer credentials at request time,
+requires HTTPS (loopback HTTP for fixtures), refuses redirects, and omits response
+bodies from diagnostics. Raw prompts, agent responses, transcript paths, and
+full source copies are excluded.
+
+The server must authenticate the caller, authorize repository access, verify
+application/build ownership, independently enforce current tier/content policy
+and revision, and reject stale or unauthorized requests. Deduplicate the
+repository/application/build `Idempotency-Key`: return the original record for
+retries and reject conflicting evidence for the same build. Store immutable
+records tied to those IDs and source fingerprint.
+
+Return `AttributionUploadResponse`: `status: "ok"`, opaque record ID, matching
+application/repository/build/snapshot IDs, and source fingerprint. Only after
+acknowledgment does the client put a small record reference in snapshots and
+build stats. Full evidence stays at the private endpoint. A private delivery
+receipt stays locally. If policy, source capture, credentials, delivery, or
+acknowledgment is unavailable, deployment continues without an attribution
+reference and emits a warning; source evidence stays local when capture succeeded.
+This also permits deployment before the control-plane endpoint ships. Reconcile pending records when the build publishes and expire
+orphaned records from failed deployments.
+
+Store policy in an access-controlled database and source evidence in private
+encrypted object storage using managed keys. Keep storage credentials in a
+service secret manager. Authorize evidence reads by repo membership, enforce
+retention/deletion, and audit policy changes/access without logging source
+bodies. Resolve BYOC destinations/credentials through authorized server
+configuration, never a repo-supplied URL. These are server requirements, not
+guarantees established by the client test.
+
+## Verification
+
+Build the agent and CLI, then run against a disposable generated app:
+
+```bash
+node scripts/verify-attribution-storage.mjs /tmp/zephyr-attribution-demo
+```
+
+The built CLI/SDK and real loopback HTTP fixture verify tier defaults, independent
+content flags, local isolation, build IDs, stable retry identity, rejected
+acknowledgments/redirects, and private restrictions. The verifier restores shared
+config and writes a private `storage-test-report.json`. Production authorization,
+encryption, retention, and BYOC routing require separate server verification.