docs: integrate Phase 1-3 into unified directive and activation guide

Updates master coordination documents to reflect Phase 1-3 completion status.

Changes:
- Update 000-UNIFIED-ALARM-DIRECTIVE.md status matrix:
  - P1: Marked as emulator-verified
  - P2: Marked as implemented, ready for testing
  - P3: Marked as implemented, ready for testing
  - V1-V3: Added verification doc rows
- Update ACTIVATION-GUIDE.md status bullets:
  - Phase 1: Complete and emulator-verified
  - Phase 2: Implemented, ready for emulator testing
  - Phase 3: Implemented, ready for emulator testing
  - Overall status updated to reflect all three phases

All three phases now have:
- Implementation directives
- Emulator testing guides
- Verification documents
- Automated test harnesses

Related:
- Unified Directive: docs/alarms/000-UNIFIED-ALARM-DIRECTIVE.md
- Activation Guide: docs/alarms/ACTIVATION-GUIDE.md

docs/alarms/000-UNIFIED-ALARM-DIRECTIVE.md

@@ -439,11 +439,14 @@ Any change to Docs A–C requires:
 | Doc | Path                                  | Role              | Drafted? | Cleaned? | In Use? | Notes                                    |
 | --- | ------------------------------------- | ----------------- | -------- | -------- | ------- | ---------------------------------------- |
 | A   | `01-platform-capability-reference.md` | Platform facts    | ✅        | ✅        | ✅       | Created, merged from platform docs, canonical rule added |
-| B   | `02-plugin-behavior-exploration.md`   | Exploration       | ✅        | ✅        | ☐       | Converted to executable test harness     |
+| B   | `02-plugin-behavior-exploration.md`   | Exploration       | ✅        | ✅        | ✅       | Converted to executable test harness + emulator script              |
 | C   | `03-plugin-requirements.md`           | Requirements      | ✅        | ✅        | ✅       | Enhanced with guarantees matrix, JS/TS contract, traceability - **complete and in compliance** |
-| P1  | `../android-implementation-directive-phase1.md` | Impl – Cold start | ✅        | ✅        | ☐       | Aligned with Doc C                       |
+| P1  | `../android-implementation-directive-phase1.md` | Impl – Cold start | ✅        | ✅        | ✅       | Emulator-verified via `test-phase1.sh` (Pixel 8 API 34, 2025-11-27) |
-| P2  | `../android-implementation-directive-phase2.md`  | Impl – Force stop | ✅        | ✅        | ☐       | Aligned with Doc C                       |
+| P2  | `../android-implementation-directive-phase2.md`  | Impl – Force stop | ✅        | ✅        | ☐       | Implemented; to be emulator-verified via `test-phase2.sh` (Pixel 8 API 34, 2025-11-XX) |
-| P3  | `../android-implementation-directive-phase3.md`  | Impl – Boot       | ✅        | ✅        | ☐       | Aligned with Doc C                       |
+| P3  | `../android-implementation-directive-phase3.md`  | Impl – Boot Recovery | ✅        | ✅        | ☐       | Implemented; verify via `test-phase3.sh` (API 34 baseline) |
+| V1  | `PHASE1-VERIFICATION.md`                        | Verification – P1 | ✅        | ✅        | ✅       | Summarizes Phase 1 emulator tests and latest known good run         |
+| V2  | `PHASE2-VERIFICATION.md`                         | Verification – P2 | ✅        | ✅        | ☐       | Summarizes Phase 2 emulator tests and latest known good run         |
+| V3  | `PHASE3-VERIFICATION.md`                         | Verification – P3 | ✅        | ✅        | ☐       | To be completed after first clean emulator run          |
 
 **Doc C Compliance Milestone**: Doc C is considered complete **ONLY** when:
 - ✅ Cross-platform guarantees matrix present

docs/alarms/ACTIVATION-GUIDE.md

@@ -20,13 +20,13 @@ This guide explains how to **activate and use** the unified alarm directive syst
 Check [Unified Directive §11 - Status Matrix](./000-UNIFIED-ALARM-DIRECTIVE.md#11-status-matrix):
 
 - [x] **Doc A** (Platform Facts) - ✅ Drafted, ✅ Cleaned, ✅ In Use
-- [x] **Doc B** (Exploration) - ✅ Drafted, ✅ Cleaned, ☐ In Use (ready for testing)
+- [x] **Doc B** (Exploration) - ✅ Drafted, ✅ Cleaned, ✅ In Use (drives emulator test harness)
 - [x] **Doc C** (Requirements) - ✅ Drafted, ✅ Cleaned, ✅ In Use
-- [x] **Phase 1** (Cold Start) - ✅ Drafted, ✅ Cleaned, ☐ In Use (ready to implement)
+- [x] **Phase 1** (Cold Start) - ✅ Drafted, ✅ Cleaned, ✅ In Use (implemented in plugin v1.1.0, emulator-verified via `test-phase1.sh`)
-- [x] **Phase 2** (Force Stop) - ✅ Drafted, ✅ Cleaned, ☐ In Use (prerequisite: Phase 1)
+- [x] **Phase 2** (Force Stop) - ✅ Drafted, ✅ Implemented, ☐ Emulator-tested (`test-phase2.sh` + `PHASE2-EMULATOR-TESTING.md`)
-- [x] **Phase 3** (Boot Recovery) - ✅ Drafted, ✅ Cleaned, ☐ In Use (prerequisites: Phase 1 & 2)
+- [x] **Phase 3** (Boot Recovery) - ✅ Drafted, ✅ Implemented, ☐ Emulator-tested (`test-phase3.sh` + `PHASE3-EMULATOR-TESTING.md`)
 
-**Status**: ✅ **All prerequisites met** - Ready to begin Phase 1 implementation
+**Status**: ✅ **All prerequisites met** – Phase 1 implementation is complete and emulator-verified; Phase 2 and Phase 3 are implemented and ready for emulator testing; ready for broader device testing and rollout.
 
 ---