Skip to content

1.7.225.dev0 — guarded OpenCode 2.3.x history recovery

Pre-release
Pre-release

Choose a tag to compare

@groopcd groopcd released this 18 Nov 17:09
· 24 commits to devel since this release

1.7.225.dev0 — guarded history recovery across stable OpenCode 2.3 patches

Experimental development prerelease from devel, source
44b1c1442411732c012689202bcb6cd8f9c8befb. Not a stable release or security
certification. Stable master and v1.6.94 remain unchanged.

Highlights

  • Recognize stable OpenCode 2.3.x: one shared storage-profile selector handles
    canonical stable 2.3.N releases instead of requiring a new allowlist entry
    for every patch. Legacy 2.2.6/2.2.7 remain shell-only.
  • Handle the real 2.3.1/2.3.2 scheduler change: recognize known schedule
    and newer automation column layouts, require exactly one, and refuse every
    scheduler row before native startup, including terminal/unknown and WAL rows.
  • Validate newer retained-subagent metadata: optional outstanding lists
    receive bounded, explicit shell/subagent validation. Image, Code Mode, nested,
    unknown and malformed forms remain refused rather than silently discarded.
  • Explain compatibility refusals: unsupported versions warn before the owning
    client opens; recognized metadata/API incompatibilities advise checking for an
    oc-box update first and updating an older OpenCode when appropriate. Keep data;
    never reset or downgrade workspace state to bypass a refusal.

Shutdown behavior

The existing verified whole-container stop, same-resource restart, isolated
unregistered Reader, checked exports/imports, host verification and final cleanup
remain authoritative. Native executable probes must match the captured exact
patch on both sides; a common series does not waive a patch mismatch. Native
2.3.0 cannot consume an automation-layout store through this path.

A raw clean client may return 0 after a live timeout only when the guarded copy
and cleanup succeed. Actual client failures, cancellation, unknown status,
partial/failing sync and uncertain cleanup remain nonzero, with manual-sync
guidance. Interruption and unconfirmed-background-completion warnings remain.
No job is declared complete, deleted, acknowledged or resumed.

The 30-second activity grace is unchanged. This release does not speed up large
history exports, expand unrelated native UI/attachment support, or enable ordinary
manual-sync preparation as an automatic-recovery shortcut.

Validation and limits

  • Focused source checks and independent runtime review covered the shared
    profile, strict scheduler/job metadata, exact binary matching, failure/cleanup
    outcomes and fixed compatibility guidance.
  • A fresh synthetic native 2.3.2 regression passed: 12 sessions verified, one
    Reader, eight source and eight destination automation refusals, preserved
    source/destination jobs, claims, queued input and original history, and no
    extra provider/shell/plugin execution. Initial fixture failures remain failed
    evidence; corrected runs are recorded separately.
  • The operator subsequently reported a real-workspace pass with this exact
    candidate and native 2.3.2: all 136 sessions exported unchanged, zero pending,
    successful automatic post-stop fallback and final cleanup, exit 0 without
    manual sync. This is user-supplied output, not an independently inspected full
    host-fixture gate. It establishes no new changed-archive import verification,
    job completion, general lifecycle or performance claim.
  • CI retains native 2.3.0 and follows the latest stable 2.3 patch, recording its
    actual version and binary hash.

Future-patch behavior is not proven solely by matching layouts. Guards check
columns, not all defaults, triggers, indexes or foreign keys; native startup can
change without changing them. Unknown minor/major series, prereleases and
modified identities remain refused. Nonempty outstanding forms have synthetic
metadata coverage, not a separately observed native reproduction.

Historical acceptance and failure evidence retain their exact source/native
identities. The earlier 631d317 host runner remains failed/incomplete at 20/29;
its twelve verified archives and later informational retained-state audit do not
reclassify that run or accept every subsequent source.

Previously disclosed dashboard limits remain: full UI restore returned 0 but the
later verifier refused manifest. The observed extraction-root mode tightening
from 0755 to 0700 does not establish all-entry equality or the sole cause of that
refusal. Portable UI was unarmed; remaining three-scope
Storage, reviewed ciphertext deletion, source-removal preservation, final
journal/attestation and manager Quit checks are unaccepted/unperformed. Human
observations retain NOT_AUTOMATICALLY_PASSED. Offline/native results do not imply
rendered-browser/host-gesture, real-provider, network-containment or comprehensive
host acceptance. This prerelease does not promote stable or waive those gates.

Distribution

GitHub development prerelease and matching oc-box==1.7.225.dev0 package. Exact
publishing-workflow wheel, sdist, validated identity and checksums are attached
after successful publication. No LinkedIn announcement is approved.