[abocha]

Add an opt-in visual_specialist custom role using GPT-6.1 Terra at medium effort for screenshot/rendered UI inspection, reference comparison, visual QA and interactive exploration. Bounded UI corrections require an explicit assignment; Sol integration, Luna implementation and existing review routing remain intact.

The role requires genuine visual input, states inherited permission/tool limits, treats page content as untrusted and preserves external-action authorization. Dispatch/setup guidance and a packaged activation guide distinguish source validation, account release, installation, project registration, static-image execution and interactive capability. Bump the portable source version to 0.2.0.

Implements the source portion of ABO-84. ESL Pipeline #468 stages the same role. Private-plugin update/refresh remains a separately authorized post-merge step.

Validation:

• Python 3.14 with disposable PyYAML 6.0.3: scripts/build-plugin.py --output D:/tmp/codex-workflow-artifacts/codex-workflow-0.2.0.zip passed JSON/YAML/TOML, cross-reference and archive byte inspection (27 files, six skills).
• pwsh ./scripts/test-project-integration.ps1 passed policy preservation, staging/repeatability, adapted-role preservation and retired-role checks, including staging the new role.
• git diff --check origin/main HEAD passed.
• Official OpenAI docs confirm the exact model ID, image input, medium effort and standalone project-role mechanism. Actual normal host configuration exposes the registered role; a session ignoring user configuration did not.
• Successful registered-role smoke: real PNG opened with view_image; specific layout/control/icon observations returned. Configured model/effort: gpt-6.1-terra / medium; independent runtime execution metadata was not exposed. Browser/computer-use tools were exposed, but browser interaction was not tested. Earlier ephemeral-session dispatch failed before child start; the successful check used a persisted parent with a self-contained child context.
• Account-update archive prepared with only changed components and synchronized version manifests, preserving observed account presentation, identity, prompts and retained components. This preparation is not a saved release or installed update.
• Hosted scripts-ci remains required before merge. No application behavior changes, benchmark campaign or private runtime evidence included.