Adopt platform SDLC standard (ADR-0003): task class, blocking DoD, verifier families, OutcomeEvent

[100rd]

Platform ADR-0003 (unified SDLC standard) is accepted: https://github.com/100rd/genai-enablement/blob/main/docs/decisions/0003-unified-sdlc-standard.md

multiqlti conformance work (Appendix A of the ADR — all policy/config level, engine unchanged):

• I1 — task class field + auto-escalation: runs carry class (R0 default). Attaching a workspace commit, sandbox execution with external effects, or a deployment target escalates R0 → A/B/C/E automatically. A run must not silently stay R0 after gaining a workspace.
• I3 — quality-gated DoD default (class ≥ A): default pipeline template wires code_review.approved == true and fact_check.verdict != fail as blocking guardrails/DAG conditions (mechanism exists: guardrail-runner llm_check/json_schema, DAG condition evaluator). R0 runs keep advisory mode. Needs a migration note: some runs that used to reach completed will now fail — intended.
• I4 — verifier family preset: config preset pinning testing / code_review / fact_check to a different model family than development; record the attestation in run metadata. Consensus engine remains the stronger optional form.
• I6 — OutcomeEvent emitter: one structured event per run at terminal state (task_id, factory, class, tier, lifecycle, verdict, gate, verifier_families, landed_at, cost_usd). Schema will be published versioned in genai-enablement — track that follow-up.
• I8 — escape join: incident/revert signals joinable to run.id (source independent of the verifying stage).

Reference vocabulary: https://github.com/100rd/genai-enablement/blob/main/docs/platform-glossary.md

[100rd]

Re-scope note (post-#525 pipeline retirement):

1. Appendix A machinery is retired. guardrail-runner, the DAG-condition-evaluator, staged pipeline lifecycle, and per-stage model presets no longer exist. The live unit of work is the consilium loop (consilium-loop-controller.ts + server/services/sdlc/*). A re-derived invariant mapping (I1–I8 → kept machinery) exists as the live design doc for this issue; implementation is phased P1–P6, with P1 (additive class/autonomyTier on consilium_loops, default R0, zero behavior change) landing first.
2. I7 (skills registry) folds into Parse Agent Skills SKILL.md in git-skill-sync (platform skills registry, ADR-0002) #446 — delivered by the git-backed skills sync work; no duplicate effort here.
3. I6 (OutcomeEvent) no longer builds on OTel ([Phase 6.5] Tracing & Observability (OpenTelemetry) #94) — the OTel/core-Tracer stack is dead-after-carve and slated for deletion; I6 becomes a fresh lightweight emitter (DB row + log) fired per loop terminal state, with cost_usd joined via the run_id column rename.