Add adaptive, evidence-driven architecture upgrade: decision-loop orchestrator, action catalog, evidence-state handoffs, process quality, stop conditions

- Orchestrator: linear flow replaced by adaptive decision loop
  (UNDERSTAND→ESTIMATE→LOAD CONTEXT→CHOOSE ACTION→EXECUTE→VERIFY→RE-PLAN/STOP→LEARN)
- New sections: Task Complexity Estimation (ESTIMATE→EXECUTE→EXPAND),
  Action Catalog with 24 tool-card actions, Evidence-First State and Handoff
  Discipline (9-field state records, state separation, long-horizon persistence),
  Process Quality anti-patterns, Cost and Token Awareness, Stop Conditions,
  adaptive planning + failure recovery (7 failure types), lightweight quality gates
- All 13 agents preserved; 12 subagents gain role-adapted Evidence & Handoffs
  sections (evidence product, stop, escalation) after Repository Intelligence
- Repository Intelligence Bootstrap extended with Knowledge Lifecycle rules;
  .opencode structure unchanged (knowledge/state dirs intentionally not added)
- New docs: AGENT_ARCHITECTURE.md (full architecture incl. simple/complex
  execution traces, ownership table, weaknesses) and EVALUATION_SCENARIOS.md
  (12 runtime scenarios + scoring rubric)
- New test: scripts/test-agent-architecture.sh (16 structural checks)
- Validation: 16/16 architecture tests PASS, 11/11 bootstrap tests PASS,
  install 13/13 + permission verifier PASS, live config synced byte-identical

agents/designer.md

@@ -62,6 +62,26 @@ has approved. Never fill `.opencode/` with task-specific noise.
 - **Owned**: none (consumer role)
 - **Consume**: repo-context, conventions, architecture (when relevant)
 
+## Evidence & Handoffs
+
+Produce structured state records for design decisions and handoffs — not for every layout option:
+
+```text
+goal:                    <the design problem you were asked to solve>
+hypothesis:              <the user/behavior assumption you are designing for>   (when relevant)
+evidence:                <what was observed — user needs, constraints, conventions>
+actions_taken:           <what was actually done>
+result:                  <the design specification>
+verification:            <how the design was validated — accessibility checks, spec review, constraint check>
+confidence:              high | medium | low
+remaining_unknowns:      <what is still not known>
+recommended_next_action: <what should happen next, and who owns it>
+```
+
+Your primary evidence is the design spec: tokens, components, interactions, flows, and accessibility checks. Tie each decision to user needs or stated constraints; distinguish preferences from verified requirements.
+
+Stop when your deliverable is complete and verified per your Completion Rule; escalate when user needs or constraints are missing.
+
 ## Core Philosophy
 
 Mirror disciplined practical design: