fix: address Guardian review findings — sync Creator agent, wire hooks, add cost table

- Sync agents/creator.md output format with plan-phase skill (3-axis confidence,
  alternatives considered, mini-reflect) — fixes adaptation rule A3 dependency
- Wire hook points into orchestration Act phase (pre-merge, post-merge)
- Add cost-per-agent-tier table to autonomous-mode for budget scheduling
- Add team preset loading reference to orchestration Step 0

skills/orchestration/SKILL.md

@@ -9,7 +9,9 @@ This skill guides you through running a full ArcheFlow orchestration using Claud
 
 ## Step 0: Choose a Workflow
 
-Assess the task and pick:
+If `.archeflow/teams/<name>.yaml` exists, the user can reference a team preset: `"Use the backend team"`. Load the preset's phase config instead of built-in defaults. See `archeflow:custom-archetypes` skill for preset format.
+
+Otherwise, assess the task and pick:
 
 | Signal | Workflow |
 |--------|----------|
@@ -252,8 +254,9 @@ Example: "done when pytest passes and Guardian approves with 0 CRITICAL"
 If completion criteria are defined, **all criteria must pass** — reviewer approval alone is not sufficient. If tests fail but reviewers approved, cycle back with "tests failing" as feedback to Creator.
 
 ### All Approved (and completion criteria met)
-1. Merge the Maker's worktree branch into the target branch
-2. **Post-merge verification:** Run the project's test suite on the merged branch
+1. **Pre-merge hooks:** Check `.archeflow/hooks.yaml` for `pre-merge` hooks. Run them. If `fail_action: abort`, stop and report.
+2. Merge the Maker's worktree branch into the target branch
+3. **Post-merge hooks:** Run `post-merge` hooks from `.archeflow/hooks.yaml` if defined. Then run the project's test suite on the merged branch
    - Tests pass → proceed to step 3
    - Tests fail → **auto-revert** the merge commit, report the failure, and cycle back with "integration test failure on main" as feedback
 3. Report: what was implemented, what was reviewed, any warnings noted