[okisdev]

summary

• a peer brief for a UI package now names the rendered browser pass as the orchestrator's, after merge. of the 24 dispatched codex runs last week that loaded a browser verification skill, none produced a screenshot, and 14 stopped at listen EPERM when their sandbox refused the dev server port, after spending turns probing for Playwright and starting servers. the sentence joins the existing rule that peers report process dependent suites as environment findings and the orchestrator reruns them
• release 0.0.66: the four plugin versions and the marketplace are bumped together, and rules-manifest.json is regenerated

test plan

already verified

• npm test -> 1619 tests, 1616 pass, 0 fail, 3 skipped
• claude plugin validate on plugins/codex, plugins/grok, plugins/cursor, plugins/fusion, and . -> all passed
• node plugins/fusion/scripts/generate-rules-manifest.mjs -> 52 rules template versions, the new one included

reviewer should verify

• after the marketplace update and /fusion:setup, ~/.claude/rules/orchestration.md carries the new sentence, and the next UI brief to codex names the browser pass as the orchestrator's

notes

• rules edits, per CONTRIBUTING's rules release checklist: one sentence added, nothing deleted or softened, and no load bearing invariant touched