fix(opencode): Judgment Day judges cannot inspect Engram-backed targets

[SantiagoMQv]

Pre-flight Checklist

• I searched open and closed issues and found no equivalent report. Related but distinct: fix(opencode): 4R reviewers cannot read external review artifacts #1977, fix(opencode): SDD orchestrator cannot launch phase subagents in noninteractive run #2307, and fix(review): Judgment Day is a developer tool but requires delivery-receipt machinery to start #2487.
• I understand that PRs require status:approved before implementation.

📝 Bug Description

On Gentle AI 2.2.4 with OpenCode 1.18.13, both managed Judgment Day judges fail before inspecting an Engram-backed SDD design target. The judge runtimes expose no Engram MCP resources or resource templates, and reads of the exact injected skill and repository source roots are denied by the external-directory policy.

This report records observed evidence only; it does not assert an unconfirmed root cause. The workflow fails closed: no findings or verdict are produced, and dependent SDD task planning remains blocked.

🔄 Steps to Reproduce

1. Use an Engram-backed SDD change whose design artifact has a stable opaque revision.
2. Launch the managed blind jd-judge-a and jd-judge-b agents through the supported subagent mechanism.
3. Ask each judge to read the Engram artifact, verify its revision, load exact injected skills, and inspect bounded repository sources.
4. Observe both judges return incomplete before inspection because no Engram MCP resources/templates are available and external-directory reads are denied.
5. Retry once with explicit user authorization and the same immutable target.
6. Observe the same two failures again.

✅ Expected Behavior

Managed Judgment Day judges should receive the immutable Engram-backed artifact and exact comparison context through a supported, narrowly scoped integration. They should be able to load the required managed skills and permitted repository sources, complete both blind inspections, and return a verdict while unrelated external paths remain denied.

If Engram-backed targets are unsupported, the integration should return a typed preflight result before launching judges, with an actionable supported route that preserves the target and review state.

❌ Actual Behavior

Two bounded attempts were made, each with both blind judges, for four judge runs total. Every run failed before inspection. The repeated envelopes reported:

INCOMPLETE: Engram observation revision could not be read or verified because no MCP resources or resource templates were available.
Required injected skill and repository source reads were denied by the external_directory permission policy.

No judge inspected candidate content. Findings remained empty because inspection never began, and no APPROVE or REJECT verdict was emitted.

Gentle AI Version

2.2.4

Operating System

macOS

AI Agent / Client

OpenCode 1.18.13

📋 Affected Area

Agent Detection

💡 Logs / Error Output

completed_inspection: false
attempts: 2 Judgment Day launches, 2 blind judges per launch
outcomes: 4 incomplete inspections
engram_resources: unavailable
external_directory: denied for injected skills and bounded repository sources
verdict: none
mutation_outcome: none by judge runs

Additional Context

• Platform: Darwin arm64; shell: zsh.
• Operation shape: read-only Judgment Day over an Engram-backed SDD design, using an opaque target revision and exact injected skill/source roots.
• The target revision remained unchanged. Judge runs did not modify repository bytes, staging, lifecycle authority, or the canonical SDD artifact.
• Expected dependent action was task planning; it remained blocked.
• fix(opencode): 4R reviewers cannot read external review artifacts #1977 addressed a 4R temporary-artifact path and was closed after PR fix(review): replace eager diff transport with frozen git trees #1970, with a maintainer request to file a fresh issue if the denial reproduced on a later build. This occurrence is Judgment Day plus an Engram-backed target on 2.2.4.
• fix(opencode): SDD orchestrator cannot launch phase subagents in noninteractive run #2307 concerns noninteractive SDD phase fallback from subagent to orchestrator. Here the Judgment Day subagents launched, but could not access their required inputs.
• fix(review): Judgment Day is a developer tool but requires delivery-receipt machinery to start #2487 concerns coupling Judgment Day to receipt machinery. This occurrence fails earlier at target and skill/source inspection.
• Diagnostics were privacy-scrubbed: no raw arguments, absolute paths, private repository names, usernames, hostnames, credentials, source contents, diffs, or environment values are included.

[SantiagoMQv]

Closing this report after further diagnosis.

This occurrence was caused by a recovery-route mismatch rather than a general Engram access regression. The SDD change began under Gentle AI 1.46.0 with hybrid persistence, was later explicitly moved to OpenSpec authority, and the current recovery accidentally produced an Engram-only design before directly launching the hardened Judgment Day judges.

The parent orchestrator and normal SDD agents can read Engram. The dedicated judge profiles intentionally expose only bounded read access and no Engram MCP tools, while the repository sources for this recovery were outside their permitted root. The 2.2.4 cutover canary covered a fresh OpenSpec RDD-off workflow with no reviews or Judgment Day, so it did not validate this legacy recovery shape.

The correct recovery is to restore OpenSpec as the artifact authority, materialize the reconciled design there, and re-enter through the supported native review transport from the correct worktree. No Gentle AI fix is requested on the evidence currently available. Closing as an incorrect initial diagnosis while preserving this clarification for audit.