From 0c951c0ea9854b18a89224d2365fc2d63142bf5d Mon Sep 17 00:00:00 2001
From: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Date: Tue, 20 Oct 2026 08:10:52 +0000
Subject: [PATCH] docs: explain Git transformations when signing kits

The signing instructions did not account for Git changing signed file contents. Explain the signing warning and why local verification does not establish that committed bytes match.
---
 content/manuals/ai/sandboxes/customize/kits-v2.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/content/manuals/ai/sandboxes/customize/kits-v2.md b/content/manuals/ai/sandboxes/customize/kits-v2.md
index 64216dc889..6d83f41fa4 100644
--- a/content/manuals/ai/sandboxes/customize/kits-v2.md
+++ b/content/manuals/ai/sandboxes/customize/kits-v2.md
@@ -715,8 +715,14 @@ $ sbx kit verify --key cosign.pub ./my-kit/
 
 For a local directory, `sbx kit sign` writes a `kit.sig.bundle` file next to
 `spec.yaml`. Commit this file so consumers can verify a kit loaded from the Git
-repository. For an OCI kit, the signature is stored as an OCI referrer. You can
-sign an OCI kit after pushing it, or push and sign it in one step:
+repository.
+
+Git line-ending conversion and clean filters can invalidate a source signature.
+If `sbx kit sign` warns about these transformations, ensure Git preserves the
+signed files unchanged before sharing the Git reference.
+
+For an OCI kit, the signature is stored as an OCI referrer. You can sign an OCI
+kit after pushing it, or push and sign it in one step:
 
 ```console
 $ sbx kit push ./my-kit/ ghcr.io/myorg/my-kit:1.0 --sign