code-authoring-routerlisted

# Code authoring router Before editing, preserve the repository's current VCS state and inspect repository facts to select the construction guidance that matches the affected code. A generic request such as “결제 기능 추가해줘” is an implementation signal, not proof of a technology stack. ## Resolve project policy If root `vulpora.config.json` exists, validate and apply its `locale` and `vcs` policy. Otherwise use the portable defaults: follow the user and repository language, auto-detect the hosted VCS and default branch only when needed, and preserve the current branch and worktree. Do not create, switch, fetch, fast-forward, push, or open a change request merely because implementation was requested. Prepare a child branch only when the user/repository requires it or `vcs.prepareBranch` is `true`. In that opt-in path, use the configured provider and base branch (`auto` means the remote default, never an assumed `develop`), and preserve dirty or diverged work. The GitLab-specific `git-flow` skill may be used only when GitLab is proven and its house style matches the project policy. Record the resolved policy and any branch action with the routing evidence. ## Detect and route 1. Inspect project instructions, build files, dependency catalogs, source extensions, migration directories, mappings, query builders, and nearby tests. 2. Record the evidence paths and choose every installed, applicable authoring skill: | Repository and task evidence | Load before editing | |---|---| |