@mevdragon/vidfarm-devcli 0.2.7 → 0.2.9

package/.env.example

@@ -6,10 +6,19 @@ OPENROUTER_API_KEY=""
 GEMINI_API_KEY=""
 PERPLEXITY_API_KEY=""
 
+# Optional. Production CDK wires these automatically for the EC2 app and ZIP Lambda.
+VIDFARM_ZIP_LAMBDA_URL=""
+VIDFARM_ZIP_LAMBDA_SECRET=""
+VIDFARM_BILLING_URL=""
+VIDFARM_BILLING_SECRET=""
+VIDFARM_RATE_LIMITS_TABLE_NAME=""
+
 # Optional when calling a hosted Vidfarm API directly.
 VIDFARM_USER_ID=""
 VIDFARM_API_KEY=""
 
 # Optional local overrides. The CLI will choose sensible local defaults.
 PUBLIC_BASE_URL="http://localhost:3310"
+# Optional public browser-facing chat endpoint. Leave empty locally unless you want the UI to hit a separate chat host directly.
+PUBLIC_EDITOR_CHAT_URL=""
 REMOTION_MODE="local"

package/GETTING_STARTED.developers.md

@@ -46,7 +46,7 @@ https://calendly.com/zoom-gtm/creative-director-interviews
 
 0. Tell your manager your email so he can whitelist you access to Vidfarm. After he confirms you have access, login at https://vidfarm.cloud.zoomgtm.com
 
-1. Open VSCode in a new project called "Vidfarm-Developer"
+1. Open VSCode in a new project and create a new project folder "Vidfarm-Developer"
 
 2. Open terminal and login to github cli and npm cli (ask ai/codex if you need help). ask your manager if they gave you npm access to "vidfarm-devcli" yet.
 
@@ -85,32 +85,3 @@ That will populate with a reference folder of what a template code looks like. W
 8. Create a new folder beside src called `drafts/` which is where we will put messy files when needed.
 
 9. Now find an easy winning format from https://winning-formats-gallery-tiktok.cloud.zoomgtm.com/ and save the image to your drafts/ folder. then tell Codex to look at that image (right click, copy relative path, paste to codex), then tell codex please make a new template based on the image.
-
-## Publish Responsibility
-
-When your template is ready for hosted Vidfarm, your responsibility is only:
-
-1. push your template code to GitHub
-2. register or update the template source metadata so Vidfarm knows the repo URL, branch, and template folder path
-
-Your responsibility does not include:
-
-1. importing the source into the live platform
-2. activating the release
-3. making the template public/live
-
-Those are platform-admin steps. If an API route says `403 Admin access required` for import or activate, that means you reached the correct handoff boundary.
-
-When you need to register your template with hosted Vidfarm, use the dev CLI command below from your repo root:
-
-```bash
-npx @mevdragon/vidfarm-devcli register-source-hosted \
-  --env-file .env \
-  --template-id <uuid-v4> \
-  --slug-id <template_slug> \
-  --repo-url https://github.com/<you>/<repo> \
-  --branch main \
-  --template-module-path templates/vidfarm_template_<slug>/src/template.ts
-```
-
-That command uses your `VIDFARM_API_KEY` and sends the registration to the hosted REST API, so the template appears in Vidfarm's review queue with `pending_review` status.

package/README.md

@@ -30,6 +30,7 @@ npx @mevdragon/vidfarm-devcli dev --port 3310 --reset
 npx @mevdragon/vidfarm-devcli session
 npx @mevdragon/vidfarm-devcli validate-template --template-id template_0000
 npx @mevdragon/vidfarm-devcli copy-reference-template --template-dir ./src/vidfarm_template_0000
+npx @mevdragon/vidfarm-devcli autocreate-template ./drafts/my_format ./templates/vidfarm_template_my_format
 npx @mevdragon/vidfarm-devcli generate-template --slug-id template_0001 --template-dir ./templates/vidfarm_template_0001
 npx @mevdragon/vidfarm-devcli analyze-viral-dna --template-dir ./templates/vidfarm_template_0001
 npx @mevdragon/vidfarm-devcli analyze-visual-dna --template-dir ./templates/vidfarm_template_0001
@@ -38,6 +39,8 @@ npx @mevdragon/vidfarm-devcli presign-preview-media --file ./drafts/preview/exam
 
 After install, the package exposes both `vidfarm` and `vidfarm-devcli` as local binaries.
 
+`autocreate-template` prepares the auto-create harness run folder, stages media from the input path, snapshots the current harness files, scaffolds the output template, and writes an agent handoff prompt at `auto-create-templates/runs/<run_id>/agent_prompt.md`. Keep improving `auto-create-templates/AUTO_CREATE_TEMPLATES.md`; each new run uses the current harness and stores a per-run snapshot for traceability.
+
 ## What The Local CLI Does
 
 The local CLI runs the same template contract used by the hosted platform, but with local-first defaults:
@@ -88,6 +91,7 @@ The developer handoff ends at:
 
 - `git push` of the template code
 - template source registration or registration update
+- for an already-registered template, publishing the exact GitHub commit SHA that should enter review
 
 The developer handoff does not include:
 
@@ -95,7 +99,7 @@ The developer handoff does not include:
 - activating a release
 - making the template public/live
 
-If a developer receives `403 Admin access required` while trying to import or activate a registered source, that is expected. Those routes are for platform admins.
+If a developer receives `403 Admin access required` while trying to import or activate a registered source, that is expected. Those routes are for platform admins. Developers should use the publish-update flow to submit an exact commit SHA for review instead.
 
 ## Template Deploy Cycle
 
@@ -132,10 +136,10 @@ node dist/src/cli.js deploy-template-cycle \
 
 The important distinction is:
 
-- third-party developers only ship template repo changes plus registration metadata
+- third-party developers ship template repo changes plus registration metadata, and can publish an exact commit SHA for an existing registered template
 - platform admins import and activate those template repo changes
 - new source registrations land in the hosted review queue before approval
-- newly imported releases can be approved while an older active release stays live
+- developer-published commit SHAs become reviewable releases while an older active release stays live
 - platform code changes ship through the root prod deploy script
 - multiple templates can live in one git repo as long as each template has its own folder and its `template_module_path` points at that folder's `src/template.ts`
 
@@ -153,7 +157,20 @@ For hosted template source registration, treat `template_module_path` as repo-re
 
 For hosted registration, use `register-source-hosted`. It talks to the Vidfarm REST API directly, so the source record lands in the production database that backs the hosted review queue. `register-source-prod` remains as a compatibility alias for internal/operator workflows.
 
-For private GitHub repos, set `VIDFARM_GITHUB_TOKEN` or `GITHUB_TOKEN` in the hosted runtime environment before using the REST import and approval flow. The production API now performs the clone/import itself, so the token must be available to the server process rather than injected from the operator shell.
+For updates to an already-registered template, use `publish-update-hosted` with the exact reviewed commit SHA. The CLI packages that commit locally into a signed artifact, uploads it to platform-controlled S3 through the Vidfarm API, and then creates or refreshes the pending release for admin review without granting developers approval or activation rights.
+
+```bash
+node dist/src/cli.js publish-update-hosted \
+  --env-file .env \
+  --template-id c7af2cd8-f032-45fa-9d4d-7af0e85cf4ef \
+  --slug-id vidfarm_template_reddit_brainrot \
+  --repo-url https://github.com/mevdragon/vidfarm_templates.git \
+  --branch main \
+  --template-module-path src/vidfarm_template_reddit_brainrot/src/template.ts \
+  --commit-sha 5e05a90a05a40105cc6e3b6a06774fdfb60c1893
+```
+
+The hosted publish path no longer depends on server-side GitHub access for template updates. Prod imports the uploaded artifact from S3 during review/import.
 
 For local CLI usage, the `session` command gives you a local seeded session so you can test without manually wiring auth state.
 
@@ -180,4 +197,4 @@ If your template uses `ctx.remotion`, develop and validate it locally through th
 
 ## Next Read
 
-For the external template-author workflow, continue with [GETTING_STARTED.developers.md](./GETTING_STARTED.developers.md) and the example template in [`templates/template_0000`](./templates/template_0000).
+For the external template-author workflow, continue with [GETTING_STARTED.developers.md](./GETTING_STARTED.developers.md) and the example template in [`templates/vidfarm_template_0000`](./templates/vidfarm_template_0000).