OpenCode v2 ignores config instructions (usai-provider list, scope-layers doc, team-kit template) #482

Since acq 4.0 (#466), every OpenCode sandbox also gets OpenCode 2.0.22 from the opencode kit. Images that bake OpenCode 1.x (acq's opencode-docker template, the default for acq run opencode, and devenv-opencode) still run 1.x first on PATH, so instructions load there. An image with no OpenCode of its own (shell-docker, devenv-shell, the agent-less direction of quickstart ADR-0030) runs only 2.x, and there OpenCode v2 accepts the instructions config field but never reads it: anomalyco/opencode#51341 (open), fix in anomalyco/opencode#51422 (open).

Confirmed with live runs: on 2.0.22 (msb 0.7.6), a file listed in instructions through OPENCODE_CONFIG did not reach the agent's context, while the global ~/.config/opencode/AGENTS.md (the playbook) did. On msb 0.7.7 with acq v4.0.1, opencode-docker resolved opencode to 1.18.32 and devenv-opencode:1.0.0 to 1.18.23, while shell-docker had only the kit's 2.0.22.

Affected here, on images where 2.x runs:

• usai-provider opencode.jsonc: CLAUDE.md, CONTRIBUTING.md, .cursor/rules/*.md and .github/copilot-instructions.md are not loaded (AGENTS.md still loads natively).
• integrations/isolation/docs/scope-layers.md: the "Your own agent instructions (OpenCode)" row recommends OPENCODE_CONFIG_CONTENT with instructions. feat(isolation): add the scope-layers pattern and a team-kit template #441 now notes the limitation and which images it applies to.
• The team-kit template (feat(isolation): add the scope-layers pattern and a team-kit template #441) delivers team conventions through instructions. Its scripts/verify now fails when the sandbox runs 2.x.

Remaining: the usai-provider list has no note yet. Re-test all three once the opencode kit pins a release with anomalyco/opencode#51422.