sweep-all

Sweep all disciplines

A declared second species in this plugin: NOT a corrector. Every sibling skill re-anchors ONE discipline; this one carries no discipline of its own. It is a pure router that COMPOSES the correctors into a single batched re-anchor pass. It holds zero discipline text: the disciplines live in the correctors, the shared method lives in ${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md, and membership + order live in each corrector's own tier metadata. This skill names no members. It globs and reads them, so the bundle cannot drift from a hand-maintained list.

Two modes

1. Session-start digest (cheap, default when nothing has happened yet). Derive the posture from the skill listing and each corrector's tier metadata. NO corrector bodies load, NO audit runs. Report which correctors are core (run every session), which are situational (relevance-gated), and which are never-batched. This is the conversation-start case: set posture, audit nothing.
2. Full batch pass (mid-session, or on explicit request). Preflight that the fan-out can inherit this conversation (mandatory. See Preflight), then fan out an audit-only subagent per in-scope corrector and apply their corrections once, on the main thread, in a fixed order (below). A failed preflight degrades to mode 1 with the exact degrade token as the report's first line (see Preflight).

Resolving membership (never named inline)

Glob the sibling corrector directories and read each one's metadata.discipline-batch (core / situational / never) and metadata.discipline-batch-rank. The runbook never hardcodes member names; the tier is colocated with each corrector, so changing a shipped tier is a PR to that corrector. Drift is structurally impossible.

• core. In scope every session.
• situational. In scope only when relevant to THIS conversation. Route from the corrector's own listing description (its trigger phrases and "at conversation start on …" clause), not from a guess. Report which situational correctors were included and which were skipped and why. A skip is always reported, never silent.
• never. Excluded from the batch by execution or interaction class (heavier fan-out tiers; correctors that need a non-fork fresh context or stop to remediate with the user). Membership is whichever correctors declare discipline-batch: never. This runbook does not enumerate them. Report that they exist (from the glob) and are invoked directly, not batched.