activate-projectlisted

# activate-project Skill for **activating a guest project** that was deployed into the app slot (`/opt/fractera/app`, served on :3000). Fractera now deploys ANY repository — a fresh starter, our reference project (Fractera-Pro), or the user's own public repo. "Activation" is the step that makes that guest behave like a first-class Fractera project: it gains the standard page set and its cloud dependencies are migrated onto this server's substrate. Offer it right after a fresh deploy. This skill is the JUDGEMENT. The facts about what landed in the slot are in `/opt/fractera/app-slot.json` (`{framework, contract, repoUrl}`, written by bootstrap). Read that first. ## When to offer activation After a deploy whose `app-slot.json.framework` is **not** `fractera-pro` — i.e. an empty starter or the user's own repo. Fractera-Pro already ships activated. A plain starter or a cloud-coupled repo benefits most. Ask the owner once: > "Your project is live. Want me to activate it — add the Fractera workspace > pages and move any cloud database / storage / auth / vector store onto this > server? You can also skip and keep it exactly as is." Never activate without the owner's go — it edits their code. ## The invariant: one scenario for every repo Every activated project ends up working the SAME way, so one set of docs covers any repo. Do not invent a per-repo flow — follow these four moves in order. ### 1. Read (or create) the guest's own instruction The slot is governed by the gues