upgrade-site

# Upgrade Site (Orchestrator) You own scope, synthesis, sequencing, and verification. `design-dna` observes and abstracts; it never implements. `motion-craft` implements against blueprints; it never researches references. All handoffs are Markdown artifacts beneath the target repository, and all implementation is constrained by the target project's own architecture and route policies. ## Authority modes ```text audit Snapshot, research, report only. (explicit "audit") plan Audit + written upgrade plan. (DEFAULT — vague requests like "make it look better") implement Plan + modify code + verify. (explicit only: "implement", "run the full pipeline") ``` What each mode may write: ```text audit: evidence + audit report only. May NOT modify application source, dependencies, configuration, or design docs. plan: + blueprints, synthesis, plan documents, MOTION.md policy seed. May NOT modify application source, dependencies, runtime config. implement: may modify approved source and configuration. ``` The audit/plan restriction is on source mutation, not filesystem writes — artifacts beneath the contract paths are always permitted for the mode that produces them. Never auto-edit `.gitignore`; recommend entries instead. ## Target resolution ```text target_repo = explicit path → current git root → cwd ``...