verification-before-completion

<EXPLICIT-MODE-GATE> If activation mode is explicit (`~/.config/aegis/config.toml` has `activation_mode = "explicit"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible in the environment) and the current user request did not explicitly invoke Aegis or this skill by name, exit back to the fast path: answer concisely without this workflow's checklist, ceremony, or document requirements. If the user explicitly named Aegis or this skill, proceed normally. </EXPLICIT-MODE-GATE> # Execute Before any success claim, classify destructive permission needs, choose and run a fresh falsifying check, read its complete result/scope, then select L0/L1/L2. If evidence is partial, stale, failing, or narrower than the claim, downgrade; never claim complete first and verify later. This Method Pack grants no authoritative `GateDecision`, `PolicySnapshot`, evidence sufficiency, requirement acceptance, or completion authority. ## Stop Signals Stop before claiming or advancing when: - evidence is uncertain, stale, agent-only, or narrower than the claim; - the next action is commit, push, PR, merge, tag, publish, release, or handoff; - task/slice completion is being treated as accepted requirement satisfaction; - governance or retirement lacks repair/retirement evidence; - retained old logic lacks a retention reason and retirement trigger; or - complexity closure is unresolved. Destructive or irreversible work needs scoped permission; warnings or broad assent do not grant it. ## Required Eviden...