EPIC C and EPIC D are one graph, not two lists

Epic D's five adoptions are the re-home targets for Epic C's nine retirements. The governing order is stated in C's body: re-home the opinion first, observe it firing, then delete the pipe. Deleting first loses the opinion, and has already cost this repo two PRs to notice once.

3 / 5Epic D adopted in code
3 of 9Epic C "overlaps" that were refuted
92%v10.0.0 milestone (112/121)
2issues that unblock the rest

The finding that should change the plan

The audit's overlap column is not settled evidence. Three separate times, a CC feature that merely resembled an ork mechanism was recorded as replacing it. Each was refuted only when someone probed the actual behaviour rather than reading the docs.

Mechanism 06 is the sharpest: it was marked CONFIRMED on the strength of CC's own plugins reference, then retracted the same day. An empirical probe already committed in scripts/build-plugins.sh said the opposite, and re-running it gave 35 command wrappers loaded with commands/ present and 0 without. Acting on the documentation would have deleted every /ork: slash command while leaving 105 skills model-invocable only.

Epic C: the nine, by probe verdict

mechwhat it isverdictevidence
Verdicts are taken from the probe comments on the epic, not from the original audit table. "unprobed" means no fitness probe has been run and recorded, so its RETIRE classification is still an unverified claim.

Epic D: the five, and what each unlocks

capabilityissuestateretirement it re-homes

Three landed together in #3582. A baseline correction is recorded there and is worth repeating: before that PR the true state was 0 of 5 adopted in code. Two earlier closures had counted documentation prose as adoption.

The critical path

Only two issues actually gate the remainder, and one of them is a decision rather than a change.


    

      

        
#3424 needs an operator decision, not code. Stage 1 of the sandbox rollout is already live on this machine (sandbox.enabled, autoAllowBashIfSandboxed, 19 denied domains, strictAllowlist off), while the rollout doc still states nobody has run stage 1 for a day. The written plan and the running state disagree.

      

      

        
#3326 is small and unblocked. The plugin dependencies array is the only Epic D item with no security decision attached, so it is the piece that can move without waiting on anything.

      

    

  


  
What I would do next, in order

  

    

      
actionwhy now