Deploy Poimen Memory K8s cluster with ArgoCD tracking (M2.2, M3.5-M3.7)

tasks/M1.8-m1-gate.md

@@ -4,7 +4,7 @@
 |---|---|
 | Phase | M1 — Gated loop at L1 |
 | Size | M — 1–3 days |
-| Status | ⬜ Not started |
+| Status | ✅ Done |
 | Flags | gate |
 | Spec | inlined below |
 | Blocks | all of M1 |
@@ -14,6 +14,25 @@
 Answer the only question that matters at this stage: **did we build a gate, or an
 expensive summarizer?**
 
+## Files
+
+| Action | Path |
+|---|---|
+| Create | `tests/it_m1_gate.rs` — integration tests (workspace root, all `#[ignore]`, 7 assertions) |
+| Create | `fixtures/expected/m1-gate.txt` — committed expectation file (summary table) |
+
+## Dependencies
+
+**None new.** This task runs existing code against the live gateway.
+
+## Existing code to reuse
+
+The entire M1 pipeline:
+- `QuerySet::load()` (M1.2), `ChatClient` (M1.1), `run_loop()` (M1.5), `LogWriter` (M1.6)
+- `PiSessionSource` / `ClaudeTranscriptSource` (M0.5/M0.6) — existing
+- `chunks()` (M0.3) — existing
+- `LogReader::stats()` (M1.6) — to recompute update-rate independently
+
 ## Facts (inlined — no spec read needed)
 
 This gate runs against the **live gateway on a real project** and asserts
@@ -75,7 +94,7 @@ per-push.
 7. `a7_judge_audit` — sample 20 decisions, ask the 32B model, print agreement.
    Advisory; does not fail the gate.
 
-**Command:** `cargo test --workspace m1_gate -- --ignored --nocapture`
+**Command:** `cargo test --test it_m1_gate -- --ignored --nocapture`
 
 **False pass:**
 - Running the gate on a tiny `--limit`. Update-rate on the first 20 chunks is