Repository navigation
Add guided reference authoring and the VFlow production origin - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and behavior
Agents could promote mixed concept boards into canonical character references and compose shots without a clear reference-authoring workflow. Add versioned MCP instructions/prompts/resources and a tools-only fallback, typed face/body/prop/scene/storyboard materials, per-item visual review, pinned source lineage, exact generation-input packets and external actual-use evidence. Strict projects enforce the same rules through domain, REST, MCP and UI; existing projects and immutable revisions remain readable.
Add the reference-authoring workbench with independent tile/original previews, review/history, source impact, input inspection and draft recovery. V2 interchange preserves material dependencies and storyboard baselines and rejects lossy v1 overwrites. No generation or rendering runtime is introduced.
Use
https://vflow.talkincode.netas the canonical website and/mcpendpoint. Retain the old hostname as a compatibility alias on the same Worker/D1/R2; OAuth discovery derives endpoints from the requested origin. Preserve the already-deployed OAuth, candidate-material and preview fixes that had not yet been committed.Data and rollout
Migration
0003_reference_authoring.sqladds reference document/evidence tables without rewriting projects, media or timelines. Existing OAuth migration 0002 remains intact. Apply schema before Worker promotion, preserve dashboard vars, and verify Access/OAuth, authenticated UI, input guidance and existing composition readback after deployment. Old data does not become automatically visually approved.Validation
npm run typecheckandnpm run lintnpm test: 49 checks across 15 suitesnpm run test:browser: 17 Chromium checks, including decoded original images, strict reference approval/input previews, read-only access and failed/unsaved draft recoveryCloses #1.