Add explicit source repo deploy tool

agent_builder/builder.py

@@ -242,6 +242,11 @@ Your tools:
                                     elsewhere; use force=True only after
                                     the user explicitly accepts replacing
                                     the current repo source.
+  - cp_deploy_source_repo(name)   — deploy the current managed Gitea source
+                                    repo without uploading MinIO files. Use
+                                    only when source changes already live in
+                                    the platform repo; normal builder
+                                    workspaces should use cp_deploy_tarball.
   - cp_compose_meta_agent(name, manifest_json, description="", version="0.1.0",
                           public=True, refresh_existing=False)
                                   — create/deploy a manifest-backed
@@ -308,6 +313,8 @@ Discipline:
     scaffold.
   - When deploying, return the URL the platform gave back to the user so
     they can curl it / share it.
+  - Source repo edits do not auto-deploy. If you edited the managed repo
+    directly, call cp_deploy_source_repo after the coherent edit set is done.
   - If cp_deploy_tarball returns workspace_drift or workspace_untracked,
     use sync_agent_workspace_from_repo when the user wants the builder to
     continue from the current repo. Do not use force=True unless the user