Skip to content

1.7.224.dev0 — verified shutdown history-sync outcomes

Pre-release
Pre-release

Choose a tag to compare

@groopcd groopcd released this 18 Nov 15:20
· 25 commits to devel since this release

1.7.224.dev0 — verified shutdown history-sync outcomes

Experimental development prerelease from devel; not a stable release or a
security certification. Source: cb1e299b34835fcc2468913967af1bcb8aa0423a.

Highlights

  • Use the final synchronization result: a clean native client may now exit
    successfully after a live-readiness timeout only when the existing guarded
    post-stop archive copy, native verification, recovery cleanup and final
    container stop all succeed.
  • Keep real failures actionable: original client errors and cancellation,
    unknown client status, partial or failed synchronization and uncertain cleanup
    remain nonzero. The guidance to retry oc-box sync remains on synchronization
    or cleanup failure.
  • Separate waiting from copying: progress labels distinguish the live
    activity wait from archive synchronization. Aggregate-only feedback reports
    source mode and exported/unchanged/updated/pending counts without identifiers,
    transcript text, commands or credential values.

Behavior and safety

The initial 30-second live-work grace is unchanged. This is not a native
export/import timeout, and the change does not clear native job records,
declare background work complete, resume pending work, add client autoaccept or
speed up full-history exports.

The existing verified-stop Reader and the same checked archival backend used by
manual sync remain in place. There is no recursive CLI call or extra ordinary
runtime/configuration/credential preparation in the fallback. The explicit
interrupted-work and unconfirmed-background-completion warning remains.

Validation and experimental limits

Eighteen focused local regression methods and independent code/documentation
review covered the changed result, failure-guidance and cleanup policy. Release
CI and the guarded build-only workflow supply their own source, native and
package checks; their results are attached to this exact source, not a new
external-host acceptance.

The new exit-outcome policy has no clean formal external-host acceptance.
The historical 631d317 host runner remains failed/incomplete at 20/29 checks
because of its import PATH versus native session import PATH observer
mismatch. It recorded one guarded recovery and twelve native-verified archives;
a separate informational audit confirmed the retained source and original
destination logical table hashes. Missing original in-memory plugin, schema,
export/digest, warning/output and process baselines remain unavailable. Those
observations and the later 65bae6b successful fallback observation are not
reclassified as acceptance of this source.

Previously disclosed dashboard limits remain: full UI restore returned zero but
its later verifier refused manifest; portable UI was unarmed; remaining
three-scope Storage, reviewed ciphertext deletion, source-removal preservation,
final journal/attestation and manager Quit checks are unaccepted/unperformed.
Manual observations retain NOT_AUTOMATICALLY_PASSED. Rendered browser behavior
and actual host-gesture coverage are not implied by offline/native probes.
Historical 42-check history/readiness, 12/six recovery, vault, sharing and CLI
lifecycle reports retain their original source/native identities.

This prerelease does not promote master or stable, waive the outstanding
formal-acceptance work, or certify every timeout/project. Raw private fixture
evidence is not published.

Distribution

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