Skip to content

OpenCode 2 (#730 WS2 remainder): plugin-array v2 verdict pass + subtask2 decision #3286

Open

Description

@dezren39

Parent

Remainder of #730 (OpenCode 2 migration, workstream 2), split out by queue triage task 2194 (2026-11-01) because the queue dedupe key for #730 is consumed by its triage task — this issue carries the follow-up's queue identity. #730 remains the parent tracker; the fleet-wide set is tracked at developing-today-forks/opencode#374.

State at split (verified on main 558cc1d2, triage task 2194)

Acceptance criteria

  • Every one of the 13 plugin-array entries has a v2-compatibility verdict recorded (here or on OpenCode 2: validate .opencode config against the v2 schema and port the v1 plugins #730): v2-ready (version), v2-incompatible (evidence), or unknown (what was checked — upstream release/changelog/API source cited, not assumed).
  • subtask2 has a recorded decision: v2-compatible release adopted, or fork/vendor/replacement options recorded with a recommendation (escalate to Drew if the choice is genuinely his).
  • The SDK-pin bump (@opencode-ai/plugin 1.18.19 → v2-era, with a v2 CLI load check of the repo's agents/commands/skills) is enqueued as a scoped small_fix packet informed by the verdicts, or recorded as blocked with the reason.

Activity

  1. added
    kind/featureNew feature or capability request
    priority/normalOrdinary priority (the default)
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 1, 2026
  2. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  3. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 1, 2026
  4. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked / escalated

  5. added
    queue/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 1, 2026
  6. 5 remaining items

  7. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    user/escalatedQueue or user escalation state
    queue/blockedQueue or user escalation state
    on Nov 3, 2026
  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  9. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 3, 2026
  10. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked

    Blocked — packet defect (verified fresh on npm, 2026-11-03):

    1. There is no v2-era release of @opencode-ai/plugin. npm view @opencode-ai/plugin versions runs 1.x only; dist-tags.latest is 1.19.5. Acceptance 1 ("pin moved from 1.18.19 to a v2-era release") cannot be satisfied under that package name.
    2. The v2 SDK ships under a new name: @opencode/plugin — dist-tags.latest 2.2.5, described by its publisher as "Authoring interfaces and runtime loader support for OpenCode V2 plugins". The laptop's v2 CLI is opencode v2.0.30.
    3. Adopting the renamed SDK is a plugin port, which this packet explicitly excludes. Local code imports the old package at runtime, not just for types: .opencode/plugin/mcpx-session.ts (import { tool, type Plugin }), .opencode/tool/session-identity.ts (import { tool }), .opencode/plugins/autoresearch-context.ts (type-only), plus tests under .opencode/plugin/mcpx/. Swapping the dependency without porting those imports breaks the load the acceptance wants checked; porting them violates the packet's "No plugin ports in this task" scope line.

    Correction needed (producer/Drew): reissue the packet as one of —
    (a) a rename+port task: @opencode-ai/plugin → @opencode/plugin@^2.2.5 including the local plugin/tool imports above, with the v2 CLI load check; or
    (b) a latest-1.x bump only: 1.18.19 → 1.19.5 with lockfile + load check, explicitly NOT v2-era (keeps local plugins on the v1 SDK they are written against).

    No files were changed. The empty worktree/branch queue/7452-3286-sdk-pin at ~/git/fleet/7452-3286-sdk-pin (laptop, base 550b611eb) is preserved for whichever corrected packet lands.

  11. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  12. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7452 (small_fix, blocked, priority 30) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort/lLarge: multi-day or open-ended; expect staged check-inskind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)queue/blockedQueue or user escalation statequeue/queuedHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions