fixing logs

Author: EMaher

.squad/decisions.md

@@ -150,29 +150,9 @@
 - Use hand-rolled yaml for deterministic outcode, like CI gates.
 **Context:** The branch maintenance plan defines 6 new workflows. Elizabeth asked whether gh-aw could replace hand-rolled YAML implementations.
 
-**Decision — Phased adoption (hybrid approach):**
-
-**Convert to gh-aw (Phase 1 — Advisory Workflows):**
-- `squad-triage-advisor.yml` → gh-aw LabelOps pattern
-- `external-pr-advisor.yml` → gh-aw PR event pattern
-- `squad-clarify-advisor.yml` → gh-aw LabelOps pattern
-
-**Keep as Traditional YAML (Deterministic Gates):**
-- `block-workflow-changes.yml` — CI gate, needs deterministic pass/fail
-- `squad-history-protection.yml` — CI gate, needs deterministic pass/fail
-- `squad-dashboard.yml` — Scheduled report, mostly data aggregation
-
-**Rationale:**
-1. Advisory workflows benefit most from AI reasoning (intelligent comment generation vs brittle templates)
-2. CI gates must be deterministic — AI non-determinism is unacceptable for security controls
-3. safe-outputs architecture aligns with Two-Tier labeling policy
-4. gh-aw eliminates ~200 lines of github-script per advisory workflow
-
-**Prerequisites:**
-- [ ] `gh aw` CLI extension installed in CI
-- [ ] Team evaluates gh-aw lock.yml compilation in local dev
-- [ ] Determine if safe-outputs can enforce Tier-2 label blocking adequately
-- [ ] Evaluate AI response quality for triage recommendations
+**Decision:**
+- Use gh-aw LabelOps pattern, event pattern for advising.
+- Use hand-rolled yaml for deterministic outcode, like CI gates.
 
 **Impact:** Reduces maintenance burden for advisory workflows; eliminates keyword-matching brittleness in triage; no change to security posture.
 
@@ -202,7 +182,7 @@
 - V14: Compiled output tampering (must be in CODEOWNERS)
 - V15: Framework supply chain (low probability, monitor GitHub advisories)
 
-**Tier-1/Tier-2 Label Security:** `blocked: ["squad:*", "go:*", "priority:*"]` provides equivalent or stronger protection than current policy. Gaps: re-application prevention (add to agent instructions), glob pattern completeness (use both `allowed` and `blocked`).
+**Label Security:** `blocked: ["squad:*", "go:*", "priority:*"]` provides equivalent or stronger protection than current policy. Gaps: re-application prevention (add to agent instructions), glob pattern completeness (use both `allowed` and `blocked`).
 
 **New Guardrails Required (MANDATORY for adoption):**
 1. Comment provenance banner — All gh-aw-generated comments must include visible "🤖 Generated by gh-aw workflow: {name}" header