gooseworks 0.5.7-dev.50.cbe6a0c1 → 0.5.7-dev.51.418668bd

package/dist/skills/server-entry-skills.d.ts

@@ -1,8 +1,8 @@
 /** The rulebook version this text was built from. */
 export declare const SERVER_RULEBOOK_VERSION = "1.3.0";
 export declare const SERVER_VIDEO_ENTRY_SKILLS: {
-    readonly 'goose-video': "---\nname: goose-video\ndescription: \"Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer.\"\nversion: 4.4.2\n---\n\n# GooseWorks video\n\nFrom an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.\n\nFor a video already started, call video_read and follow its next_step.\n\nExplicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.\n\nFor other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.\n4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.\n5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.\n6. The plan. Call video_create with the picked style and the products; its next_step says what follows.\n\n## A supplied video reference comes first\n\nWatch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.\nWhen they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.\nIf no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.\n\n## Rules\n\n- Talk to marketers: what they get and decide, never how it's made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.\n- Money is a credit number exactly as an answer gives it: never dollars or your own math.\n- Follow the next_step in every answer.\n- Card on screen (display_hint \"widget\"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.\n- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.\n- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.\n- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.\n- Never invent an offer, a claim or proof.\n- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.\n";
-    readonly 'make-custom-video': "---\nname: make-custom-video\ndescription: \"Keep an explicit custom choice. Study its reference and check custom-video support on this connection before planning.\"\nversion: 3.4.2\n---\n\n# GooseWorks video\n\nFrom an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.\n\nFor a video already started, call video_read and follow its next_step.\n\nExplicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.\n\nFor other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.\n4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.\n5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.\n6. The plan. Call video_create with the picked style and the products; its next_step says what follows.\n\n## A supplied video reference comes first\n\nWatch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.\nWhen they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.\nIf no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.\n\n## Rules\n\n- Talk to marketers: what they get and decide, never how it's made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.\n- Money is a credit number exactly as an answer gives it: never dollars or your own math.\n- Follow the next_step in every answer.\n- Card on screen (display_hint \"widget\"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.\n- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.\n- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.\n- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.\n- Never invent an offer, a claim or proof.\n- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.\n";
+    readonly 'goose-video': "---\nname: goose-video\ndescription: \"Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer.\"\nversion: 4.4.3\n---\n\n# GooseWorks video\n\nFrom an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.\n\nFor a video already started, call video_read and follow its next_step.\n\nExplicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.\n\nFor other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.\n\n1. The request. If they haven't said what the video is about, ask in one short question.\n2. The brand. Ask which brand only when brand_read lists several; with one, use it.\n3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.\n4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.\n5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.\n6. The plan. Call video_create with the picked style and the products; its next_step says what follows.\n\n## A supplied video reference comes first\n\nWatch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.\nWhen they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.\nIf no available style fits, or they explicitly want custom, catalog_fetch type skill make-custom-video on this connection before a project write. Require its complete production-harness dependency and current custom schemas. Follow its separate authenticated script and ingredient approvals, cumulative budgets and verified execution capability. If anything is unavailable, say so and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. Fetching a skill alone proves no execution capability.\n\n## Rules\n\n- Talk to marketers: what they get and decide, never how it's made.\n- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.\n- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.\n- Money is a credit number exactly as an answer gives it: never dollars or your own math.\n- Follow the next_step in every answer.\n- Card on screen (display_hint \"widget\"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.\n- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.\n- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.\n- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.\n- Never invent an offer, a claim or proof.\n- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.\n";
+    readonly 'make-custom-video': "---\nname: make-custom-video\ndescription: \"Make a custom video from its brief and studied reference, with authenticated script and ingredient reviews.\"\nversion: 3.4.3\nrequires_skills: [video-production-harness]\nharness_binding: gooseworks/video-actions/v1\n---\n\n# Human version\n\nThe owner approves the script, then actual storyboard/ingredients and budget. Both authenticated reviews must pass before production.\n\n---\n\n# Agent version\n\nInstalled entry: catalog_fetch type skill make-custom-video here once. Check live custom schemas before writes. Keep this environment; no retired actions, template fallback or reference-as-final import.\n\n## Load the production harness\n\nRequire complete video-production-harness content/scripts/files/version/contentHash. Read its orchestrator, phases and editorial/specialist guides. Save safe paths separately with hashes/dependencies. Incomplete/mixed packages block work. Resume recorded packages, inputs and jobs.\n\n## Keep the brief and study the reference\n\nExplicit custom skips video_formats and the picker. Keep requested mechanics/assets; animated text and product photos must not become a creator montage. Implicit references use goose-video to watch and compare template constraints; custom follows no match or their choice.\nRead brand_read (kit, products, rules), then knowledge_search. Use supported claims, real photos/logo. Watch playback, or timed frames spanning the video plus audio/transcript. Record hook, scene order, pace, framing, dialogue, text, product interactions and ending with times/gaps. URLs/thumbnails are not viewing. Missing access needs an accessible source or explicit brief-only choice.\n\n## Create or resume\n\nNew: video_create with brand_id, style custom, request and a required agent-generated UUID idempotency_key; retain products, name, reference_url and campaign. Reuse that key on retries. Resume with video_read the same project: retain plan_revision, custom_review, brand_context, production_manifest and execution; never create a replacement.\nReference resolve accepts direct files; social links cause no automatic paid lookup. After watching stored media, video_change custom reference attach uses asset_id and original analysis_revision. Skip needs explicit brief-only user_quote. Pending/failed reference blocks approval; a URL is not viewing.\nA resolved reference also needs draft.reference_observation: exact source_url, real duration_s, evidence_mode playback or frames_and_audio, observed_through_s covering 95%, and a timed picture/audio summary with gaps. Its data binds the script token. Resolve/attach is not watching.\n\n## Save script and ingredients\n\nFollow the harness phases. Discover specialists for the actual scenes; check inputs, outputs, dependencies and managed execution. Reuse suitable product photos and deterministic text animation. Never substitute a template driver. Bind operations to this project and approved scene/script revisions.\nvideo_change needs expected_revision (plan_revision), custom draft and optional script. Bind brand_context_digest to the returned bundle; never author server context. Keep packages outside the review payload. Quote paid operations through the live managed estimate path with real inputs/project. Save cumulative preview_estimate/render_estimate including committed spend. Missing price/unsupported inputs blocks production; no guessed rates/direct keys.\n\n## Two authenticated owner reviews\n\nShow the complete saved script and exact cumulative budget on the authenticated review card. Only the owner's actual signed button press approves. Chat yes, OAuth, user_quote, widget origin or a copied token is not proof; never manufacture a click or self-approve. Text-only/large reviews use returned authenticated Studio phase buttons and approval_surface URL.\nReread video_read after owner actions. Script approval permits quoted previews only. Save the actual storyboard, playable ingredients and render budget; ingredient approval permits clips. Require current script_approved/ingredients_approved, matching tokens/revision and budget. Changed reviews need renewed approval. A prior yes does not authorize changed work.\n\n## Execute, check and deliver\n\nRequire execution.local from a verified customer shell. No cloud, style-only kit, API host, worker or coworker sandbox. Otherwise report the gap.\nvideo_make needs expected_revision and custom render state. Resume the same render with approved tokens; report running/failed/complete honestly and honor Stop. Save actual prompts, settings, every scene and clip checks through video_change custom production. Watch the full output against the approved script, product and brand; save its full quality report. Completion needs a confirmed upload in this project; pin only the checked complete render. Read back manifest/final before delivery. Repairs need affected assets only and renewed approvals/budget.\n\nUse plain words and returned credits. No invented claims, approvals, assets or passing checks.\n";
 };
 export type ServerVideoEntrySlug = keyof typeof SERVER_VIDEO_ENTRY_SKILLS;
 /** renderEntrySkillRules(product) for the products the CLI's own entry skills cover. */

package/dist/skills/server-entry-skills.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"server-entry-skills.d.ts","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":"AAcA,qDAAqD;AACrD,eAAO,MAAM,uBAAuB,UAAU,CAAC;AAE/C,eAAO,MAAM,yBAAyB;;;CAuF5B,CAAC;AAEX,MAAM,MAAM,oBAAoB,GAAG,MAAM,OAAO,yBAAyB,CAAC;AAE1E,wFAAwF;AACxF,eAAO,MAAM,wBAAwB;;;;CA8B3B,CAAC"}
+{"version":3,"file":"server-entry-skills.d.ts","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":"AAcA,qDAAqD;AACrD,eAAO,MAAM,uBAAuB,UAAU,CAAC;AAE/C,eAAO,MAAM,yBAAyB;;;CA8F5B,CAAC;AAEX,MAAM,MAAM,oBAAoB,GAAG,MAAM,OAAO,yBAAyB,CAAC;AAE1E,wFAAwF;AACxF,eAAO,MAAM,wBAAwB;;;;CA8B3B,CAAC"}

package/dist/skills/server-entry-skills.js

@@ -2,7 +2,7 @@
 // The entry skill text our server builds, copied here because the CLI
 // cannot import gooseworks-app. Do not edit by hand.
 //
-// Source: gooseworks-app codex/reference-first-video @ 9372e1ee477b11828806030ac3550dfee1ba676f
+// Source: gooseworks-app codex/custom-video-adapter @ 6cf00ec7ed17d50c0956bd7ea6869640e01ad117
 //   apps/api/src/services/playbooks/entry-skill.ts      buildVideoEntrySkill(slug)
 //   apps/api/src/app-mcp-server/lib/video-policy.ts     renderEntrySkillRules(product)
 //
@@ -20,7 +20,7 @@ exports.SERVER_VIDEO_ENTRY_SKILLS = {
     'goose-video': `---
 name: goose-video
 description: "Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer."
-version: 4.4.2
+version: 4.4.3
 ---
 
 # GooseWorks video
@@ -44,7 +44,7 @@ For other new videos start with get_started (wants video, request). A card is no
 
 Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
 When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
-If no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.
+If no available style fits, or they explicitly want custom, catalog_fetch type skill make-custom-video on this connection before a project write. Require its complete production-harness dependency and current custom schemas. Follow its separate authenticated script and ingredient approvals, cumulative budgets and verified execution capability. If anything is unavailable, say so and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. Fetching a skill alone proves no execution capability.
 
 ## Rules
 
@@ -62,46 +62,53 @@ If no available style fits, or they explicitly want custom, check the selected c
 `,
     'make-custom-video': `---
 name: make-custom-video
-description: "Keep an explicit custom choice. Study its reference and check custom-video support on this connection before planning."
-version: 3.4.2
+description: "Make a custom video from its brief and studied reference, with authenticated script and ingredient reviews."
+version: 3.4.3
+requires_skills: [video-production-harness]
+harness_binding: gooseworks/video-actions/v1
 ---
 
-# GooseWorks video
+# Human version
 
-From an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.
+The owner approves the script, then actual storyboard/ingredients and budget. Both authenticated reviews must pass before production.
 
-For a video already started, call video_read and follow its next_step.
+---
 
-Explicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.
+# Agent version
 
-For other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.
+Installed entry: catalog_fetch type skill make-custom-video here once. Check live custom schemas before writes. Keep this environment; no retired actions, template fallback or reference-as-final import.
 
-1. The request. If they haven't said what the video is about, ask in one short question.
-2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.
-6. The plan. Call video_create with the picked style and the products; its next_step says what follows.
+## Load the production harness
 
-## A supplied video reference comes first
+Require complete video-production-harness content/scripts/files/version/contentHash. Read its orchestrator, phases and editorial/specialist guides. Save safe paths separately with hashes/dependencies. Incomplete/mixed packages block work. Resume recorded packages, inputs and jobs.
 
-Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
-When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
-If no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.
+## Keep the brief and study the reference
 
-## Rules
+Explicit custom skips video_formats and the picker. Keep requested mechanics/assets; animated text and product photos must not become a creator montage. Implicit references use goose-video to watch and compare template constraints; custom follows no match or their choice.
+Read brand_read (kit, products, rules), then knowledge_search. Use supported claims, real photos/logo. Watch playback, or timed frames spanning the video plus audio/transcript. Record hook, scene order, pace, framing, dialogue, text, product interactions and ending with times/gaps. URLs/thumbnails are not viewing. Missing access needs an accessible source or explicit brief-only choice.
 
-- Talk to marketers: what they get and decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow the next_step in every answer.
-- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
-- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.
-- Never invent an offer, a claim or proof.
-- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.
+## Create or resume
+
+New: video_create with brand_id, style custom, request and a required agent-generated UUID idempotency_key; retain products, name, reference_url and campaign. Reuse that key on retries. Resume with video_read the same project: retain plan_revision, custom_review, brand_context, production_manifest and execution; never create a replacement.
+Reference resolve accepts direct files; social links cause no automatic paid lookup. After watching stored media, video_change custom reference attach uses asset_id and original analysis_revision. Skip needs explicit brief-only user_quote. Pending/failed reference blocks approval; a URL is not viewing.
+A resolved reference also needs draft.reference_observation: exact source_url, real duration_s, evidence_mode playback or frames_and_audio, observed_through_s covering 95%, and a timed picture/audio summary with gaps. Its data binds the script token. Resolve/attach is not watching.
+
+## Save script and ingredients
+
+Follow the harness phases. Discover specialists for the actual scenes; check inputs, outputs, dependencies and managed execution. Reuse suitable product photos and deterministic text animation. Never substitute a template driver. Bind operations to this project and approved scene/script revisions.
+video_change needs expected_revision (plan_revision), custom draft and optional script. Bind brand_context_digest to the returned bundle; never author server context. Keep packages outside the review payload. Quote paid operations through the live managed estimate path with real inputs/project. Save cumulative preview_estimate/render_estimate including committed spend. Missing price/unsupported inputs blocks production; no guessed rates/direct keys.
+
+## Two authenticated owner reviews
+
+Show the complete saved script and exact cumulative budget on the authenticated review card. Only the owner's actual signed button press approves. Chat yes, OAuth, user_quote, widget origin or a copied token is not proof; never manufacture a click or self-approve. Text-only/large reviews use returned authenticated Studio phase buttons and approval_surface URL.
+Reread video_read after owner actions. Script approval permits quoted previews only. Save the actual storyboard, playable ingredients and render budget; ingredient approval permits clips. Require current script_approved/ingredients_approved, matching tokens/revision and budget. Changed reviews need renewed approval. A prior yes does not authorize changed work.
+
+## Execute, check and deliver
+
+Require execution.local from a verified customer shell. No cloud, style-only kit, API host, worker or coworker sandbox. Otherwise report the gap.
+video_make needs expected_revision and custom render state. Resume the same render with approved tokens; report running/failed/complete honestly and honor Stop. Save actual prompts, settings, every scene and clip checks through video_change custom production. Watch the full output against the approved script, product and brand; save its full quality report. Completion needs a confirmed upload in this project; pin only the checked complete render. Read back manifest/final before delivery. Repairs need affected assets only and renewed approvals/budget.
+
+Use plain words and returned credits. No invented claims, approvals, assets or passing checks.
 `,
 };
 /** renderEntrySkillRules(product) for the products the CLI's own entry skills cover. */

package/dist/skills/server-entry-skills.js.map

@@ -1 +1 @@
-{"version":3,"file":"server-entry-skills.js","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,qDAAqD;AACrD,EAAE;AACF,gGAAgG;AAChG,mFAAmF;AACnF,uFAAuF;AACvF,EAAE;AACF,+EAA+E;AAC/E,wEAAwE;AACxE,6EAA6E;AAC7E,6EAA6E;AAC7E,sEAAsE;AACtE,iEAAiE;;;AAEjE,qDAAqD;AACxC,QAAA,uBAAuB,GAAG,OAAO,CAAC;AAElC,QAAA,yBAAyB,GAAG;IACvC,aAAa,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0ChB;IACC,mBAAmB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0CtB;CACS,CAAC;AAIX,wFAAwF;AAC3E,QAAA,wBAAwB,GAAG;IACtC,GAAG,EAAE;;;;;;;;mJAQ4I;IACjJ,GAAG,EAAE;;;;;;;;;mJAS4I;IACjJ,MAAM,EAAE;;;;;;;;;mJASyI;CACzI,CAAC"}
+{"version":3,"file":"server-entry-skills.js","sourceRoot":"","sources":["../../src/skills/server-entry-skills.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,qDAAqD;AACrD,EAAE;AACF,+FAA+F;AAC/F,mFAAmF;AACnF,uFAAuF;AACvF,EAAE;AACF,+EAA+E;AAC/E,wEAAwE;AACxE,6EAA6E;AAC7E,6EAA6E;AAC7E,sEAAsE;AACtE,iEAAiE;;;AAEjE,qDAAqD;AACxC,QAAA,uBAAuB,GAAG,OAAO,CAAC;AAElC,QAAA,yBAAyB,GAAG;IACvC,aAAa,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0ChB;IACC,mBAAmB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiDtB;CACS,CAAC;AAIX,wFAAwF;AAC3E,QAAA,wBAAwB,GAAG;IACtC,GAAG,EAAE;;;;;;;;mJAQ4I;IACjJ,GAAG,EAAE;;;;;;;;;mJAS4I;IACjJ,MAAM,EAAE;;;;;;;;;mJASyI;CACzI,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gooseworks",
-  "version": "0.5.7-dev.50.cbe6a0c1",
+  "version": "0.5.7-dev.51.418668bd",
   "description": "GooseWorks CLI — give your coding agent real data tools",
   "bin": {
     "gooseworks": "./dist/index.js"
@@ -61,7 +61,7 @@
   "homepage": "https://gooseworks.ai",
   "author": "GooseWorks <help@gooseworks.ai>",
   "gooseworksRelease": {
-    "commit": "cbe6a0c1de3ad3474c0749645143a2bcbf009ab7",
+    "commit": "418668bd5cd38cc6dd255890c3b1b799cbdb2236",
     "branch": "dev"
   }
 }

package/skills/goose-video/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: goose-video
 description: "Make a video ad in this chat. Study a supplied video reference before comparing styles; follow the next_step in every answer."
-version: 4.4.2
+version: 4.4.3
 ---
 
 # GooseWorks video
@@ -25,7 +25,7 @@ For other new videos start with get_started (wants video, request). A card is no
 
 Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
 When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
-If no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.
+If no available style fits, or they explicitly want custom, catalog_fetch type skill make-custom-video on this connection before a project write. Require its complete production-harness dependency and current custom schemas. Follow its separate authenticated script and ingredient approvals, cumulative budgets and verified execution capability. If anything is unavailable, say so and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. Fetching a skill alone proves no execution capability.
 
 ## Rules
 

package/skills/make-custom-video/SKILL.md

@@ -1,42 +1,49 @@
 ---
 name: make-custom-video
-description: "Keep an explicit custom choice. Study its reference and check custom-video support on this connection before planning."
-version: 3.4.2
+description: "Make a custom video from its brief and studied reference, with authenticated script and ingredient reviews."
+version: 3.4.3
+requires_skills: [video-production-harness]
+harness_binding: gooseworks/video-actions/v1
 ---
 
-# GooseWorks video
+# Human version
 
-From an installed entry, first catalog_fetch type skill goose-video on this same connection and follow that body. An entry already fetched in this run needs no repeat fetch.
+The owner approves the script, then actual storyboard/ingredients and budget. Both authenticated reviews must pass before production.
 
-For a video already started, call video_read and follow its next_step.
+---
+
+# Agent version
+
+Installed entry: catalog_fetch type skill make-custom-video here once. Check live custom schemas before writes. Keep this environment; no retired actions, template fallback or reference-as-final import.
+
+## Load the production harness
+
+Require complete video-production-harness content/scripts/files/version/contentHash. Read its orchestrator, phases and editorial/specialist guides. Save safe paths separately with hashes/dependencies. Incomplete/mixed packages block work. Resume recorded packages, inputs and jobs.
+
+## Keep the brief and study the reference
+
+Explicit custom skips video_formats and the picker. Keep requested mechanics/assets; animated text and product photos must not become a creator montage. Implicit references use goose-video to watch and compare template constraints; custom follows no match or their choice.
+Read brand_read (kit, products, rules), then knowledge_search. Use supported claims, real photos/logo. Watch playback, or timed frames spanning the video plus audio/transcript. Record hook, scene order, pace, framing, dialogue, text, product interactions and ending with times/gaps. URLs/thumbnails are not viewing. Missing access needs an accessible source or explicit brief-only choice.
+
+## Create or resume
+
+New: video_create with brand_id, style custom, request and a required agent-generated UUID idempotency_key; retain products, name, reference_url and campaign. Reuse that key on retries. Resume with video_read the same project: retain plan_revision, custom_review, brand_context, production_manifest and execution; never create a replacement.
+Reference resolve accepts direct files; social links cause no automatic paid lookup. After watching stored media, video_change custom reference attach uses asset_id and original analysis_revision. Skip needs explicit brief-only user_quote. Pending/failed reference blocks approval; a URL is not viewing.
+A resolved reference also needs draft.reference_observation: exact source_url, real duration_s, evidence_mode playback or frames_and_audio, observed_through_s covering 95%, and a timed picture/audio summary with gaps. Its data binds the script token. Resolve/attach is not watching.
 
-Explicit custom: skip video_formats and steps 5–6. Keep their mechanics and assets; research the brand/product and study the reference for its custom plan. Check current custom support before any write.
+## Save script and ingredients
 
-For other new videos start with get_started (wants video, request). A card is not a style choice or proof of viewing. Follow the reference rule before style selection or a plan.
+Follow the harness phases. Discover specialists for the actual scenes; check inputs, outputs, dependencies and managed execution. Reuse suitable product photos and deterministic text animation. Never substitute a template driver. Bind operations to this project and approved scene/script revisions.
+video_change needs expected_revision (plan_revision), custom draft and optional script. Bind brand_context_digest to the returned bundle; never author server context. Keep packages outside the review payload. Quote paid operations through the live managed estimate path with real inputs/project. Save cumulative preview_estimate/render_estimate including committed spend. Missing price/unsupported inputs blocks production; no guessed rates/direct keys.
 
-1. The request. If they haven't said what the video is about, ask in one short question.
-2. The brand. Ask which brand only when brand_read lists several; with one, use it.
-3. The product. Named or none wanted: find its id with brand_read (sections: products), or use []. Otherwise the product card asks: say one line and wait. Without cards, ask which product by name; use the only one, or go on with none. Never ask again after a pick.
-4. Research. Read the brand kit, learnings and the chosen products with brand_read (sections kit and learnings, plus the products' ids), then knowledge_search for them. Note what to say and avoid.
-5. The styles. Call video_formats with the request and the products' ids ([] for none). The customer picks; never recommend one. A style they named that the answer lists as available is their pick. Otherwise, with the style card on screen, say one short line and wait; without one, print the style table from the answer as it is and ask nothing else.
-6. The plan. Call video_create with the picked style and the products; its next_step says what follows.
+## Two authenticated owner reviews
 
-## A supplied video reference comes first
+Show the complete saved script and exact cumulative budget on the authenticated review card. Only the owner's actual signed button press approves. Chat yes, OAuth, user_quote, widget origin or a copied token is not proof; never manufacture a click or self-approve. Text-only/large reviews use returned authenticated Studio phase buttons and approval_surface URL.
+Reread video_read after owner actions. Script approval permits quoted previews only. Save the actual storyboard, playable ingredients and render budget; ingredient approval permits clips. Require current script_approved/ingredients_approved, matching tokens/revision and budget. Changed reviews need renewed approval. A prior yes does not authorize changed work.
 
-Watch the actual video before choosing a style or writing a custom plan. Play through it, or inspect timestamped frames spanning it plus its audio/transcript. A URL, title, caption or thumbnail is not a viewing. Record the hook, scene order, pacing, narration/dialogue, framing, product interactions, text and ending, with timestamps and gaps. If access or sampling cannot answer an essential detail, ask for an accessible video or their choice to continue from the brief; never claim it was watched.
-When they have not chosen custom, call video_formats after brand research. For plausible matches, catalog_fetch type template returns the style's plan_note, scenes, duration, cast, sound and assets. Compare these against the observed reference and their essential choices. A similar title or high brand ranking does not prove a match. Explain fit or mismatch before they choose. Keep an explicit style choice; do not quietly change constraints or over-adapt it. Reassess a later reference before creating or rewriting a plan.
-If no available style fits, or they explicitly want custom, check the selected connection's current custom workflow before a project write. This server's video_create currently starts listed styles only: custom generation is unavailable through these actions. Say that plainly and keep the brief; do not substitute a template, import the reference as a finished video, use retired actions or switch environments. On a connection with a supported custom workflow, follow its separate authenticated script and ingredient approvals and quoted budgets; fetching this skill alone proves no execution capability.
+## Execute, check and deliver
 
-## Rules
+Require execution.local from a verified customer shell. No cloud, style-only kit, API host, worker or coworker sandbox. Otherwise report the gap.
+video_make needs expected_revision and custom render state. Resume the same render with approved tokens; report running/failed/complete honestly and honor Stop. Save actual prompts, settings, every scene and clip checks through video_change custom production. Watch the full output against the approved script, product and brand; save its full quality report. Completion needs a confirmed upload in this project; pin only the checked complete render. Read back manifest/final before delivery. Repairs need affected assets only and renewed approvals/budget.
 
-- Talk to marketers: what they get and decide, never how it's made.
-- Never mention tools, ids, JSON, commands, software, vendors, models, timings, retries or your checks.
-- Everything happens here: never ask the customer to install anything or use a CLI, slash command or other app, except npx -y gooseworks@0.5.7 video check and npx -y gooseworks@0.5.7 video make <id> when a next_step gives them.
-- Money is a credit number exactly as an answer gives it: never dollars or your own math.
-- Follow the next_step in every answer.
-- Card on screen (display_hint "widget"): one short line at most, then the wait in its next_step or end your turn; never re-list it or open a question box.
-- Paid work needs the customer's yes to the credit total first, on the card or in chat at the price shown; you never approve.
-- A yes counts only for the price the customer was shown: their press on the plan card, or their yes in chat sent with that price.
-- Where the app shows no card, print the plan and its price and ask for the customer's yes here; never send them to a website to approve.
-- Never invent an offer, a claim or proof.
-- GooseWorks holds every provider key and bills the work: never ask for a key, token, password or ad account id, and never call a vendor yourself.
+Use plain words and returned credits. No invented claims, approvals, assets or passing checks.

package/skills/manifest.json

@@ -1,12 +1,12 @@
 {
   "package": "gooseworks",
-  "version": "0.5.7-dev.50.cbe6a0c1",
+  "version": "0.5.7-dev.51.418668bd",
   "entries": {
     "gooseworks": "b648ab0e21d94405f2161db5d142770115a6b4551fef778a6aa51e2d30c005bb",
     "goose-ads": "0fd22d77148ce37500f9dfc3977abc1204baabe5faf8cf30d46c32bf60a410fa",
-    "goose-video": "22b9df57ee70773af27871ebcb0ac80cdf70cab957cf5743cf9ae6435b00dd02",
+    "goose-video": "83f1fe3822c899848a808e99b81f718527e12ef7c4552542ebbf5f0b6862a13d",
     "goose-video-local": "189cd2c24bbbb152d700847832b67ce651962959fd2381e878ed7ace6bc96a54",
-    "make-custom-video": "912da13ee2ec0c48f98eef5355c572b2ce6eea8679af360ae772a46cb76602cc",
+    "make-custom-video": "b1b4243582a9fbef37d2a63fc2a280aa51ae647a73d5423009c981736cc46bec",
     "goose-product-photos": "f2f9bcd9f5982b1e53d8aef384b8ee3f4e7dcba15985f40c6075ac3e29f413ce"
   }
 }