Skip to content

v0.3.2

Choose a tag to compare

@Verlbot Verlbot released this 06 Sep 17:14
· 15 commits to main since this release
47be0ce

Honest connection health

Fixes #5 through #6. This health-only beta patch distinguishes a running sync process from usable phone-backed archive access.

  • Separate process heartbeat, transport, phone response, archive data, and validated snapshot evidence.
  • Stop treating saved pairing, timer activity, or relay token refresh as proof of a working connection.
  • Keep empty snapshots against a populated archive unverified until corrected, while allowing genuinely empty accounts and quiet inboxes without guessing from message age.
  • Require fresh evidence after recoverable interruptions; preserve terminal failure state against late events.
  • Make JSON doctor return nonzero when issues exist while still printing its JSON report.
  • Keep cached send settings distinct from a successful current refresh, preserve send/reaction protections, and use private atomic session writes.

Upgrade

Requires Go 1.25 or newer:

GOBIN="$HOME/.local/bin" go install github.com/fdsouvenir/gmcli@v0.3.2

Back up your database and session first. Store-opening commands, including offline doctor, apply the additive schema-4 migration. Archive rows are preserved; legacy activity is not promoted into new positive evidence. No down-migration is provided. Installing the executable does not replace an already-running sync process; arrange its restart separately.

Compatibility: scripts must handle a nonzero exit from JSON doctor when it reports issues. The legacy last_sync_activity_time field is not a connectivity signal; use the new evidence/status fields. The independently versioned archive skill is not republished, and its legacy health heuristic should not be used with this release.

Verification and limits

The three implementation/documentation commits were reviewed and merged as 47be0ce06d8a9924df8c16392727ea676e973fb3. Uncached Go tests, go vet, schema migration/archive-preservation tests, existing-schema-4 compatibility, and offline doctor checks passed. PR CI and merged-main CI provide repository verification.

recently_verified means bounded offline evidence, not guaranteed present connectivity. Quiet connected phones may become unknown after 15 minutes because the dependency does not expose all routine successful pings. Snapshot verification does not prove complete historical recovery.

This release does not claim a phone was reconnected. Google-account pairing remains in PR #4, with its mandatory real-device validation gate. No new Gaia pairing command, dependency upgrade, or unrelated CLI feature is included.