Implement all 5 tasks: additive extension model, framework self-enforcement, changelog, project migration, dashboard review

README.md

@@ -35,7 +35,9 @@ This will:
 - Check for uncommitted changes and warn you
 - Pull the latest updates
 
-**Upgrading existing projects:** When the framework is updated, existing projects may need their framework files upgraded (new phases added, new prompts, etc.). To upgrade an existing project, tell the agent: "Upgrade automaton for this project." The agent will check for missing files and update them.
+**Upgrading existing projects:** The framework reads prompts, contracts, and scripts from `~/.automaton/` at runtime. Projects only override `.agent.md` and `.rules.md`. This means updating the global framework (`git pull`) automatically applies to all projects. No per-project upgrade is needed.
+
+If a project was set up under the old model (with copies of framework files), it needs migration first. Tell the agent: "Upgrade automaton for this project" to run the migration.
 
 ---
 
@@ -185,21 +187,23 @@ The framework uses a **layered approach** to file management, with a clear prece
 
 ### What files belong in each layer?
 
-- **Project's `.automaton/`**: .agent.md (project-specific settings like Autopilot mode, rules override), .rules.md (project-specific constraints)
+- **Project's `.automaton/`**: .agent.md (project-specific settings like Autopilot mode, rules override), .rules.md (project-specific constraints), extensions/ (optional additive overrides)
 - **Global `~/.automaton/`**: All prompt files, contracts, scripts, config.md, workflow.md
 
 ### Upgrading
 
-When you upgrade the global framework (e.g., after pushing bug fixes), existing projects may need their framework files upgraded. Tell the agent:
+The framework reads all base files from `~/.automaton/` at runtime. To update the framework:
 
+```bash
+cd ~/.automaton && git pull
+```
+
+This automatically applies changes to all projects — no per-project upgrade needed.
+
+If a project has stale framework file copies (from the old model), tell the agent:
 > "Upgrade automaton for this project."
 
-The agent will:
-1. Compare the project's `.automaton/` files with the global `~/.automaton/` files
-2. **Customized files** — If the project has customized a file (differs from global), **keep the project's version**
-3. **Outdated files** — If the project's file is identical to the old global version, **update from global**
-4. **New files** — If the global framework has new files, **add them to the project**
-5. Report what was upgraded, added, and skipped
+The agent will run `migrate-project.sh` to clean up stale files and move customizations to `extensions/`.
 
 ## Contact & Support
 [Insert Contact Info]