Opus finding
Transition table is ambiguous/contradictory for ACTIVE→POWER and POWER→POWER
mediumdocs-gaphigh
- skills/fork-cohort/SKILL.md:126-136
`(any) → POWER` matches POWER → POWER (steady-state, not a transition), which would emit a LEVELED_UP signal every week for every persistently-POWER fork — flooding the verdict (step 7 priority #1) and the notify. It also overlaps `(absent) → ACTIVE / POWER` (NEW_ACTIVE) and `STALE → ACTIVE / POWER` (REVIVED): a fork going STALE → POWER hits both REVIVED and LEVELED_UP rules. Verdict priority resolves the notify line, but the article's "Leveled up to POWER" subsection and the state-file deltas have no precedence rule — the same fork will be listed in both Revived and Leveled-up sections.
Recommendation
Restate `(any) → POWER` as `non-POWER → POWER` (i.e. prior bucket exists and was not POWER). Add an explicit precedence: LEVELED_UP supersedes REVIVED/NEW_ACTIVE when the destination is POWER, so a fork is listed in exactly one Movement subsection. Add a row for POWER → STALE/COLD (currently falls into WENT_STALE/WENT_COLD by the ACTIVE/POWER → COLD row but WENT_STALE only mentions ACTIVE → STALE).