Repository navigation
oc-box 1.7.117.dev0 — OpenCode 2.3.0 history recovery
Pre-releaseOpenCode 2.3.0 exit-history recovery backport
This experimental development prerelease brings the audited OpenCode 2.3.0 persisted-history recovery extension from master to devel. It does not update the stable release.
- Enables the existing guarded post-stop recovery path for exact native 2.3.0, alongside 2.2.6 and 2.2.7. Unaudited versions still fail closed.
- Uses one shared exact-version allowlist for recovery eligibility and the isolated reader.
- Retains the original live timeout, nonzero exit and interrupted-work warning. This saves checked persisted history; it does not repair/delete native jobs, resume work or refresh credentials.
- Ports the focused guard regressions and ownership-safe native fixture from
328f83e/7f441b8. No unrelated stable runtime, host-fixture, CI-orchestration or dashboard changes are merged.
Validation and limitations
Local validation was deliberately focused: 68 guard/process tests and the unmodified OpenCode 2.3.0 native recovery fixture passed. The native fixture reproduced the held-shell timeout, used a verified local producer-stop/reap barrier, recovered through one isolated reader with real archive/import verification, preserved durable jobs/schedules/transcripts, and refused all eight source and eight destination scheduler cases.
The required guarded package workflow separately validates the exact clean source, wheel/sdist, optional TUI/vault installation, identity and checksums before PyPI publication. The release assets are that publishing run's exact distributions, validated-identity.json and SHA256SUMS.
Completed candidate CI: guarded build-only, Python 3.10/3.13, package and retained V1/V2 native integration, and all seven distro jobs.
The single guarded publishing run completed successfully. Its exact artifacts are attached here and the package is on PyPI. Anonymous public GitHub and PyPI downloads were compared byte-for-byte with those validated artifacts; the wheel and sdist SHA-256 values match SHA256SUMS.
No new external-host Podman or dashboard acceptance is claimed. Earlier evidence remains bound to its original source/native identities. The dashboard full-restore integrity verifier's manifest refusal and the unperformed portable UI/Storage/removal/final-attestation/Quit checks remain experimental limitations, not passes. See the complete 1.7 notes.
Upgrade
For an existing channel-aware installation, run on the host as your regular user:
oc-box upgrade --devel
oc-box --versionFor a GitHub installation enabling the optional dashboard for the first time:
curl -fsSL --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/groopcd/oc-box/master/install.sh | sh -s -- --devel --with-tui --with-vaultOmit --with-vault if unused. No workspace reset or history reimport is required. A launcher downgrade is not a workspace/session-state rollback. Stable installations remain on the stable channel unless explicitly switched.
Source identity
- Public version/tag:
1.7.117.dev0/v1.7.117.dev0 - Full identity:
1.7.117.dev0+g2f113ff - Source:
2f113ff0c4e46c13a01cbeec11b048c7ecbce4bd - Full-history commit count: 146; retained baseline: 29
- Channel:
devel, GitHub prerelease and PyPI.dev0, not a stable promotion.